Re: [PATCH v1 0/5] Resurrect IXP4xx

2023-06-19 Thread Raylynn Knight via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- > On Jun 19, 2023, at 7:31 AM, Li

Recall: mwan3 memory usage

2023-06-19 Thread Ravi Paluri
Ravi Paluri would like to recall the message, "mwan3 memory usage". ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

mwan3 memory usage

2023-06-19 Thread Ravi Paluri (QUIC)
Thanks, Florian for the reply. In our opinion, having single process to cater to both IPv4 and IPv6 would help in memory reduction, the same way as handled in mwan3 (version 2.8.16). This would reduce the memory footprint from 4 processes to 2 processes. Do you recommend we making changes to mwan

[PATCH v1 2/5] ixp4xx: Resurrect IXP4xx support using device tree

2023-06-19 Thread Linus Walleij
This resurrects the support for IXP4xx using device tree rather than the old (deleted) board files. The final pieces of IXP4xx board files were deleted in Linux v5.19. Ext4 root filesystems on CF and USB are supported by the default config. We support these three initial targets: - The Gateworks

[PATCH v1 0/5] Resurrect IXP4xx

2023-06-19 Thread Linus Walleij
IXP4xx was deleted because of lack of maintenance in 2020. In the years since, the upstream Linux support for IXP4xx has been rewritten from scratch. It is not pretty well supported using device tree and such. With the switch to kernel v6.1, OpenWrt has the required baseline to bring IXP4xx back.

[PATCH 1/5] boot/apex: Restore the APEX boot loader

2023-06-19 Thread Linus Walleij
This is a partial revert of the deletion of the IXP4xx target: we restore the APEX boot loader so we can use it for the NSLU2 and related targets. The APEX upstream is as dead as it gets so I have applied OpenWrts old patches on top of the never released v1.6.10 version and forked it into an OpenW

[PATCH v1 3/5] ixp4xx: Add a ixp4xx hardware crypto kernel module

2023-06-19 Thread Linus Walleij
The IXP4xx crypto module must be loaded after the rootfs is up as it depends on loading some NPE microcode from the file system. Signed-off-by: Linus Walleij --- package/kernel/linux/modules/crypto.mk | 13 + target/linux/ixp4xx/Makefile | 1 + 2 files changed, 14 insertio

[PATCH v1 5/5] Delete arm-magic script

2023-06-19 Thread Linus Walleij
This script was used to modify the wrong machine type passed from the boot loader to the kernel. The device tree kernels does not use the machine type so this script is no longer needed. Signed-off-by: Linus Walleij --- scripts/arm-magic.sh | 42 -- 1 file

[PATCH v1 4/5] ixp4xx: Add hdparm script

2023-06-19 Thread Linus Walleij
This script will make sure to spin down harddrives on IXP4xx NAS devices such as the NSLU2 and siblings after 1 minute of inactivity. Signed-off-by: Linus Walleij --- .../linux/ixp4xx/base-files/etc/board.d/03_hdparm | 14 ++ 1 file changed, 14 insertions(+) create mode 100644 targ

Re: [PATCH-22.03 01/10] ipq40xx: Support Chromium OS image-type creation

2023-06-19 Thread Petr Štetiar
open...@aiyionpri.me [2023-04-07 15:23:39]: Hi Jan, > This series intends to support Google WiFi device 'Gale'. IMHO it screams "a lot of regressions" in exchange for adding support for a _single_ device into sixth stable release of 22.03, and considering that we've 23.05 already in the works,

RE: mwan3 memory usage

2023-06-19 Thread Ravi Paluri
Thanks, Florian for the reply. In our opinion, having single process to cater to both IPv4 and IPv6 would help in memory reduction, the same way as handled in mwan3 (version 2.8.16). This would reduce the memory footprint from 4 processes to 2 processes. Do you recommend we making changes to mwan