staging/stintel/package/firmware, branch master

ath79: fix 5 GHz radio on TP-Link Archer C60 v3

2026-09-10T08:14:12Z

Add the QCA9888 calibration variant and its board-specific ipq-wifi package to the device image. Without this, ath10k requests the generic board ID 20 entry, which is absent from ath10k-board-qca9888, and fails to probe. Signed-off-by: Shivansh Saini Co-authored-by: Cursor Link: https://github.com/openwrt/openwrt/pull/25110 Signed-off-by: Robert Marko

ipq-wifi: update to Git HEAD (2026-09-10)

2026-09-10T08:12:10Z

49ab6793662a ipq5018: add BDFs for Wallys DR5018S 04dff0ab979f qca9888: add BDF for TP-Link Archer C60 v3 Signed-off-by: Robert Marko

qualcommax: add support for TP-Link Archer AX55 v1

2026-09-09T19:16:23Z

TP-Link Archer AX55 v1 is an IPQ5018 Wi-Fi 6 router. Hardware: SoC: Qualcomm IPQ5018 (dual Cortex-A53) RAM: 512 MiB Flash: 128 MiB SPI-NAND (dual firmware slots) Switch: Realtek RTL8367S (5x GbE), 2.5G HSGMII trunk to gmac1 WiFi: IPQ5018 2.4 GHz + QCN6122 5 GHz (ath11k) USB: 1x USB 3.0 port, SuperSpeed, using the IPQ5018 SS uni PHY; the port's 5 V rail is a GPIO-switched regulator wired as the PHY's vdd-supply, the way the MR5500 does it Button: Reset, WPS/Wi-Fi LED: power, LAN, WAN (green/orange), 2.4G, 5G, USB All five front jacks are RTL8367S ports (DSA): blue "WAN" = wan, LAN1-4 = lan1..lan4, over the 2.5G HSGMII trunk. The factory MAC is the "default-mac" file in the tp_data UBIFS volume (there is no raw nvmem cell for it). The volume is attached and mounted read-only during preinit, so board.d assigns the wired MACs (label MAC for lan/eth0, +1 for wan) the usual way and the ath11k caldata hotplug derives the Wi-Fi MACs (+2/+3) from the same mount - the same scheme the mt7981 archer-ax80-v1 uses for its tp_data. gmac1 has no nvmem MAC source, so the DSA conduit is pinned to the label MAC in board.d to keep it stable across boots. The board data files live in firmware_qca-wireless, where they were merged as f2c37a6b9d1d; this commit pins the ipq-wifi package to that revision and adds the package entry for the board. Note on revisions: some units labelled "v1" carry an RTL8367D-family switch (chip id 0x6642) instead of the RTL8367S. rtl8365mb cleanly declines it ("unrecognized switch"), so such a unit boots with no wired ports, and with Wi-Fi off by default it is only reachable via the vendor web recovery (or serial). RTL8367D support in rtl8365mb is being worked on by others; until it lands the wiki page carries a prominent warning to identify the switch before flashing. v2/v4 are entirely different hardware and are not covered by this image. Installation (serial console on the JP1 header, 115200 8N1, 1.8 V; note the RX trace is gapped and must be bridged to type): interrupt U-Boot, TFTP-boot the initramfs image to 0x44000000, "bootm", then "sysupgrade -n". A serial-free path (a telnet-enabled resigned stock image flashed from the vendor web UI, then writing the OpenWrt image to the inactive slot) is documented on the device wiki page; that path consumes the initramfs-factory.ubi artifact, which is the initramfs kernel wrapped in a UBI image so it can be written straight into the inactive rootfs partition with mtd from the running stock firmware. Recovery to stock: hold Reset while powering on, set the PC to 192.168.0.10, and upload an official signed TP-Link image at http://192.168.0.1. Signed-off-by: Stanislaw Pal Co-Authored-By: Claude Opus 5 Link: https://github.com/openwrt/openwrt/pull/24197 Signed-off-by: Robert Marko

ipq-wifi: update to Git HEAD (2026-08-26)

2026-09-07T10:23:38Z

c9c7cd8142ac ipq8074: add Netgear RBK850 BDF Signed-off-by: Piotr Szczepanik Link: https://github.com/openwrt/openwrt/pull/24906 Signed-off-by: Robert Marko

linux-firmware: mark aeonsemi-as21xxx-firmware as 'nonshared'

2026-09-03T11:19:18Z

In order for the firmware package to depend on the corresponding kmod it needs to be built within the same builtbot phase for the dependency to land in the package metadata. Select 'nonshared' to force the firmware to also get built as part of phase1. Fixes: 1446eff887 ("mediatek: filogic: bpi-r4-pro-8x: add aeonsemi phy to bpi-r4-pro-8x") Signed-off-by: Daniel Golle

mediatek: filogic: bpi-r4-pro-8x: add aeonsemi phy to bpi-r4-pro-8x

2026-09-01T15:58:57Z

Add the two external Aeonsemi AS21xxx PHYs used by the LAN and WAN 10GBASE-T ports of the BPI-R4 Pro 8x. Configure their firmware, reset timing and LEDs, and connect them to the MxL switch and GMAC1. Replace the fixed SFP GPIO hog configuration with LAN and WAN overlays selecting either the copper PHY or the corresponding SFP cage. Build all four overlays, include them in the device image and select the SFP overlays by default through U-Boot `bootconf_extra`. Make the AS21xxx firmware package pull in the PHY driver on Linux 6.18, instead of making the driver depend on the firmware. Update existing Airoha device package lists accordingly so they continue to install both components through the firmware package. Breaking change for users using the router with SFP hogs from PR #21083. After flashing the new image, configure `bootconf_extra` to select between SFP or PHY overlays: fw_setenv bootconf_extra \ mt7988a-bananapi-bpi-r4-pro-8x-lan-phy#mt7988a-bananapi-bpi-r4-pro-8x-wan-phy If bootconf_extra had additional overlays (CN13 or CN14) keep them appended Signed-off-by: Pietro Ameruoso Signed-off-by: Frank Wunderlich

qualcommbe: add support for Askey SBE1V1K

2026-08-23T16:07:01Z

This commit adds support for Askey SBE1V1K. Device specification -------------------- SoC: Qualcomm IPQ9570 RAM: Micron (2GB) Flash: 8GB eMMC Ethernet: 1x 10G RTL8261BE 1x 2.5G QCA8081 2x 1G QCA8075 Wi-Fi: QCN6214 2.4GHz 4x4 QCN6274 5GHz 4x4 QCN6274 6GHz 4x4 LEDs: 1 LED, power/status Buttons: 1 reset USB ports: none Bootloader: U-Boot 1.0.9 [spf12.2_CSU2] (Jun 28 2024 - 17:47:10 +0000) Installation (serial required): **NOTE** This procedure requires glitching the eMMC. It is very possible that you may damage or corrupt your bootloader in doing so. Proceed with caution, and always make a full eMMC backup! **NOTE** If the bootloader has trouble accessing eMMC due to glitching it, any U-Boot env updates are written directly to the start of flash, overwriting the bootloader. For this reason, it is strongly NOT recommended to make any persistent U-Boot env changes from U-Boot itself; do this in Linux. - Open the chasis and connect to the serial port. - While booting, short eMMC CLK to UART VCC during FIT image load to enter U-Boot. - setenv ipaddr 192.168.1.1 - setenv serverip 192.168.1.2 **NOTE** DO NOT SAVE THE ENV - Set your PC IP address to 192.168.1.2 and host the initramfs on a tftp server. - tftpboot 0x44000000 initramfs.itb - bootm 0x44000000 If you get an error and it reboots, try loading to 0x80000000. In the initramfs: - fw_setenv bootargs 'console=ttyMSM0,115200n8 rootwait root=/dev/mmcblk0p27' - fw_setenv bootcmd 'echo "Hit ctrl+c for shell..."; if sleep 3; then run do_boot; else do_nothing; fi;' - fw_setenv do_boot 'mmc read 0x44000000 0x00014022 0x3800; bootm 0x44000000' - Install a sysupgrade U-Boot hardcodes the bootargs to reset on each boot, which is why it is necessary for the bootcmd to override them. Thankfully, the vendor did not bother to secure U-Boot any further. As long as the vendor software does not boot, the U-Boot env will stay. If a vendor image boots, the U-Boot env will revert to default. The vendor U-Boot also ignores bootdelay, which is why we add a dummy sleep to allow the user time to drop into a shell without needing to glitch any more. Co-authored-by: Kenneth Kasilag Signed-off-by: Andrew LaMarche Link: https://github.com/openwrt/openwrt/pull/21586 Signed-off-by: Robert Marko

ipq-wifi: update to Git HEAD (2026-08-23)

2026-08-23T16:04:56Z

0c67bbcca45f qnc9274: add Askey SBE1V1K BDF + regdb Signed-off-by: Robert Marko

qualcommax: ipq60xx: add support for tp-link eap620hd-v2

2026-08-15T09:14:55Z

TP-Link EAP620HD V2 is a 802.11ax AP claiming AX1800 support. Specifications: CPU: Qualcomm IPQ6018 Quad core Cortex-A53 RAM: 1 GB Storage: ESMT PSR1GA30DT 128MB NAND Ethernet: Gigabit RJ45 port with PoE input WLAN: 2.4GHz/5GHz LEDs: Single-color LED (Blue) Buttons: 1x Reset UART: 4-pin unpopulated header 1.8 V level, Pinout 1 - TX, 2 - RX, 3 - GND, 4 - 1.8V Installation: Web UI method Set up the device using the vendor's web UI. After that go to Management->SSH and enable the "SSH Login" checkbox. Select "Save". The connect to the machine via SSH: ssh -o hostkeyalgorithms=ssh-rsa Disable signature verification: cliclientd stopcs Rename the "-web-ui-factory" image to something less than 63 characters, maintaining the ".bin" suffix. Go to System -> Firmware Update. Under "New Firmware File", click "Browse" and select the image Select "Update" and confirm by clicking "OK". If the update fails, the web UI should show an error message. Otherwise, the device should reboot into OpenWRT. TFTP method To flash via tftp, first place the initramfs image on the TFTP server. setenv serverip setenv ipaddr tftpboot tplink_eap620-hd-v2-initramfs-uImage.itb bootm This should boot OpenWRT. Once booted, flash the sysupgrade.bin image using either luci or the commandline. Big thanks to @mrnuke for the groundwork and support. Signed-off-by: Ryan S Link: https://github.com/openwrt/openwrt/pull/18227 Signed-off-by: Robert Marko

ipq-wifi: update to Git HEAD (2026-08-15)

2026-08-15T09:14:28Z

ec3c6fec867e ipq6018: add TP-Link EAP620 HD v2 BDF with corrected variant and remove old board ref Signed-off-by: Robert Marko