staging/stintel/package/boot, branch master

mpc85xx: ws-ap3715i: enable access to u-boot env

2026-05-05T12:09:38Z

find_mtd_part() outputs /dev/mtdblockX, to which fw_setenv cannot write, "/dev/mtd$(find_mtd_index '')" could be used instead. The envsize should also be changed to 0x1000 to make the CRC checksum valid and the env block recognized by the uboot-envtools, but the flash sector size remains 0x10000, otherwise the env block will be readable but not writable. The "read-only" mark within device tree is also removed. Signed-off-by: Edward Chow Link: https://github.com/openwrt/openwrt/pull/23121 Signed-off-by: Robert Marko

uboot-tools: envtools: add support for ELECOM WRC-X6000GSD

2026-05-02T23:14:11Z

Add support for ELECOM WRC-X6000GSD, to update U-Boot environment variables. Signed-off-by: INAGAKI Hiroshi Link: https://github.com/openwrt/openwrt/pull/22926 Signed-off-by: Hauke Mehrtens

uboot-tools: envtools: add support for ELECOM WRC-X6000QS

2026-05-02T23:14:11Z

Add support for ELECOM WRC-X6000QS, to update U-Boot environment variables. Signed-off-by: INAGAKI Hiroshi Link: https://github.com/openwrt/openwrt/pull/22926 Signed-off-by: Hauke Mehrtens

uboot-at91: fix wrong BUILD_DEVICES for sama5d4_xplained_nandflash

2026-04-20T16:07:56Z

The sama5d4_xplained_nandflash target incorrectly references microchip_sama5d3-xplained as its BUILD_DEVICES value. This appears to be a copy-paste error, as all other SAMA5D4 Xplained targets (e.g. mmc and spiflash) correctly use microchip_sama5d4-xplained. The target name itself also clearly refers to the SAMA5D4 platform. In addition, the SAMA5D3 Xplained and SAMA5D4 Xplained boards use different NAND flash hardware and configurations, so pointing the nandflash target to a SAMA5D3 device is incorrect and may lead to invalid builds or runtime issues. Fix the inconsistency by updating BUILD_DEVICES to microchip_sama5d4-xplained, aligning the nandflash target with the rest of the SAMA5D4 definitions and ensuring the correct device mapping. Signed-off-by: Cerrone Diamant Link: https://github.com/openwrt/openwrt/pull/23022 Signed-off-by: Robert Marko

treewide: use HTTPS for PKG_SOURCE_URL where possible

2026-04-20T03:58:37Z

Switch http:// (and redundant ftp://) PKG_SOURCE_URL entries to https:// across tools/ and package/. PKG_HASH alone does not protect against an attacker tampering with insecure downloads when a maintainer regenerates the hash via `make ... FIXUP=1`: HTTPS authenticates the upstream so the captured hash reflects real upstream content. In-place http -> https (HTTPS reachability verified per host): - tools/elftosb, tools/lzop, tools/liblzo, tools/mpfr, tools/dosfstools, tools/libressl, tools/xz - package/libs/mpfr, package/libs/libmnl, package/libs/libnfnetlink Replaced with @OPENWRT (HTTPS-only mirror) where the upstream HTTPS host is dead or has a broken certificate: - package/libs/popt (ftp.rpm.org cert mismatch) - package/firmware/ixp4xx-microcode (was http://downloads.openwrt.org) - package/boot/imx-bootlets (trabant.uid0.hu cert mismatch) - package/boot/kobs-ng (freescale.com URL is dead, redirects to nxp.com root) Dropped redundant ftp://ftp.denx.de fallback (https://ftp.denx.de is already listed): - package/boot/uboot-tools, tools/mkimage Signed-off-by: Paul Spooren

treewide: remove references for obsolete binutils versions

2026-04-18T17:34:21Z

Support for obsolete versions was dropped in upstream commit 72731b445ee3. Signed-off-by: Konstantin Demin Link: https://github.com/openwrt/openwrt/pull/21997 Signed-off-by: Nick Hainke

uboot-tools: envtools: add support for BUFFALO WSR-3000AX4P

2026-04-16T20:48:57Z

Add support for BUFFALO WSR-3000AX4P, to allow updating environment variables of U-Boot on that device. Signed-off-by: INAGAKI Hiroshi Link: https://github.com/openwrt/openwrt/pull/22587 Signed-off-by: Hauke Mehrtens

uboot-envtools: add extreme-networks,ws-ap3805i

2026-04-16T19:20:01Z

This device has a redundant configuration. Important when writing to it. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/22882 Signed-off-by: Robert Marko

uboot-tools: fix libyaml linker error

2026-04-14T17:17:47Z

When we cross build uboot-tools, the dtc tool is still compiled for the host. Therefore, we should not attempt to link the OpenWrt system libraries. CPU architecture mismatch can lead to build errors. Fixes: https://github.com/openwrt/openwrt/issues/22924 Fixes: 55925650aabb ("uboot-tools: update to v2026.04") Signed-off-by: Shiji Yang Link: https://github.com/openwrt/openwrt/pull/22927 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