staging/stintel/include, branch master

base-files: add warning to distfeeds.list

2026-04-15T08:03:10Z

Add a message to the apk distfeeds.list that changes won't be saved and that users should modify customfeeds.list instead. Signed-off-by: Eric Fahlgren Link: https://github.com/openwrt/openwrt/pull/22586 Signed-off-by: Robert Marko

filogic: add support for D-Link AQUILA PRO AI E30

2026-04-12T23:52:29Z

Specification: The device is similar to the M30 but has only one LAN port and no WAN port. - MT7981 CPU using 2.4GHz and 5GHz WiFi (both AX) - 512MB RAM - 128MB NAND flash with two UBI partitions with identical size - 1 multi color LED (red, green, blue, white) connected via GCA230718 - 2 buttons (WPS, reset, LED) - 1 1Gbit LAN port Disassembly: - There are two screws at the power connector which must be removed. Afterwards the top case can be removed (it is clipped on, so some tools are required). Serial Interface: - The serial interface can be connected to the 4 pin holes on the board. Do NOT connect VCC. - The pins are labelled on the PCB (RX, TX, GND) - Settings: 115200, 8N1 MAC addresses: - LAN MAC is stored in partition "Odm" at offset 0x8f - WLAN MAC (2.4 GHz and 5GHz) is LAN MAC + 1 Reverting back to OEM firmware: - There is currently no easy way to revert back to the OEM image - The methods from M30 and M60 doesn't seem to work anymore - If you plan to revert back to OEM firmware later, do the following steps before flashing OpenWrt: - Boot from initramfs as described in "Flashing via U-Boot" but don't flash anything - Instead, make a backup of UBI and UBI1 partition - The created dumps must be written to the initial partitions to revert back to OEM Flashing via Recovery Web Interface: - Set your IP address to 192.168.200.10, subnetmask 255.255.255.0 - Press the reset button while powering on the device - Keep the reset button pressed until the LED blinks red - Open a Chromium based and goto http://192.168.200.50/ (recovery web interface) - Download openwrt-mediatek-filogic-dlink_aquila-pro-ai-e30-a1-squashfs-recovery.bin - Note: The recovery web interface always reports successful flashing, even if it fails - After flashing, the recovery web interface will try to forward the browser to 192.168.0.1 (can be ignored) - If flashing was successful, OpenWrt is accessible via 192.168.1.1 - The recovery image boots an initramfs image, flash the sys upgrade image to get to „normal“ OpenWrt mode Flashing via U-Boot: - Open the case, connect to the UART console - Set your IP address to 192.168.200.2, subnet mask 255.255.255.0. Connect to one of the LAN interfaces of the router - Run a tftp server which provides openwrt-mediatek-filogic-dlink_aquila-pro-ai-e30-a1-initramfs-kernel.bin - Supply the board with 12V - Select "7. Load image" in the U-Boot menu - Enter image file, tftp server IP and device IP (if they differ from the default). - TFTP download to RAM will start. After a few seconds OpenWrt initramfs should start - The initramfs is accessible via 192.168.1.1, change your IP address accordingly (or use multiple IP addresses on your interface) - Perform a sysupgrade using openwrt-mediatek-filogic-dlink_aquila-pro-ai-e30-a1-squashfs-sysupgrade.bin - Reboot the device. OpenWrt should start from flash now Flashing via OEM web interface is not possible, as it will change the active partition and OpenWrt is only running on the first UBI partition. Signed-off-by: Roland Reinl Link: https://github.com/openwrt/openwrt/pull/22776 Signed-off-by: Hauke Mehrtens

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

kernel.mk: add 6.18 workaround for empty Module.symvers.tmp

2026-03-28T10:51:10Z

On Linux 6.18 the path-based symvers filter can yield an empty tmp file for external modules. Add a 6.18-only fallback using modules.order to populate Module.symvers.tmp. Signed-off-by: Til Kaiser Link: https://github.com/openwrt/openwrt/pull/21078 Signed-off-by: Robert Marko

config: add build config option to sign each .apk package

2026-03-02T10:08:10Z

Add a build config option to sign each individual .apk package. If individual .apk files are signed with the build key, they can be installed with 'apk add' without '--allow-untrusted' to a firmware compiled by the same buildhost. Enable the option by default, but disable it for BUILDBOT. (At the moment, since commit 084697e, only the package index is signed, which forces users to use '--allow-untrusted' when installing self-built .apk files.) Signed-off-by: Hannu Nyman

targets: add REGULATOR_SUPPORT auto-feature

2026-03-01T09:59:19Z

Not all targets need regulator support, so they dont enable it as its disabled in the generic config by default. So, in order to allow kernel modules to depend on regulator support lets add a new feature flag "regulator" and set it automatically if target kernel config enables CONFIG_REGULATOR. Link: https://github.com/openwrt/openwrt/pull/22172 Signed-off-by: Robert Marko

build: pass CPPFLAGS to cmake build

2026-02-17T00:29:57Z

The TARGET_CPPFLAGS contain the include paths used by OpenWrt. This also contains the including of the fortify sources headers. If they are not provided, the applications will not use fortify sources headers when compiled against musl. Add them to cmake builds too. cmake does not support a special CPPFLGS option [0], just add them to CFLAGS and CXXFLAGS like we also do it for meson and normal make. This should fix fortify sources support for cmake builds. I found this explanation for the flags: * CFLAGS: C flags, passed during compile AND link * CXXFLAGS: C++ flags, passed during compile AND link * CPPFLAGS: pre-processor flags, passed ONLY during compile * LDFLAGS: linker flags, passed ONLY during link [0]: https://gitlab.kitware.com/cmake/cmake/-/issues/12928 Link: https://github.com/openwrt/openwrt/pull/22042 Signed-off-by: Hauke Mehrtens

treewide: drop CVS support

2026-02-13T14:40:13Z

We have no CVS-managed package in official repositories. This commit drops obsolete SCM system support. Signed-off-by: Yanase Yuki Link: https://github.com/openwrt/openwrt/pull/21340 Signed-off-by: Robert Marko

image: support generating per device targz rootfs

2026-02-09T15:43:29Z

Currently, for targets that use the CONFIG_TARGET_ROOTFS_TARGZ a single rootfs tarball is generated for the subtarget based of $(TARGET_DIR). However, this means that it does not respect DEVICE_PACKAGES like other rootfs images. So, lets augment CONFIG_TARGET_ROOTFS_TARGZ by adding a proper targz fstype so that per device rootfs is generated under lock. This is required so that devices that use custom sysupgrade archives like Methode devices, can actually include a per device rootfs so when building for multiple devices and with CONFIG_TARGET_PER_DEVICE_ROOTFS set the built image actually includes the listed DEVICE_PACKAGES. Signed-off-by: Robert Marko

package-pack: fix Ubuntu 18.04 compilation

2026-02-07T23:23:13Z

Add \ to fix parsing with make 4.1. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/21910 Signed-off-by: Hauke Mehrtens