On Wed, Jan 15, 2020 at 6:01 PM Hauke Mehrtens wrote:
>
> Hi,
>
> I meet with jow about 2 weeks ago and we talked about a lot of OpenWrt
> related stuff, one of the topics was the release after 19.07.
>
> As the 19.07 release is now done, I would like to follow up on this topic.
>
> We thought
Hi,
I meet with jow about 2 weeks ago and we talked about a lot of OpenWrt
related stuff, one of the topics was the release after 19.07.
As the 19.07 release is now done, I would like to follow up on this topic.
We thought that the time between the 19.07 branch and the final release
was way too
On 05/12/2019 11:58, Florian Eckert wrote:
+++ b/package/network/services/wireguard/Makefile
@@ -93,6 +93,8 @@ define Package/wireguard-tools/install
$(INSTALL_BIN) ./files/wireguard_watchdog $(1)/usr/bin/
$(INSTALL_DIR) $(1)/lib/netifd/proto/
$(INSTALL_BIN)
On 05/12/2019 11:33, Florian Eckert wrote:
If a config section of a peer does not have a public key defined, the
whole interface does not start. The following log is shown
daemon.notice netifd: test (21071): Line unrecognized: `PublicKey='
daemon.notice netifd: test (21071): Configuration
On 22/12/2019 21:50, Michal Cieslakiewicz wrote:
This patchset introduces support for two Netgear dual-band routers
based on the same PCB (29764821) with QCA9563 SoC, AR9580 5GHz chip,
128 MiB RAM, 2 MiB SPI-NOR + 128 MiB SPI-NAND flash:
* Netgear WNDR4300 v2
* Netgear WNDR4500 v3
WNDR4300v2
On 09/01/2020 19:27, Maxim Storchak wrote:
If zram-backed swap is added after an existing swap, it gets a lower
priority. Assiming that usually all other swaps are slower, there should
be a way to assign a higher priority to zram swap.
Signed-off-by: Maxim Storchak
Merged, thanks !
---
On 12/01/2020 20:20, David Bauer wrote:
This commit adds support for the D-Link DIR-505, previously supported in
ar71xx.
Hardware
SoC: Atheros AR9330
FLASH: 8M SPI-NOR
RAM: 64M
WIFI: 1T1R 1SS Atheros AR9330
LED: Power green, Status red
BTN: WPS, Reset
Installation
On 22/12/2019 02:51, Rosen Penev wrote:
The depends are totally wrong. libunwind does not work with powerpc and
i386 as it needs glibc.
Instead of duplicating the platforms, just change the dependency.
Signed-off-by: Rosen Penev
Merged, thanks !
---
package/devel/perf/Makefile | 4 ++--
Hello,
The following patches (submitted by you) have been updated in Patchwork:
* openwrt: [OpenWrt-Devel,v3] dropbear: move failsafe code out of base-files
- http://patchwork.ozlabs.org/patch/1197588/
- for: OpenWrt development
was: New
now: Accepted
* openwrt:
On 07/11/2019 11:40, Florian Eckert wrote:
With this change it is now possible to switch off single instances of
the uhttpd config. Until now it was only possible to switch all
instances of uhttpd on or off.
Signed-off-by: Florian Eckert
Merged, thanks !
---
Merged, thanks !
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Merged, thanks !
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 13/11/2019 22:09, Jeff Kletsky wrote:
From: Jeff Kletsky
Certain boards have limitations on U-Boot that prevent flashing
of images where the kernel size exceeds a threshold, yet
sysupgrade can sucessfully manage larger kernels. The current
check-size will remove the target artifact if its
Merged, thanks !
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 01/01/2020 16:55, Jo-Philipp Wich wrote:
Hi Linus,
can you move the condition before the sed program populating the initial
config? That should restore the ability for users to deselect busybox
hdparm (e.g. to replace it with something different).
~ Jo
folded Jo's comment into the patch
On 14/01/2020 17:40, Tomasz Maciej Nowak wrote:
The memory hacks got removed from ath10k with 1e27bef ("mac80211: remove
ath10k_pci memory hacks"). As this device has low amount of RAM, switch
to ath-10k-ct small buffers variant, to avoid the OOM Reaper.
Signed-off-by: Tomasz Maciej Nowak
On 10/01/2020 15:27, Dainis Jonitis wrote:
When available, use 64-bit byte counters rx/tx_bytes64. New 32-bit
counters rx/tx_bytes32 are guaranteed to clamp to max 32-bit value
and never wrap around. For compatibility with legacy clients the old
values rx/tx_bytes are just aliases of new
Merged into my staging tree at
http://git.openwrt.org/?p=openwrt/staging/jow.git.
Thank you!
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The 'DEFAULT:=m if ALL' line prevents the phase1 buildbots from building
the package, and users from downloading it, since they use 'ALL_KMODS=y'
but 'ALL' is not set.
Signed-off-by: Eneas U de Queiroz
--
This was reported here: https://github.com/openwrt/packages/issues/10987
This should be
Commit a5af33ce9a16 ("instance: strdup string attributes") has
introduced duplication of various string attributes in order to fix
use-after-free, but missed handling of `pidfile` and `seccomp` attribute
cases in instance_config_move() where the new value of `pidfile` or
`seccomp` is being
In hopes of guiding this conversation toward the forum, I reposted Nishant
Sharma's comment there...
https://forum.openwrt.org/t/help-pre-select-new-openwrt-project-logo-in-the-poll/52674/9
> On Jan 15, 2020, at 12:00 AM, Nishant Sharma wrote:
>
> Hi Petr,
>
> On 14/01/20 4:57 PM, Petr
Hi Petr,
thanks for reviewing and fixing this!
On Wed, Jan 15, 2020 at 11:30:57AM +0100, Petr Štetiar wrote:
> Commit a5af33ce9a16 ("instance: strdup string attributes") has
> introduced duplication of various string attributes in order to fix
> use-after-free, but missed handling of one
Fixes `removed` to proper `remove` in "Failed to removed pidfile".
Fixes: b12bb150ed38 ("procd: service: Support writing pidfiles")
Signed-off-by: Petr Štetiar
---
service/instance.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/service/instance.c b/service/instance.c
Commit a5af33ce9a16 ("instance: strdup string attributes") has
introduced duplication of various string attributes in order to fix
use-after-free, but missed handling of one `pidfile` attribute case in
instance_config_move() where the new value of `pidfile` is being
copied/assigned. Source of this
f2fs max label length is 1024B (512 * uint16_t) which is way above
current 256B used in `struct blkid_struct_probe` which renders labels on
f2fs system unusable:
$ mkfs.f2fs -l drive /dev/sda1
$ block info /dev/sda1
label buffer too small 1024 > 255
So increase the label buffer again in order
25 matches
Mail list logo
