staging/stintel, branch master

realtek: add RTL8224 initialization to Realtek driver

2026-04-08T16:46:32Z

Adds an initialization sequence for the RTL8224. It relies a lot on magic values, however it explicitely initializes the SerDes part of the chip. Signed-off-by: Damien Dejean Link: https://github.com/openwrt/openwrt/pull/22609 Signed-off-by: Robert Marko

realtek: pcs: rtl930x: enable USXGMII-QX configuration

2026-04-08T16:46:32Z

The RTL8224 driver now puts the PHY into the proper mode, but the SerDes side is still missing. It was deactivated due to a known regression. Thus, allow USXGMII-QX configuration since both sides should be properly configured now. Signed-off-by: Jonas Jelonek Link: https://github.com/openwrt/openwrt/pull/22609 Signed-off-by: Robert Marko

treewide: strip trailing whitespace

2026-04-08T08:05:53Z

Strip trailing whitespace in all code: find . -type f | grep "\.c$" | xargs sed -i 's/[ \t]\+$//' find . -type f | grep "\.h$" | xargs sed -i 's/[ \t]\+$//' find . -type f | grep "\.dts$" | xargs sed -i 's/[ \t]\+$//' find . -type f | grep "\.dtsi$" | xargs sed -i 's/[ \t]\+$//' Signed-off-by: Mieczyslaw Nalewaj Link: https://github.com/openwrt/openwrt/pull/22840 Signed-off-by: Christian Marangi

mediatek: filogic: fix EAX17 rootfs hash in FIT node for per-device rootfs builds

2026-04-08T08:02:58Z

When CONFIG_TARGET_PER_DEVICE_ROOTFS is enabled (as in buildbot builds), the final per-device rootfs is assembled at root.squashfs+pkg= rather than root.squashfs. The gen_netgear_rootfs_node.sh script was always hashing root.squashfs (the base rootfs without device-specific packages), causing the size and hash in the FIT node to not match the actual rootfs written to the UBI volume, resulting in boot failure on buildbot-produced images. Fix by using the per-device rootfs path when TARGET_PER_DEVICE_ROOTFS is set, consistent with how include/image.mk handles the same distinction elsewhere. Fixes: 46ab9f3f1c ("filogic: add support for Netgear EAX17") Signed-off-by: Jascha Sundaresan Link: https://github.com/openwrt/openwrt/pull/22839 Signed-off-by: Christian Marangi

build: set max-page-size linker flag to match target page size

2026-04-07T22:34:59Z

ELF binaries embed the maximum page size used during linking in the PT_LOAD segment alignment. If this value is larger than the actual system page size, the kernel will still load the binary but wastes memory due to over-alignment. If it is smaller, the binary may fail to load or cause incorrect behavior with features like RELRO. Most architectures use 4KB pages, but loongarch64 uses 16KB pages (CONFIG_PAGE_SIZE_16KB). Explicitly pass -z max-page-size to the linker so that binaries are built with the correct page alignment for the target, avoiding issues with RELRO segment padding and ensuring correct memory mapping on the target system. Before binutils 2.39 RELRO sections were padded to common page size which is 4K on MIPS, with binutils 3.29 the padding was changed to max page size which is 64K on MIPS. With this change we will pad them to 4K again. This reduces the size of user space binaries in OpenWrt. The size of the uncompressed root file system of a mips malta be build decreased by about 20%. old file size: ``` $ du -s build_dir/target-mips_24kc_musl/root-malta/ 15844 build_dir/target-mips_24kc_musl/root-malta/ ``` New file size: ``` $ du -s build_dir/target-mips_24kc_musl/root-malta/ 12564 build_dir/target-mips_24kc_musl/root-malta/ ``` The size of the image did not decrease much because of the strong compression used by OpenWrt. Link: https://github.com/openwrt/openwrt/pull/22800 Signed-off-by: Hauke Mehrtens

uboot-mediatek: bpi-r4-lite fix emmc frequency

2026-04-07T22:17:56Z

Use lower emmc frequency. This fix issue when mmc write, from uboot, failed. Failed case: - we boot from NAND - choose "Install bootloader, recovery and production to eMMC" MMC erase: dev # 0, block # 0, count 1024 ... 1024 blocks erased: OK MMC write: dev # 0, block # 0, count 1024 ... mmc write failed 0 blocks written: ERROR Signed-off-by: Janusz Dziedzic Link: https://github.com/openwrt/openwrt/pull/22615 Signed-off-by: Hauke Mehrtens

ramips: refresh patches

2026-04-07T22:01:20Z

Refreshed patches by running: make target/linux/refresh Signed-off-by: Mieczyslaw Nalewaj Link: https://github.com/openwrt/openwrt/pull/22810 Signed-off-by: Hauke Mehrtens

ramips: restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 for 6.18

2026-04-07T22:00:24Z

Restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 in ramips 6.18 config fragments to fix build failures where PAGE_BLOCK_MAX_ORDER was undefined. Support for Linux 6.18 on ramips was added after this OpenWrt change: https://github.com/openwrt/openwrt/commit/ac0cb87a453698efc6c812e4f27cadbeb208f14e. Before that integration, the kernel option CONFIG_PAGE_BLOCK_MAX_ORDER=10 was provided in target/linux/generic/config-6.18 and applied broadly. After the ramips 6.18 integration the generic fragment no longer supplied this option for ramips targets, which caused some backported code paths and drivers to assume PAGE_BLOCK_MAX_ORDER was defined and led to compilation failures. Signed-off-by: Mieczyslaw Nalewaj Link: https://github.com/openwrt/openwrt/pull/22831 Signed-off-by: Hauke Mehrtens

tools/cmake: update to 4.3.1

2026-04-07T21:01:22Z

Release notes:https://cmake.org/cmake/help/latest/release/4.3.html Refresh patches: - 130-bootstrap_parallel_make_flag.patch - 150-zstd-libarchive.patch - 160-disable_xcode_generator.patch Signed-off-by: Jack Sun Link: https://github.com/openwrt/openwrt/pull/22693 Signed-off-by: Robert Marko

mediatek: device tree overlay for BPI-R4 with BE14 module

2026-04-07T18:38:07Z

Some Banana Pi BPI-R4 BE14 WiFi modules are shipped with zeroed tx_power fields in EEPROM (2G/5G/6G). This leads to low transmit power on affected bands. This overlay provides known-good EEPROM data (including correct tx_power values for 2G/5G/6G bands) dumped from a working BE14 module. To enable BE14 overlay, add into u-boot bootconf_extra parameter: 'mt7988a-bananapi-bpi-r4-wifi-be14'. You can use example script: overlay="mt7988a-bananapi-bpi-r4-wifi-be14" current="$(fw_printenv -n bootconf_extra 2>/dev/null)" if [ -n "${current}" ]; then fw_setenv bootconf_extra "${current}#${overlay}" else fw_setenv bootconf_extra "${overlay}" fi Earlier proposal proposed in [1] was fallback to default values if invalid EEPROM content is detected. [1] https://github.com/openwrt/openwrt/pull/19503/ Fixes: https://github.com/openwrt/openwrt/issues/17489 Signed-off-by: Daniel Pawlik