staging/stintel/package/base-files, branch master

base-files: add mtd_get_mac_uci_config()

2026-08-11T21:18:26Z

Add mtd_get_mac_uci_config() for reading a MAC address from a UCI-style config stored in an MTD partition. This is needed to support the TP-Link ER605 v1; the existing UBI helper already covers the ER605 v2. Also refactor common sed logic into a shared helper used by both variants and drop the redundant cat pipe. TP-Link ER605 v2 device support is unaffected. The one and only MAC address on the tddp partition for v1/v2 is the label MAC address. Signed-off-by: Charles Joynson Link: https://github.com/openwrt/openwrt/pull/24331 Signed-off-by: Jonas Jelonek

base-files: fix missing tabs

2026-07-26T16:02:42Z

Tabs were missing from the default button behavior modification blocks, breaking the build if they were activated. Signed-off-by: David Bauer

wifi-scripts: support multiple device paths per board.json wlan entry

2026-07-22T07:32:52Z

The path field of a board.json wlan entry may now be an array of device paths. ucidef_add_wlan accepts several leading path arguments and stores them as a JSON array; a single path is still stored as a plain string for backwards compatibility. A phy is matched if it corresponds to any of the listed paths, so a radio that enumerates on a non-deterministic PCI path still resolves to the correct named phy. Signed-off-by: Felix Fietkau

base-files: derive DHCP DUID from device MAC address

2026-06-24T09:21:28Z

The DUID-UUID was generated from a random UUID, which is regenerated on every fresh flash and therefore does not survive reconfiguration events such as reflashing without keeping the configuration. RFC8415/RFC6355 prefer a DUID that remains stable across such events. Add a ucode helper that picks the first LAN port (falling back to WAN) from /etc/board.json, resolves its MAC address and derives a stable UUID from it, falling back to a random UUID only when that fails. Signed-off-by: Felix Fietkau

base-files: handle name collision between kernel UBI volume and MTD partition

2026-06-16T14:07:58Z

On the AP-325 (and variants), the bootloader enforces a particular UBI volume layout and naming, so unfortunately the kernel's UBI volume and MTD partition end up with the name, which confuses the current logic. Therefore, add an option to ignore the MTD partition. Signed-off-by: Lukas Stockner Link: https://github.com/openwrt/openwrt/pull/20738 Signed-off-by: Paul Spooren

base-files: support rootfs_data on its own partition

2026-06-16T14:07:48Z

The current code assumes that the rootfs_data UBI volume is on the same MTD partition as the rootfs. Unfortunately, this does not work on the Aruba AP-325 (and variants), since the bootloader enforces a particular UBI volume layout. Therefore, this adds a separate variable to set the rootfs_data partition, and updates all existing devices with a non-default rootfs partition to also specify the new variable. Signed-off-by: Lukas Stockner Link: https://github.com/openwrt/openwrt/pull/20738 Signed-off-by: Paul Spooren

Revert "base-files: support rootfs_data on its own partition"

2026-06-16T14:05:25Z

This reverts commit 13fc688f033895e0ba91c1d752ffd63a06760ef5. Wrong Signed-off-by line was used, reverting and re-applying. Signed-off-by: Paul Spooren

Revert "base-files: handle name collision between kernel UBI volume and MTD partition"

2026-06-16T14:05:23Z

This reverts commit eef8c718b474aff652b42c2e96b55b1b310f7f56. Wrong Signed-off-by line was used, reverting and re-applying. Signed-off-by: Paul Spooren

base-files: handle name collision between kernel UBI volume and MTD partition

2026-06-16T11:45:44Z

base-files: support rootfs_data on its own partition

2026-06-16T11:45:44Z