BUILD_CFG_DISTCLEANtrue開始前に <code>make distclean</code> を実施BUILD_CFG_DISTCLEANBooleanParameterDefinitionBUILD_CFG_DIFFCONFIGtruediffconfigを使用してビルドBUILD_CFG_DIFFCONFIGBooleanParameterDefinitionBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)ビルド対象機種系統BUILD_CFG_TARGET_DEVChoiceParameterDefinitionWR8750N/WR9500N/WG600HP (AR9344)WG1400HP/WG1800HP/WG1800HP2 (QCA9558)https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/<p>OpenWrt main for NetBSD based NEC Aterm series routers:</p>
<p>NECのBootloaderからinitramfs-factory.binブート可</p>
OpenWrt (master) for NEC Aterm (NetBSD based)OpenWrt (master) for NEC Aterm (NetBSD based)OpenWrt (master) for NEC Aterm (NetBSD based)OpenWrt-master-NEC-BSD-AtermOpenWrt-master-NEC-BSD-Atermhttps://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/trueStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WG1400HP/WG1800HP/WG1800HP2 (QCA9558)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWG1400HP/WG1800HP/WG1800HP2 (QCA9558)487fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/generic/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/generic/feeds.buildinfoopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic.manifestopenwrt-ath79-generic.manifestbin/targets/ath79/generic/openwrt-ath79-generic.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/generic/profiles.jsonsha256sumssha256sumsbin/targets/ath79/generic/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/generic/version.buildinfofalsediffconfig: true, device: WG1400HP/WG1800HP/WG1800HP2 (QCA9558)#48734195273023555OpenWrt (master) for NEC Aterm (NetBSD based) #487487falsefalse48752SUCCESS1788751200654https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/487/home-slave02_taihasvgitStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WR8750N/WR9500N/WG600HP (AR9344)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)486fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/tiny/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/tiny/feeds.buildinfoopenwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binopenwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wg600hp-uboot.binopenwrt-ath79-tiny-nec_wg600hp-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-uboot.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr8750n-uboot.binopenwrt-ath79-tiny-nec_wr8750n-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-uboot.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr9500n-uboot.binopenwrt-ath79-tiny-nec_wr9500n-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-uboot.binopenwrt-ath79-tiny.manifestopenwrt-ath79-tiny.manifestbin/targets/ath79/tiny/openwrt-ath79-tiny.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/tiny/profiles.jsonsha256sumssha256sumsbin/targets/ath79/tiny/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/tiny/version.buildinfofalsediffconfig: true, device: WR8750N/WR9500N/WG600HP (AR9344)#48626275833023555OpenWrt (master) for NEC Aterm (NetBSD based) #486486falsefalse48651SUCCESS1788738000597https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/486/home-slave02_taihasv- target/linux/qualcommax/dts/ipq6000-nn6000-v2.dtse5517d856dc802a7bff3899091ea5b0a724dcaad1788428109000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq60xx: enable lan4 port for link nn6000v2
The swport5 node was disabled by mistake during the PPE conversion.
Fixes: f50435627d37 ("qualcommax: ipq60xx/ipq807x: convert to PPE networking stack")
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
Link: https://github.com/openwrt/openwrt/pull/25006
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-03 11:35:09 +0200e5517d856dc802a7bff3899091ea5b0a724dcaadqualcommax: ipq60xx: enable lan4 port for link nn6000v2edittarget/linux/qualcommax/dts/ipq6000-nn6000-v2.dts
- package/network/config/wifi-scripts/files-ucode/lib/netifd/wireless/mac80211.shpackage/network/config/wifi-scripts/Makefilee21a4ef958d8ea1006a0b4a8ebbf0c6a35be95a01788428299000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comwifi-scripts: silence iw antenna/distance failures like shell did
The shell mac80211.sh ran both of these with >/dev/null 2>&1:
iw phy "$phy" set antenna $txantenna $rxantenna >/dev/null 2>&1
iw phy "$phy" set distance "$distance" >/dev/null 2>&1
The ucode rewrite dropped the redirect, so on any driver without
->set_coverage_class every wifi up now logs
netifd: radio0 (3302): command failed: Not supported (-95)
with no indication of which command failed. Neither return value is
checked, so the message is pure noise -- but it reads like wifi up
failed, and on ath12k/IPQ5332 it cost real debugging time before the
line was traced back to iw.c:616 rather than to the driver.
Restore the redirect. distance defaults to 0 and antenna to 0xffffffff,
so both calls run on every setup for every radio.
Signed-off-by: Hideo Sumi <hideo.sumi@mugops.com>
2026-09-03 11:38:19 +0200e21a4ef958d8ea1006a0b4a8ebbf0c6a35be95a0wifi-scripts: silence iw antenna/distance failures like shell dideditpackage/network/config/wifi-scripts/files-ucode/lib/netifd/wireless/mac80211.sheditpackage/network/config/wifi-scripts/Makefile
- package/firmware/linux-firmware/aeonsemi.mk897533e4886e008e994980ea1339cff44e5a405e1788434358000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orglinux-firmware: mark aeonsemi-as21xxx-firmware as 'nonshared'
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 <daniel@makrotopia.org>
2026-09-03 12:19:18 +0100897533e4886e008e994980ea1339cff44e5a405elinux-firmware: mark aeonsemi-as21xxx-firmware as 'nonshared'editpackage/firmware/linux-firmware/aeonsemi.mk
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c1866d1eba79b6f9a6261bcc3e3ffbe28abbf373e1788447634000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl838x: don't clobber adjacent LOG counter
rtl838x_packet_cntr_clear() zeroes one of the two registers that make up
a LOG table entry and then writes the whole entry back without reading it
first, wiping the adjacent counter with whatever stale data is in the
table register cache. Two 32-bit packet counters share one entry, so the
counter next to the one being cleared is lost.
Read the entry before modifying one half, mirroring the same fix already
applied to rtl930x_packet_cntr_clear().
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25005
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 17:00:34 +02001866d1eba79b6f9a6261bcc3e3ffbe28abbf373erealtek: dsa: rtl838x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cd8f9a15a2de22dc5f8644243c8637d66d854c7141788447634000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl839x: don't clobber adjacent LOG counter
rtl839x_packet_cntr_clear() has the same defect as the rtl838x variant:
it zeroes one register of a shared two-register LOG table entry and
writes the entry back without reading it first, so the counter sharing
that entry is overwritten with stale register-cache data.
Read the entry before modifying one half, mirroring the same fix already
applied to rtl930x_packet_cntr_clear().
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25005
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 17:00:34 +0200d8f9a15a2de22dc5f8644243c8637d66d854c714realtek: dsa: rtl839x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- target/linux/mediatek/dts/mt7622-buffalo-wsr-2533dhp2.dtstarget/linux/mediatek/dts/mt7622-elecom-wrc-2533gent.dtstarget/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-versiontarget/linux/mediatek/image/mt7622.mktarget/linux/mediatek/mt7622/config-6.18target/linux/mediatek/mt7622/base-files/etc/board.d/05_compat-versiontarget/linux/mediatek/dts/mt7622-buffalo-wsr.dtsitarget/linux/mediatek/dts/mt7622-totolink-a8000ru.dtstarget/linux/mediatek/mt7622/base-files/etc/board.d/02_network7727479e5f7160391b3eeb2f58244daf360ed1b31788454364000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commediatek: mt7622: convert devices with RTL8367S switch to DSA
Migrate Buffalo WSR-2533DHP2, ELECOM WRC-2533GENT and TOTOLINK A8000RU
from swconfig to DSA. These devices use an external Realtek RTL8367S
switch handled by the rtl8365mb DSA driver.
Per-device changes:
- Drop the proprietary mediatek,rtk-gsw node
- Add realtek,rtl8365mb DSA switch with ports lan1-lan4, wan and CPU
- Move CPU port to gmac0 at 2500base-x (HSGMII)
- Remove gmac1 (was 5u@eth1 in swconfig; DSA uses single CPU port)
- Drop unused rgmii_via_gmac2 pin group
- Replace swconfig with kmod-dsa-rtl8365mb
- Bump DEVICE_COMPAT_VERSION (config migration not possible)
- Remove swconfig board setup from 02_network
- Disable CONFIG_RTL8367S_GSW in mt7622 kernel config
CPU link / bandwidth notes:
- Buffalo WSR-2533DHP2 and TOTOLINK A8000RU: already used 2500base-x
on gmac0 before this change; aggregate bandwidth stays the same.
- ELECOM WRC-2533GENT: gmac0 moves from SGMII (1G) to 2500base-x
(HSGMII). The swconfig setup previously used two 1G CPU links
(gmac0 + gmac1) for 2 Gbps aggregate; DSA collapses this to a
single 2.5 Gbps link.
MAC address assignment notes:
- Buffalo WSR-2533DHP2: WAN uses base MAC + 1, gmac0/LAN uses base MAC
(previously the WAN MAC existed on the implicit eth1/gmac1 interface)
- ELECOM WRC-2533GENT: WAN inherits CPU MAC via DSA conduit
(original gmac1 had no nvmem-cells assignment)
- TOTOLINK A8000RU: WAN reuses macaddr_factory_24 (previously gmac1)
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/24861
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-03 18:52:44 +02007727479e5f7160391b3eeb2f58244daf360ed1b3mediatek: mt7622: convert devices with RTL8367S switch to DSAedittarget/linux/mediatek/mt7622/base-files/etc/board.d/05_compat-versionedittarget/linux/mediatek/mt7622/config-6.18edittarget/linux/mediatek/image/mt7622.mkedittarget/linux/mediatek/dts/mt7622-buffalo-wsr.dtsiedittarget/linux/mediatek/dts/mt7622-totolink-a8000ru.dtsedittarget/linux/mediatek/dts/mt7622-elecom-wrc-2533gent.dtsedittarget/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-versionedittarget/linux/mediatek/dts/mt7622-buffalo-wsr-2533dhp2.dtsedittarget/linux/mediatek/mt7622/base-files/etc/board.d/02_network
- target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/port.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rate.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/smi.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_portIsolation.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_error.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/cpu.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_phy.htarget/linux/mediatek/files/drivers/net/phy/rtk/Makefiletarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/mirror.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/eee.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_scheduling.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_led.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_reg.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eav.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_types.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_i2c.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/port.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_fc.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/l2.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_vlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/smi.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_lut.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/leaky.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/igmp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mirror.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_i2c.htarget/linux/mediatek/mt7622/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rldp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_svlan.ctarget/linux/mediatek/mt7623/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_cputag.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/ptp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trunk.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trap.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/storm.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_unknownMulticast.ctarget/linux/mediatek/mt7629/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_qos.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/dot1x.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_interrupt.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/interrupt.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mib.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rldp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/i2c.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/cpu.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_hsb.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/dot1x.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/l2.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_scheduling.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_switch.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/led.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/interrupt.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_inbwctrl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_svlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/oam.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rldp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trunk.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_cputag.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eee.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_inbwctrl.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/ptp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_igmp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_oam.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_misc.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/leaky.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/storm.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/svlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_dot1x.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_hal.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_qos.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/qos.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/acl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/vlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_switch.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_port.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_acl.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_igmp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/vlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/acl.htarget/linux/mediatek/patches-6.18/500-gsw-rtl8367s-mt7622-support.patchtarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mirror.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mii_mgr.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_port.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_trunking.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mib.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_hsb.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_interrupt.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_trunking.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_fc.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rma.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/mirror.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_acl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/igmp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/stat.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/stat.htarget/linux/mediatek/filogic/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_vlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_mdio.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_storm.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_portIsolation.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_green.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eee.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_unknownMulticast.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_green.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_meter.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/qos.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rldp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/eee.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_dbg.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eav.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/i2c.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_phy.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/led.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_oam.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_misc.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rma.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/svlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_led.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_storm.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_meter.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trap.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_lut.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_hal.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_dot1x.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rate.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/oam.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_base.h70c61a29e5acb6afe6c59b5df18eaab0ebc88d0a1788454364000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commediatek: remove RTL8367S_GSW driver and disable swconfig on mt7622
All mt7622 devices using the RTL8367S switch have been migrated to
the generic rtl8365mb DSA driver. Remove the now-unused RTL8367S_GSW
driver and disable swconfig in the mt7622 kernel config, since no
device in this target needs it anymore.
The driver and its Kconfig symbol are shared across the mediatek
target, so this also drops the tree-wide files/drivers/net/phy/rtk/
sources and the now-dead "# CONFIG_RTL8367S_GSW is not set" line
from the filogic, mt7623 and mt7629 kernel configs.
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/24861
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-03 18:52:44 +020070c61a29e5acb6afe6c59b5df18eaab0ebc88d0amediatek: remove RTL8367S_GSW driver and disable swconfig on mt7622deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_green.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/svlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/i2c.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mib.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mii_mgr.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/igmp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_hsb.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/led.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_misc.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trunk.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/leaky.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_hsb.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/smi.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_svlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_vlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/dot1x.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/dot1x.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/port.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/l2.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_unknownMulticast.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/stat.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_lut.cdeletetarget/linux/mediatek/patches-6.18/500-gsw-rtl8367s-mt7622-support.patchdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/cpu.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_inbwctrl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eee.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rate.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/ptp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/smi.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_types.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_led.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/led.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_green.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_interrupt.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_igmp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rldp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/ptp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/interrupt.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/acl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_switch.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_igmp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trap.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/interrupt.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rldp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_acl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_mdio.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eee.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/mirror.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_phy.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_unknownMulticast.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_interrupt.hedittarget/linux/mediatek/mt7629/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/Makefiledeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_phy.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mib.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_led.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rma.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_reg.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_lut.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_port.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_cputag.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_oam.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_svlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_scheduling.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_portIsolation.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_hal.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/qos.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_storm.cedittarget/linux/mediatek/filogic/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_qos.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_trunking.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_i2c.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_hal.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/storm.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_vlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_i2c.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/i2c.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/stat.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_storm.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rma.hedittarget/linux/mediatek/mt7622/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_oam.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/cpu.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_meter.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/port.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/leaky.hedittarget/linux/mediatek/mt7623/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/igmp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/mirror.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rate.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rldp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_dbg.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_acl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/storm.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/vlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trap.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_cputag.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_dot1x.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rldp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eav.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_misc.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/oam.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mirror.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/eee.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/vlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/oam.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eav.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_port.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_fc.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/svlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_error.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/acl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_meter.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_scheduling.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trunk.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_switch.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_qos.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_inbwctrl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_base.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/eee.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/qos.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mirror.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_portIsolation.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_trunking.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_fc.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_dot1x.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/l2.h
- target/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchtarget/linux/generic/pending-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchtarget/linux/generic/backport-6.18/786-02-v7.4-net-phy-add-notify_phy_attach_detach-hooks-to-struct-mii_bus.patchtarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchtarget/linux/generic/pending-6.18/703-phy-add-detach-callback-to-struct-phy_driver.patchtarget/linux/generic/backport-6.18/786-01-v7.4-net-phy-add-phy_detach_internal-helper.patch5a09fb18589c60ce87189d8c70e0946deb3320d71788456292000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.dekernel: backport (*notify_phy_attach/detach)() hooks
Provide two hooks in struct mii_bus
- notify_phy_attach(): called in phy_attach_direct() after PHY
hardware has been initialized and just before PHY is resumed.
- notify_phy_detach(): called in phy_detach() right after PHY
has been suspended.
Link: https://github.com/openwrt/openwrt/pull/25009
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 19:24:52 +02005a09fb18589c60ce87189d8c70e0946deb3320d7kernel: backport (*notify_phy_attach/detach)() hooksaddtarget/linux/generic/backport-6.18/786-02-v7.4-net-phy-add-notify_phy_attach_detach-hooks-to-struct-mii_bus.patchedittarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchedittarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchedittarget/linux/generic/pending-6.18/703-phy-add-detach-callback-to-struct-phy_driver.patchedittarget/linux/generic/pending-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchaddtarget/linux/generic/backport-6.18/786-01-v7.4-net-phy-add-phy_detach_internal-helper.patch
- target/linux/realtek/patches-6.18/031-31-v7.4-net-mdio-realtek-rtl9300-Open-up-C22-and-C45-space-in-parallel.patchtarget/linux/realtek/patches-6.18/031-33-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL839x.patchtarget/linux/realtek/patches-6.18/031-25-v7.4-net-mdio-realtek-rtl9300-Add-polling-doc.patchtarget/linux/realtek/patches-6.18/031-30-v7.4-net-mdio-realtek-rtl9300-Increase-MDIO-timeout.patchtarget/linux/realtek/patches-6.18/031-28-v7.4-net-mdio-realtek-rtl9300-Configure-hardware-polling-during-probing.patchtarget/linux/realtek/patches-6.18/031-32-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL838x.patchtarget/linux/realtek/patches-6.18/031-34-v7.4-net-mdio-realtek-rtl9300-reword-Kconfig-and-module-description.patchtarget/linux/realtek/patches-6.18/031-27-v7.4-net-mdio-realtek-rtl9300-suppress-sysfs-bind-unbind-attributes.patchtarget/linux/realtek/patches-6.18/031-26-v7.4-net-mdio-realtek-rtl9300-deny-C45-over-C22-access.patchtarget/linux/realtek/patches-6.18/031-29-v7.4-net-mdio-realtek-rtl9300-Add-page-tracking.patchaa66786f38505c80daaec59ed922d420261467fe1788456292000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: backport Realtek Otto MDIO patches
Another bunch of Realtek otto MDIO patches has been
accepted upstream. Add them downstream.
Link: https://github.com/openwrt/openwrt/pull/25009
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 19:24:52 +0200aa66786f38505c80daaec59ed922d420261467ferealtek: backport Realtek Otto MDIO patchesaddtarget/linux/realtek/patches-6.18/031-28-v7.4-net-mdio-realtek-rtl9300-Configure-hardware-polling-during-probing.patchaddtarget/linux/realtek/patches-6.18/031-27-v7.4-net-mdio-realtek-rtl9300-suppress-sysfs-bind-unbind-attributes.patchaddtarget/linux/realtek/patches-6.18/031-34-v7.4-net-mdio-realtek-rtl9300-reword-Kconfig-and-module-description.patchaddtarget/linux/realtek/patches-6.18/031-26-v7.4-net-mdio-realtek-rtl9300-deny-C45-over-C22-access.patchaddtarget/linux/realtek/patches-6.18/031-32-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL838x.patchaddtarget/linux/realtek/patches-6.18/031-31-v7.4-net-mdio-realtek-rtl9300-Open-up-C22-and-C45-space-in-parallel.patchaddtarget/linux/realtek/patches-6.18/031-33-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL839x.patchaddtarget/linux/realtek/patches-6.18/031-25-v7.4-net-mdio-realtek-rtl9300-Add-polling-doc.patchaddtarget/linux/realtek/patches-6.18/031-30-v7.4-net-mdio-realtek-rtl9300-Increase-MDIO-timeout.patchaddtarget/linux/realtek/patches-6.18/031-29-v7.4-net-mdio-realtek-rtl9300-Add-page-tracking.patch
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.htarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c28ba2708f1f609bfd134975808b2bc6ed9dc97421788509061000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: derive phylink capabilities from SoC config
Replace the separate RTL83xx and RTL93xx phylink capability callbacks
with a common implementation.
Add mac_capabilities to the SoC configuration and use it to advertise
the supported link speeds and corresponding SerDes interface modes.
RTL838x and RTL839x support speeds up to 1 Gbps, while RTL930x and
RTL931x additionally support 2.5, 5 and 10 Gbps.
Continue to advertise PHY_INTERFACE_MODE_INTERNAL for all ports.
Do not advertise PHY_INTERFACE_MODE_GMII, as the RTL83xx and RTL93xx
SoCs do not provide a GMII interface between their MACs and PHYs.
When PCS instances are described for a port, copy the supported SerDes
interface modes to pcs_interfaces and register the callback used to
resolve the available PCS instances.
This removes duplicated capability definitions, prevents phylink from
selecting an unsupported GMII interface and provides the basis for
taking the port-specific MAC-to-SerDes mapping into account.
Assisted-by: ChatGPT (OpenAI GPT-5.6 Sol)
Link: https://github.com/openwrt/openwrt/pull/24992
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 10:04:21 +020028ba2708f1f609bfd134975808b2bc6ed9dc9742realtek: dsa: derive phylink capabilities from SoC configedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.hedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.c
- target/linux/realtek/patches-6.18/039-01-v7.4-gpio-realtek-otto-use-__raw_readl-writel-in-realtek_.patchtarget/linux/realtek/patches-6.18/039-02-v7.4-gpio-realtek-otto-make-bank_read-write-overridable-b.patch0f948c5111d8b55732373a24630daf4311d2bf021788525869000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: backport realtek-otto-gpio patches
Backport the realtek gpio driver patches for that makes it
functional when SWAP_IO_SPACE is enabled.
Signed-off-by: Rustam Adilov <adilov@tutamail.com>
Link: https://github.com/openwrt/openwrt/pull/25015
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 14:44:29 +02000f948c5111d8b55732373a24630daf4311d2bf02realtek: backport realtek-otto-gpio patchesaddtarget/linux/realtek/patches-6.18/039-01-v7.4-gpio-realtek-otto-use-__raw_readl-writel-in-realtek_.patchaddtarget/linux/realtek/patches-6.18/039-02-v7.4-gpio-realtek-otto-make-bank_read-write-overridable-b.patch
- target/linux/realtek/dts/rtl9302_zyxel_xgs1x10-12-common.dtsi2b263a3951b638f183caaf11bb918feaa41028721788545749000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: extend Zyxel XGS1x10-12 SFP LED configuration for 100M/10M
Speeds of 100 Mb/s and 10 Mb/s are possible for SFP ports when SGMII or
USXGMII is used. Extend the LED configuration to include these speeds.
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
Link: https://github.com/openwrt/openwrt/pull/25018
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 20:15:49 +02002b263a3951b638f183caaf11bb918feaa4102872realtek: extend Zyxel XGS1x10-12 SFP LED configuration for 100M/10Medittarget/linux/realtek/dts/rtl9302_zyxel_xgs1x10-12-common.dtsi
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cdb825a4e86e984a23a10be1f3a69c07c6e883b3e1788553553000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: make 10gr link helper generic to rtl93xx
Both RTL93xx variants use the same link status bit for 10GR links.
Rename the RTL931x helper to rtl93xx so it can be shared by both
variants.
The link status is latched low, so discard the first read and return
the current state from the second. Use the helper in the RTL930x
state-machine initialization instead of open-coding the two reads.
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:53 +0200db825a4e86e984a23a10be1f3a69c07c6e883b3erealtek: pcs: make 10gr link helper generic to rtl93xxedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c8d14167c132899aed8a947fc7c5c793aae38cafb1788553554000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: split pcs_get_state link state sources
pcs_get_state always read the MAC-side link/speed mirror registers,
regardless of SerDes mode. For Clause 37 modes, that mirror can go stale:
a speed renegotiated purely at the SGMII/PCS level is visible in the SerDes
LPA register immediately, but the MAC-side mirror only refreshes when the
MAC force-enable selector is pulsed.
Read the SerDes Clause 22/37 BMSR and LPA registers directly for SGMII,
1000BASE-X and 2500BASE-X, and decode them with the standard phylink helper.
Read BMSR twice because its link status is latched low. Keep all other
SerDes modes on the existing MAC-side mirror path.
When SGMII operates without in-band negotiation, preserve the speed,
duplex and pause settings supplied by phylink; the PCS decoder only updates
link state in that mode.
This fixes PCS state reporting for the SGMII speed-change bug reported on
RTL930x SFP ports. Refreshing the MAC datapath with a force-enable pulse will
be handled separately later.
Link: https://github.com/openwrt/openwrt/issues/23055
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:54 +02008d14167c132899aed8a947fc7c5c793aae38cafbrealtek: pcs: split pcs_get_state link state sourcesedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c2a9f30361eba0eafd3cbe0c319b08e156b72015e1788553554000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl931x: drop unused link status getter
rtpcs_931x_sds_link_sts_get() is marked __always_unused and has no
callers. The active PCS paths now contain the status handling they
require, so remove the dormant SDK-derived diagnostic helper.
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:54 +02002a9f30361eba0eafd3cbe0c319b08e156b72015erealtek: pcs: rtl931x: drop unused link status getteredittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dtstarget/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mace250cadb9d9be98e286e67cbbea64572ac1ea6931788553798000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commpc85xx: red-15w: use nvmem for wifi MAC
Remove userspace handling for the wifi MAC as nvmem is available to
handle this.
Add label-mac-device support for similar reasons. The ethaddr MAC shows
up on the label on the device.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24699
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:29:58 +0200e250cadb9d9be98e286e67cbbea64572ac1ea693mpc85xx: red-15w: use nvmem for wifi MACedittarget/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dtsedittarget/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
- package/boot/uboot-tools/Makefilepackage/boot/uboot-tools/uboot-envtools/files/mpc85xx3809dfe5c69b43bc9b39f7b75fa493bbc2ad57ac1788553875000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.compackages: uboot-tools: add env config for Sophos RED 15w
Uboot-Envtools is installed by default on the mpc85xx target.
Add the proper configuration for the Sophos RED 15w, so the fw_*env
commands will actually work.
Fix alphabetic sorting in the case statement while we're at it.
Signed-off-by: Shine- GH <4c.fce2@proton.me>
Link: https://github.com/openwrt/openwrt/pull/24939
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:31:15 +02003809dfe5c69b43bc9b39f7b75fa493bbc2ad57acpackages: uboot-tools: add env config for Sophos RED 15weditpackage/boot/uboot-tools/uboot-envtools/files/mpc85xxeditpackage/boot/uboot-tools/Makefile
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.ca43f44ae3eab5e6c89fdc8b047c51747fa620b381788629188000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: release the LAG table on error paths
rtldsa_93xx_lag_set_group2ports() gets an already locked table handle
from priv->r->lag_table() and releases it only on the success path, so
both error returns leave the mutex held for good.
The lock covers a whole table access register rather than one of its
tables, so the damage is wider than LAG: on RTL930x that register also
carries VLAN, the ingress ACL, spanning tree state, the packet counters
and port isolation, and every later access to any of them blocks. On
RTL931x the LAG table shares its register with port isolation.
Only the -ENOSPC path can be reached today, when a bond has more than
eight member ports; nothing bounds the member count before it.
Callers cannot reach the -EOPNOTSUPP path because
rtldsa_port_lag_join() already rejects any hash type other than
NETDEV_LAG_HASH_L2 and L23 in rtldsa_83xx_lag_can_offload(), and the
remaining callers pass a NULL info, but the missing release is a trap
for whoever changes that guard.
Not reproduced on hardware: the board here has eight ports, one too few
to trigger the reachable path, and no RTL931x is available.
Compile-tested on realtek/rtl930x and realtek/rtl838x.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25036
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 19:26:28 +0200a43f44ae3eab5e6c89fdc8b047c51747fa620b38realtek: dsa: release the LAG table on error pathsedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.c
- target/linux/bcm27xx/patches-6.12/950-0054-Add-dwc_otg-driver.patchtarget/linux/generic/pending-6.12/701-netfilter-nf_tables-ignore-EOPNOTSUPP-on-flowtable-d.patchtarget/linux/generic/pending-6.12/655-increase_skb_pad.patchtarget/linux/generic/kernel-6.12target/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchtarget/linux/generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patchtarget/linux/generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patchca7f2b898f8c34b2f64b33e3dcff06cf67e3d4641788637832000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: bump 6.12 to 6.12.108
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.108
Upstream merged patches:
- generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patch[1]
- generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patch[2]
All other patches are automatically refreshed.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.108&id=b708aa5cb1422fc97b48f6a2598a87d638ad74c3
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.108&id=65b2f6f79753ca285f6c611e457a67812e31816c
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24993
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-05 21:50:32 +0200ca7f2b898f8c34b2f64b33e3dcff06cf67e3d464kernel: bump 6.12 to 6.12.108edittarget/linux/generic/pending-6.12/701-netfilter-nf_tables-ignore-EOPNOTSUPP-on-flowtable-d.patchedittarget/linux/bcm27xx/patches-6.12/950-0054-Add-dwc_otg-driver.patchdeletetarget/linux/generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patchedittarget/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchedittarget/linux/generic/pending-6.12/655-increase_skb_pad.patchedittarget/linux/generic/kernel-6.12deletetarget/linux/generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patch
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.caddae4dbfb01a0d92fdfe146ec915b2fe13d9ef21788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl930x: don't clobber adjacent LOG counter
On RTL930x two packet counters share a single LOG table entry, so the
counter ID is halved when addressing the table. rtl930x_packet_cntr_clear()
zeroed one of the two registers and then wrote the whole entry back
without first reading its current contents, wiping the adjacent counter
with whatever stale data happened to be in the table register cache.
Read the entry before modifying one half so the adjacent counter is kept
intact.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200addae4dbfb01a0d92fdfe146ec915b2fe13d9ef2realtek: dsa: rtl930x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c27c185120e11e8eb7fbca594d9d629e9b66510241788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: bound PIE rule search by the phase block range
rtl839x_pie_rule_add(), rtl930x_pie_rule_add() and rtl931x_pie_rule_add()
split the PIE blocks into an ingress and an egress half and only scan the
half matching the rule's phase, but the "nothing found" check still
compared against the full block count. For a rule that exhausted its half
the loop then fell through with a stale block/index instead of returning
-EOPNOTSUPP.
Compare against max_block so an exhausted phase range fails cleanly.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +020027c185120e11e8eb7fbca594d9d629e9b6651024realtek: dsa: rtl83xx: bound PIE rule search by the phase block rangeedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.hd8693b19b4379ac0ab34338787e3e8781be7ac271788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: widen pie_rule.ethertype_m to u16
The EtherType value in struct pie_rule is a u16, but its mask field was
only u8, so it cannot express a full 16-bit match. Widen the mask to
match the value it applies to.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d8693b19b4379ac0ab34338787e3e8781be7ac27realtek: dsa: widen pie_rule.ethertype_m to u16edittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.h
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.cd51cfa41a6d6c9d3a395baaf9457b53a116ea0cb1788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: set fwd_sel for the tc flower TRAP action
The FLOW_ACTION_TRAP handler filled in fwd_data and fwd_act but left
fwd_sel clear, so the PIE never actually selected the forwarding action
and trapped packets were not redirected to the CPU port.
Set fwd_sel like the other forwarding actions do.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d51cfa41a6d6c9d3a395baaf9457b53a116ea0cbrealtek: dsa: rtl83xx: set fwd_sel for the tc flower TRAP actionedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cd6933d6aedc8a8d5aff646ed3fe71135d5a46fcd1788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: check L4 port and VLAN template fields
*_pie_verify_template() rejected a template that lacked the SIP, DIP,
SMAC or DMAC field a rule needs, but silently accepted one missing the
L4 source/destination port or inner-VLAN fields. When such a template
was picked the corresponding match was simply dropped: a
"flower ip_proto udp dst_port 5353" offload installed against an L2-only
template matched every UDP frame instead of just mDNS.
The same gap exists identically in all four PIE-based SoCs (rtl838x,
rtl839x, rtl930x, rtl931x): each verify_template() stops at the SMAC/DMAC
check and never looks at the L4 port or VLAN fields.
Reject a template that does not carry the port/VLAN field the rule masks,
so the block search falls through to one that does.
The failure was observed on an RTL9302C (Zyxel XGS1210-12, rtl930x): a
dst_port 5353 drop rule also counted UDP sent to other ports. rtl838x/
839x/931x share the same verify_template() structure and template
layout, so the fix is applied there too, though only rtl930x hardware
was available to reproduce and verify it.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d6933d6aedc8a8d5aff646ed3fe71135d5a46fcdrealtek: dsa: rtl83xx: check L4 port and VLAN template fieldsedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- package/network/config/wifi-scripts/files-ucode/usr/share/ucode/wifi/iface.uc93d975fe9c098e39e19f1248c8eabee2e7c66db81788645823000https://taiha.net/jenkins/user/mailmailmail@david-bauer.netwifi-scripts: iface: set auth_type on unset encryption
parse_encryption returns leaves config.auth_type unset in case
encryption is unset. However, the owe_transition_iface config option for
the unencrypted network is currently only set in case encryption is
explicitly set to 'none'.
These two should be identical in their behavior. Set the encryption to
"none" in case it is unset and do not return. This aligns the behavior
of unset encryption with encryption explicitly set to 'none'.
Signed-off-by: David Bauer <mail@david-bauer.net>
2026-09-06 00:03:43 +020093d975fe9c098e39e19f1248c8eabee2e7c66db8wifi-scripts: iface: set auth_type on unset encryptioneditpackage/network/config/wifi-scripts/files-ucode/usr/share/ucode/wifi/iface.uc
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c1be891e4bbccc958ac8f8ff04c55ff1188fb34f51788709386000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl839x: read PIE rules from the IACL table
rtl839x_pie_rule_read() selects table type 2 through RTL8380_TBL_0,
the RTL838x table access block, while its own comment names the IACL
table and the matching rtl839x_pie_rule_write() reaches it through
RTL8390_TBL_0.
The two blocks differ in more than their address. RTL8380_TBL_0 drives
the command register at 0x6914, with the execute bit at 15 and the
inverted read/write polarity rtl_table_exec() applies to RTL838x;
RTL8390_TBL_0 uses 0x1190, execute at 16 and normal polarity. On an
RTL839x the reader therefore drives the RTL838x table register at
0x6914 and takes its seventeen words from 0x6918 instead of 0x1194.
rtl_table_get() also locks the descriptor it is handed, so the reader
holds a different mutex from the one the writer holds and the two do
not serialise against each other.
Nothing reaches this today: .pie_rule_read is populated for RTL838x
and RTL839x but is never invoked through priv->r, so the defect is
latent and no failure has been observed. It is fixed because the
reader and the writer have to agree before either becomes reachable.
Compile-tested on realtek/rtl839x. Not run on hardware, no RTL839x
board here; the change selects the table the writer already selects.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25051
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:06 +02001be891e4bbccc958ac8f8ff04c55ff1188fb34f5realtek: dsa: rtl839x: read PIE rules from the IACL tableedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c3d94c1e94216a05b39d5ff085a58b0e7fda408d91788709431000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: drop the tc flow hashtable ref before HW teardown
rtl83xx_delete_flower() called pie_rule_rm() - which takes pie_mutex -
while still holding rcu_read_lock(), i.e. it could sleep inside an RCU
read-side critical section.
Remove the flow from the hashtable and drop the RCU lock first, then tear
down the hardware rule outside the critical section. Propagate the
rhashtable_remove_fast() error and return -ENOENT (not -EINVAL) when no
flow matches the cookie.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25050
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:51 +02003d94c1e94216a05b39d5ff085a58b0e7fda408d9realtek: dsa: rtl83xx: drop the tc flow hashtable ref before HW teardownedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cc197aadfcc0e085b92d9c03216546e55e8132f571788709431000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: verify the MAC template against the mask, not the value
*_pie_verify_template() gates the SMAC / DMAC template requirement on
ether_addr_to_u64(pr->smac) / pr->dmac, i.e. on the match value, while
every neighbouring field (sip_m, dip_m, ethertype_m, itag_m, sport_m,
dport_m) is gated on its mask. A rule matching the all-zero MAC -
"flower dst_mac 00:00:00:00:00:00", full mask, zero value - then passes
verification against a template that has no DMAC field and is programmed
to match every frame instead of just that address.
Gate on smac_m / dmac_m like the other fields. Pre-existing in all four
*_pie_verify_template() implementations; only rtl930x was exercised
(tc cls_flower offload), the other three are changed for consistency.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25050
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:51 +0200c197aadfcc0e085b92d9c03216546e55e8132f57realtek: dsa: rtl83xx: verify the MAC template against the mask, not the valueedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c
- target/linux/generic/pending-6.18/897-02-net-pse-pd-add-LED-trigger-support.patchtarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchtarget/linux/generic/pending-6.18/897-01-net-pse-pd-add-devm_pse_poll_helper.patche87bdafa704f1bd3238046f2a9473915834134581788710617000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comgeneric: pse-pd: rework the phydev->psec notifier patch to fix rtnl deadlock
The notifier patch attached phydev->psec under rtnl_lock() inside
phy_device_register(). Drivers that register their MDIO bus from
ndo_init() (like the lantiq etop) already hold rtnl at that point, so the
attach tried to take rtnl a second time and deadlocked on probe.
Aleksander hit this on lantiq arx100.
Rework 896-03 to use a dedicated mutex instead of rtnl for the psec
attach, the notifier walks and the ethtool PSE paths, so there is no rtnl
recursion any more.
The mutex lives in pse_core.c rather than in phylib: net/ethtool is always
built into vmlinux while PHYLIB is tristate, so net/ethtool/pse-pd.c must
not call a phylib export or CONFIG_PHYLIB=m fails to link. PSE_CONTROLLER
is bool, so pse_core is either in vmlinux or absent and every config can
reach pse_phy_lock()/pse_phy_unlock(); !PSE_CONTROLLER gets no-op stubs in
pse.h.
phy_device_register_locked() is gone with it. It only existed because the
attach took rtnl, and was identical to phy_device_register() apart from an
ASSERT_RTNL(), so sfp.c calls phy_device_register() again and
include/linux/phy.h stays untouched.
Also refresh 897-01 and 897-02, whose hunks shift.
Tested-by: Aleksander Jan Bajkowski <olek2@wp.pl>
Signed-off-by: Carlo Szelinsky <github@szelinsky.de>
Link: https://github.com/openwrt/openwrt/pull/24945
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 18:03:37 +0200e87bdafa704f1bd3238046f2a947391583413458generic: pse-pd: rework the phydev->psec notifier patch to fix rtnl deadlockedittarget/linux/generic/pending-6.18/897-02-net-pse-pd-add-LED-trigger-support.patchedittarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchedittarget/linux/generic/pending-6.18/897-01-net-pse-pd-add-devm_pse_poll_helper.patch
- target/linux/generic/hack-6.18/790-net-phy-skip-MMD-30-for-RTL8221B-when-reading-C45-PH.patch88dcd8c303b688b344c8f22c24df6a49f6b6b7071788710770000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comkernel: add hack to avoid killing RTL8221B PHYs
RTL8221B unfortunately suffers from a issue where reading registers from
MMD 30 can break the PHY. Once it is in the broken state, recovery is
only possible by hardware reset.
Add a hack which prevents the kernel from reading MMD 30 while probing
for PHYs when a RTL8221B is detected, based on the ID from MMD 1.
Fixes: https://github.com/openwrt/openwrt/issues/22140
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
Link: https://github.com/openwrt/openwrt/pull/25017
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 18:06:10 +020088dcd8c303b688b344c8f22c24df6a49f6b6b707kernel: add hack to avoid killing RTL8221B PHYsaddtarget/linux/generic/hack-6.18/790-net-phy-skip-MMD-30-for-RTL8221B-when-reading-C45-PH.patch
- package/kernel/mac80211/patches/ath11k/951-wifi-ath11k-disable-interrupts-during-firmware-crash-recovery.patchpackage/kernel/mac80211/patches/ath11k/950-wifi-ath11k-implement-CE-interrupt-enable-disable-for-AHB.patchpackage/kernel/mac80211/Makefile3ec9ced6e1fa1a17803ba2da55fe35a6ba5486cc1788714058000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commac80211: ath11k: stop a firmware crash from rebooting the SoC on AHB
On IPQ8074 a firmware assert reboots the SoC.
ath11k_core_reconfigure_on_crash() frees the data path and clears the
ring list while the DP NAPI is still polling, so the NAPI services a ring
whose address pointer has just been cleared:
Unable to handle kernel read from unreadable memory at virtual address 0
pc : ath11k_hal_srng_access_begin+0xc/0x60 [ath11k]
Call trace:
ath11k_hal_srng_access_begin+0xc/0x60 [ath11k] (P)
ath11k_dp_rx_process_mon_rings+0xa0/0x5d4 [ath11k]
ath11k_dp_service_srng+0x1f4/0x348 [ath11k]
ath11k_ahb_ext_grp_napi_poll+0x34/0xd4 [ath11k_ahb]
951 disables the interrupts on the crash path again. 950 is its
prerequisite: it wires up the CE interrupt ops that
ath11k_ahb_hif_ops_ipq8074 never set, which leaves the CE half of the
quiesce a no-op on AHB. Both are in ath-next as commit a7ab5c835e42
("wifi: ath11k: implement CE interrupt enable/disable for AHB") and
commit f7a74e131d3f ("wifi: ath11k: disable interrupts during firmware
crash recovery"), and are carried here verbatim.
Tested on a Xiaomi AX3600 (IPQ8074 hw2.0) with the debugfs
simulate_fw_crash assert trigger: one assert panics and reboots the SoC
before, five asserts recover after.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/24578
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:00:58 +02003ec9ced6e1fa1a17803ba2da55fe35a6ba5486ccmac80211: ath11k: stop a firmware crash from rebooting the SoC on AHBaddpackage/kernel/mac80211/patches/ath11k/950-wifi-ath11k-implement-CE-interrupt-enable-disable-for-AHB.patchaddpackage/kernel/mac80211/patches/ath11k/951-wifi-ath11k-disable-interrupts-during-firmware-crash-recovery.patcheditpackage/kernel/mac80211/Makefile
- target/linux/airoha/an7583/config-6.18target/linux/airoha/an7581/config-6.18e4e7c4f70c0041b4436d8e2ce048114e83b52d031788715771000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comairoha: disable CONFIG_FW_LOADER_USER_HELPER_FALLBACK
NET_AIROHA_NPU is built-in and probes before rootfs is mounted, so
request_firmware() correctly fails with -ENOENT. The driver maps that
to -EPROBE_DEFER and succeeds once /lib/firmware is available.
With CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y (inherited from generic),
a missing firmware instead blocks ~60s on the sysfs userspace helper
and returns -ETIMEDOUT. That is not mapped to -EPROBE_DEFER, so NPU
probe fails permanently:
Direct firmware load for airoha/en7581_MT7996_npu_rv32.bin failed with error -2
Falling back to sysfs fallback for: airoha/en7581_MT7996_npu_rv32.bin
error -ETIMEDOUT: failed to run npu firmware
probe with driver airoha-npu failed with error -110
This shows up on official / firmware-selector images because
CONFIG_ALL_KMODS=y builds kmod-leds-lp55xx-common, which implies
FW_LOADER_USER_HELPER and then FALLBACK from generic takes effect.
Match bcm53xx/gemini/layerscape: keep FW_LOADER_USER_HELPER (from
generic) and unset only FALLBACK on an7581/an7583. Unsetting both is
not refresh-safe — FALLBACK depends on USER_HELPER, so
make target/linux/refresh drops the FALLBACK line when USER_HELPER is
off, and ALL_KMODS builds then reintroduce the -ETIMEDOUT failure.
With FALLBACK disabled, early firmware misses keep returning -ENOENT
and deferred probe can load the NPU firmware after rootfs.
Fixes: https://github.com/openwrt/openwrt/issues/22709
Supersedes: https://github.com/openwrt/openwrt/pull/22697
Signed-off-by: Daniel Pawlik <pawlik.dan@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24571
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:29:31 +0200e4e7c4f70c0041b4436d8e2ce048114e83b52d03airoha: disable CONFIG_FW_LOADER_USER_HELPER_FALLBACKedittarget/linux/airoha/an7583/config-6.18edittarget/linux/airoha/an7581/config-6.18
- target/linux/generic/backport-6.18/786-v7.3-net-phy-air_en8811h-move-LED-GPIO-configuration-to-config_init.patch928f5c5ab860779801e36b036c9c0b319230de411788716107000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comkernel: 6.18: fix EN8811H PHY LED GPIO not surviving MCU restart
Currently, the LAN1 LED usually doesn't work on Nokia XG-040G-MD and
Nokia XG-040G-MF devices: it lights up right after boot but goes dark
again as soon as the link renegotiates. Both boards wire LAN1 to a
discrete Airoha EN8811H PHY, whose LED GPIO pins are only ever
configured as outputs once, in en8811h_probe(); every later call to
en8811h_config_init() restarts the PHY's MD32 MCU, which resets that
GPIO configuration back to inputs.
Backport the fix that moves the GPIO-as-output configuration into
en8811h_config_init() so it is reapplied on every MCU restart. This is
a fix to the generic Linux PHY driver (drivers/net/phy/air_en8811h.c),
not something specific to the airoha target: other targets ship the
same PHY via kmod-phy-airoha-en8811h (e.g. mediatek/filogic boards),
so it belongs in target/linux/generic/backport-6.18/ rather than under
target/linux/airoha/.
Merged upstream into net.git by Paolo Abeni as commit 03b4702fc5e3
("net: phy: air_en8811h: move LED GPIO configuration to config_init"),
expected in v7.3. The patch is functionally identical to that commit,
refreshed into OpenWrt's quilt form.
Suggested-by: Mikhail Zhilkin <csharper2005@gmail.com>
Signed-off-by: Vitaliy Sochnev <sochnev.v.74@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24853
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:35:07 +0200928f5c5ab860779801e36b036c9c0b319230de41kernel: 6.18: fix EN8811H PHY LED GPIO not surviving MCU restartaddtarget/linux/generic/backport-6.18/786-v7.3-net-phy-air_en8811h-move-LED-GPIO-configuration-to-config_init.patch
- tools/cmake/Makefile50258d2078d3b3c4fe127f72c8d804fa498c62d21788718129000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comtools/cmake: update to version 4.4.3
Update cmake to version 4.4.3.
(No need for patch changes)
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Link: https://github.com/openwrt/openwrt/pull/25043
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:08:49 +020050258d2078d3b3c4fe127f72c8d804fa498c62d2tools/cmake: update to version 4.4.3edittools/cmake/Makefile
- package/kernel/nat46/Makefile76506c10944cb43df7d7b884c9d4504e76d9a9a71788719170000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comnat46: pass NAT46_VERSION through CFLAGS_MODULE
kbuild dropped EXTRA_CFLAGS in 6.15 (e966ad0edd00, "kbuild: remove
EXTRA_*FLAGS support"), so on 6.18 the define never reaches the
compiler and the module logs "nat46: module (version unknown) loaded".
CFLAGS_MODULE is read by both 6.12 and 6.18.
Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/25057
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:26:10 +020076506c10944cb43df7d7b884c9d4504e76d9a9a7nat46: pass NAT46_VERSION through CFLAGS_MODULEeditpackage/kernel/nat46/Makefile
- target/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_ppe_main.cf1a3f07139853ebce2dad2f1fb17fc91a1e157631788719248000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: qca_ppe: accept a multicast delete that is already done
The bridge drops a port's multicast entries on every leave, STP
transition and membership expiry, per port and without tracking which
entries this switch programmed. A delete therefore arrives both for
entries that were never added - the add path runs only for ports in an
offloaded bridge - and for entries an earlier delete already emptied.
ppe_fdb_lookup() reports those as -ENOENT and the driver returned it.
Nothing acts on that return: the object is deleted through switchdev's
deferred queue, where switchdev_port_obj_del_deferred() turns any error
other than -EOPNOTSUPP into a log line and discards it. The error only
produced kernel noise for a state that already matched the request. A
port that is not in the entry's portmap is the same case one step
further in.
Return success for both. The path that drops an entry once its last
member outside the CPU port leaves is unchanged.
Measured on an ipq8074 board with multicast snooping enabled, one group
joined by lan1, lan2 and lan3, and the three ports then removed from
the bridge in turn:
qca-ppe 3a000000.ppe lan3: Failed to del Port Multicast Database
entry (object id=2) with error: -ENOENT (-2).
twice before this change and not at all after it, the ports returning
to the bridge either way.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/24968
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:27:28 +0200f1a3f07139853ebce2dad2f1fb17fc91a1e15763qualcommax: qca_ppe: accept a multicast delete that is already doneedittarget/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_ppe_main.c
- package/kernel/mac80211/patches/ath12k/200-Revert-wifi-ath12k-convert-tasklet-to-BH-workqueue-f.patch4ab78459bd8d41d3e4af93ce2c8babd4f1f533c71788721070000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commac80211: ath12k: drop the BH workqueue revert
Patch 200 reverted the ath12k conversion from tasklets to BH workqueues.
It arrived with 88f4c32060 ("mac80211: update to version 6.14.11") in May
2025, when main still built kernel 6.6 on 26 targets; BH workqueues only
exist from 6.9, so the revert was doing real work then.
Main now builds 6.12 and 6.18. Both provide system_bh_wq and from_work(),
so there is nothing left for the revert to paper over.
It also leaves the driver inconsistent. backports 7.2 uses intr_wq in
ce.h, pci.c and ahb.c alike, and patch 200 converts only the first two
back to tasklets -- ahb.c was added to the driver after the conversion
landed and never got the same treatment. Building with ATH12K_AHB enabled
therefore fails.
Against pristine backports 7.2 the mac80211 patch series applies 151/151
with this patch removed, and no intr_tq reference survives in ath12k. An
ipq53xx build with ATH12K_AHB enabled links ahb.o cleanly, and the driver
probes an on-chip radio on real hardware.
Bump PKG_RELEASE so existing installs pick up the rebuilt module: it feeds
ABI_VERSION for the kmod packages.
Signed-off-by: Hideo Sumi <hideo.sumi@mugops.com>
Link: https://github.com/openwrt/openwrt/pull/24978
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:57:50 +02004ab78459bd8d41d3e4af93ce2c8babd4f1f533c7mac80211: ath12k: drop the BH workqueue revertdeletepackage/kernel/mac80211/patches/ath12k/200-Revert-wifi-ath12k-convert-tasklet-to-BH-workqueue-f.patch
- package/boot/uboot-rockchip/Makefiletarget/linux/rockchip/image/armv8.mke36c1c0caf018a7e476e40711d9fbf3c13a8eae11788721977000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comuboot-rockchip: switch to dedicated profile for NanoPi R76S
Support for NanoPi R76S has been merged upstream u-boot, so use
it instead of the generic profile.
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
Link: https://github.com/openwrt/openwrt/pull/25047
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:12:57 +0200e36c1c0caf018a7e476e40711d9fbf3c13a8eae1uboot-rockchip: switch to dedicated profile for NanoPi R76Seditpackage/boot/uboot-rockchip/Makefileedittarget/linux/rockchip/image/armv8.mk
- package/kernel/rtl8812au-ct/patches/120-cfg80211-7.2.patchpackage/kernel/rtl8812au-ct/Makefile3c1066f412f672d73345c05963437f4ce5e7856b1788722178000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comrtl8812au-ct: fix build with mac80211 7.2
mac80211 7.2 changes cfg80211 key and station operations to take a
wireless_dev instead of a net_device. It also updates station notification
helpers and the remain-on-channel callback.
Adapt the driver to the new API and bump the package release.
Signed-off-by: Alexander Zaguzin <st7105@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25020
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:16:18 +02003c1066f412f672d73345c05963437f4ce5e7856brtl8812au-ct: fix build with mac80211 7.2addpackage/kernel/rtl8812au-ct/patches/120-cfg80211-7.2.patcheditpackage/kernel/rtl8812au-ct/Makefile
- package/network/config/netifd/files/usr/libexec/network/packet-steering.ucpackage/network/config/netifd/Makefilee801f59cff6bb65a4d9555ad995d9ad9fca9049f1788722749000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comnetifd: avoid pinning mt76 TX worker to NAPI CPU
The packet steering script treats both threaded NAPI and the mt76 TX
worker as tasks belonging to the same wireless device. assign_dev_cpu()
then assigns all of these tasks to the same CPU.
This unnecessarily restricts the mt76 TX worker to the NAPI CPU even
though its affinity does not otherwise need to be constrained.
On MT7988A with MT7996 this caused the TX worker to share CPU3 with the
NAPI thread. Moving it to another CPU increased measured TX throughput
from 1.45 Gbit/s to 2.09 Gbit/s.
Stop matching the mt76 TX worker in the packet steering script. This
leaves its CPU affinity unrestricted and lets the scheduler place it
more appropriately.
Fixes: https://github.com/openwrt/openwrt/issues/24697
Signed-off-by: Gary Dotzler <geldot@protonmail.com>
Link: https://github.com/openwrt/openwrt/pull/25016
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:25:49 +0200e801f59cff6bb65a4d9555ad995d9ad9fca9049fnetifd: avoid pinning mt76 TX worker to NAPI CPUeditpackage/network/config/netifd/files/usr/libexec/network/packet-steering.uceditpackage/network/config/netifd/Makefile
- package/network/services/dropbear/Makefilepackage/network/services/dropbear/Config.infe4bb132561130e85cc87f27691e55ca9ac5cd201788723090000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comdropbear: enable ECDSA by default for backward compatibility
Enable ECDSA by default to:
- Support login with existing ECDSA keys.
- Ensure compatibility with legacy YubiKey devices (e.g., firmware 5.4)
and PIV-based SSH keys (RSA/ECDSA only).
- Maintain access until Ed25519 adoption is widespread.
Default 'y' for all builds except those with SMALL_FLASH.
This activates:
- DROPBEAR_ECC_256 (via DROPBEAR_ECDH || DROPBEAR_ECDSA), enabling
NIST-curve code for non-SMALL_FLASH builds.
- DROPBEAR_SK_ECDSA (default y), offering
sk-ecdsa-sha2-nistp256@openssh.com by default.
Note: Increases only binary size for non-SMALL_FLASH targets.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Link: https://github.com/openwrt/openwrt/pull/24685
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 19:31:30 +0000fe4bb132561130e85cc87f27691e55ca9ac5cd20dropbear: enable ECDSA by default for backward compatibilityeditpackage/network/services/dropbear/Config.ineditpackage/network/services/dropbear/Makefile
githttps://taiha.net/jenkins/user/mailmailhttps://taiha.net/jenkins/user/danieldanielhttps://taiha.net/jenkins/user/haukehaukehttps://taiha.net/jenkins/user/jelonek.jonasjelonek.jonashttps://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenhttps://taiha.net/jenkins/user/robimarkorobimarkoblueStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WR8750N/WR9500N/WG600HP (AR9344)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)486fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/tiny/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/tiny/feeds.buildinfoopenwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-initramfs-factory.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binopenwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-initramfs-kernel.binopenwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wg600hp-uboot.binopenwrt-ath79-tiny-nec_wg600hp-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wg600hp-uboot.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr8750n-uboot.binopenwrt-ath79-tiny-nec_wr8750n-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr8750n-uboot.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-initramfs-factory.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-initramfs-kernel.binopenwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-squashfs-sysupgrade.binopenwrt-ath79-tiny-nec_wr9500n-uboot.binopenwrt-ath79-tiny-nec_wr9500n-uboot.binbin/targets/ath79/tiny/openwrt-ath79-tiny-nec_wr9500n-uboot.binopenwrt-ath79-tiny.manifestopenwrt-ath79-tiny.manifestbin/targets/ath79/tiny/openwrt-ath79-tiny.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/tiny/profiles.jsonsha256sumssha256sumsbin/targets/ath79/tiny/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/tiny/version.buildinfofalsediffconfig: true, device: WR8750N/WR9500N/WG600HP (AR9344)#48626275833023555OpenWrt (master) for NEC Aterm (NetBSD based) #486486falsefalse48651SUCCESS1788738000597https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/486/home-slave02_taihasv- target/linux/qualcommax/dts/ipq6000-nn6000-v2.dtse5517d856dc802a7bff3899091ea5b0a724dcaad1788428109000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq60xx: enable lan4 port for link nn6000v2
The swport5 node was disabled by mistake during the PPE conversion.
Fixes: f50435627d37 ("qualcommax: ipq60xx/ipq807x: convert to PPE networking stack")
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
Link: https://github.com/openwrt/openwrt/pull/25006
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-03 11:35:09 +0200e5517d856dc802a7bff3899091ea5b0a724dcaadqualcommax: ipq60xx: enable lan4 port for link nn6000v2edittarget/linux/qualcommax/dts/ipq6000-nn6000-v2.dts
- package/network/config/wifi-scripts/files-ucode/lib/netifd/wireless/mac80211.shpackage/network/config/wifi-scripts/Makefilee21a4ef958d8ea1006a0b4a8ebbf0c6a35be95a01788428299000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comwifi-scripts: silence iw antenna/distance failures like shell did
The shell mac80211.sh ran both of these with >/dev/null 2>&1:
iw phy "$phy" set antenna $txantenna $rxantenna >/dev/null 2>&1
iw phy "$phy" set distance "$distance" >/dev/null 2>&1
The ucode rewrite dropped the redirect, so on any driver without
->set_coverage_class every wifi up now logs
netifd: radio0 (3302): command failed: Not supported (-95)
with no indication of which command failed. Neither return value is
checked, so the message is pure noise -- but it reads like wifi up
failed, and on ath12k/IPQ5332 it cost real debugging time before the
line was traced back to iw.c:616 rather than to the driver.
Restore the redirect. distance defaults to 0 and antenna to 0xffffffff,
so both calls run on every setup for every radio.
Signed-off-by: Hideo Sumi <hideo.sumi@mugops.com>
2026-09-03 11:38:19 +0200e21a4ef958d8ea1006a0b4a8ebbf0c6a35be95a0wifi-scripts: silence iw antenna/distance failures like shell dideditpackage/network/config/wifi-scripts/files-ucode/lib/netifd/wireless/mac80211.sheditpackage/network/config/wifi-scripts/Makefile
- package/firmware/linux-firmware/aeonsemi.mk897533e4886e008e994980ea1339cff44e5a405e1788434358000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orglinux-firmware: mark aeonsemi-as21xxx-firmware as 'nonshared'
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 <daniel@makrotopia.org>
2026-09-03 12:19:18 +0100897533e4886e008e994980ea1339cff44e5a405elinux-firmware: mark aeonsemi-as21xxx-firmware as 'nonshared'editpackage/firmware/linux-firmware/aeonsemi.mk
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c1866d1eba79b6f9a6261bcc3e3ffbe28abbf373e1788447634000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl838x: don't clobber adjacent LOG counter
rtl838x_packet_cntr_clear() zeroes one of the two registers that make up
a LOG table entry and then writes the whole entry back without reading it
first, wiping the adjacent counter with whatever stale data is in the
table register cache. Two 32-bit packet counters share one entry, so the
counter next to the one being cleared is lost.
Read the entry before modifying one half, mirroring the same fix already
applied to rtl930x_packet_cntr_clear().
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25005
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 17:00:34 +02001866d1eba79b6f9a6261bcc3e3ffbe28abbf373erealtek: dsa: rtl838x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cd8f9a15a2de22dc5f8644243c8637d66d854c7141788447634000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl839x: don't clobber adjacent LOG counter
rtl839x_packet_cntr_clear() has the same defect as the rtl838x variant:
it zeroes one register of a shared two-register LOG table entry and
writes the entry back without reading it first, so the counter sharing
that entry is overwritten with stale register-cache data.
Read the entry before modifying one half, mirroring the same fix already
applied to rtl930x_packet_cntr_clear().
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25005
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 17:00:34 +0200d8f9a15a2de22dc5f8644243c8637d66d854c714realtek: dsa: rtl839x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- target/linux/mediatek/dts/mt7622-buffalo-wsr-2533dhp2.dtstarget/linux/mediatek/dts/mt7622-elecom-wrc-2533gent.dtstarget/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-versiontarget/linux/mediatek/image/mt7622.mktarget/linux/mediatek/mt7622/config-6.18target/linux/mediatek/mt7622/base-files/etc/board.d/05_compat-versiontarget/linux/mediatek/dts/mt7622-buffalo-wsr.dtsitarget/linux/mediatek/dts/mt7622-totolink-a8000ru.dtstarget/linux/mediatek/mt7622/base-files/etc/board.d/02_network7727479e5f7160391b3eeb2f58244daf360ed1b31788454364000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commediatek: mt7622: convert devices with RTL8367S switch to DSA
Migrate Buffalo WSR-2533DHP2, ELECOM WRC-2533GENT and TOTOLINK A8000RU
from swconfig to DSA. These devices use an external Realtek RTL8367S
switch handled by the rtl8365mb DSA driver.
Per-device changes:
- Drop the proprietary mediatek,rtk-gsw node
- Add realtek,rtl8365mb DSA switch with ports lan1-lan4, wan and CPU
- Move CPU port to gmac0 at 2500base-x (HSGMII)
- Remove gmac1 (was 5u@eth1 in swconfig; DSA uses single CPU port)
- Drop unused rgmii_via_gmac2 pin group
- Replace swconfig with kmod-dsa-rtl8365mb
- Bump DEVICE_COMPAT_VERSION (config migration not possible)
- Remove swconfig board setup from 02_network
- Disable CONFIG_RTL8367S_GSW in mt7622 kernel config
CPU link / bandwidth notes:
- Buffalo WSR-2533DHP2 and TOTOLINK A8000RU: already used 2500base-x
on gmac0 before this change; aggregate bandwidth stays the same.
- ELECOM WRC-2533GENT: gmac0 moves from SGMII (1G) to 2500base-x
(HSGMII). The swconfig setup previously used two 1G CPU links
(gmac0 + gmac1) for 2 Gbps aggregate; DSA collapses this to a
single 2.5 Gbps link.
MAC address assignment notes:
- Buffalo WSR-2533DHP2: WAN uses base MAC + 1, gmac0/LAN uses base MAC
(previously the WAN MAC existed on the implicit eth1/gmac1 interface)
- ELECOM WRC-2533GENT: WAN inherits CPU MAC via DSA conduit
(original gmac1 had no nvmem-cells assignment)
- TOTOLINK A8000RU: WAN reuses macaddr_factory_24 (previously gmac1)
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/24861
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-03 18:52:44 +02007727479e5f7160391b3eeb2f58244daf360ed1b3mediatek: mt7622: convert devices with RTL8367S switch to DSAedittarget/linux/mediatek/mt7622/base-files/etc/board.d/05_compat-versionedittarget/linux/mediatek/mt7622/config-6.18edittarget/linux/mediatek/image/mt7622.mkedittarget/linux/mediatek/dts/mt7622-buffalo-wsr.dtsiedittarget/linux/mediatek/dts/mt7622-totolink-a8000ru.dtsedittarget/linux/mediatek/dts/mt7622-elecom-wrc-2533gent.dtsedittarget/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-versionedittarget/linux/mediatek/dts/mt7622-buffalo-wsr-2533dhp2.dtsedittarget/linux/mediatek/mt7622/base-files/etc/board.d/02_network
- target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/port.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rate.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/smi.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_portIsolation.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_error.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/cpu.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_phy.htarget/linux/mediatek/files/drivers/net/phy/rtk/Makefiletarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/mirror.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/eee.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_scheduling.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_led.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_reg.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eav.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_types.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_i2c.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/port.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_fc.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/l2.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_vlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/smi.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_lut.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/leaky.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/igmp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mirror.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_i2c.htarget/linux/mediatek/mt7622/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rldp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_svlan.ctarget/linux/mediatek/mt7623/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_cputag.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/ptp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trunk.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trap.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/storm.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_unknownMulticast.ctarget/linux/mediatek/mt7629/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_qos.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/dot1x.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_interrupt.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/interrupt.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mib.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rldp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/i2c.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/cpu.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_hsb.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/dot1x.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/l2.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_scheduling.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_switch.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/led.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/interrupt.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_inbwctrl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_svlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/oam.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rldp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trunk.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_cputag.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eee.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_inbwctrl.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/ptp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_igmp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_oam.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_misc.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/leaky.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/storm.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/svlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_dot1x.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_hal.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_qos.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/qos.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/acl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/vlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_switch.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_port.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_acl.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_igmp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/vlan.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/acl.htarget/linux/mediatek/patches-6.18/500-gsw-rtl8367s-mt7622-support.patchtarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mirror.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mii_mgr.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_port.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_trunking.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mib.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_hsb.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_interrupt.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_trunking.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_fc.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rma.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/mirror.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_acl.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/igmp.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/stat.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/stat.htarget/linux/mediatek/filogic/config-6.18target/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_vlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_mdio.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_storm.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_portIsolation.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_green.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eee.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_unknownMulticast.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_green.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_meter.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/qos.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rldp.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/eee.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_dbg.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eav.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/i2c.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_phy.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/led.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_oam.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_misc.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rma.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/svlan.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_led.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_storm.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_meter.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trap.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_lut.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_hal.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_dot1x.htarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rate.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/oam.ctarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_base.h70c61a29e5acb6afe6c59b5df18eaab0ebc88d0a1788454364000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commediatek: remove RTL8367S_GSW driver and disable swconfig on mt7622
All mt7622 devices using the RTL8367S switch have been migrated to
the generic rtl8365mb DSA driver. Remove the now-unused RTL8367S_GSW
driver and disable swconfig in the mt7622 kernel config, since no
device in this target needs it anymore.
The driver and its Kconfig symbol are shared across the mediatek
target, so this also drops the tree-wide files/drivers/net/phy/rtk/
sources and the now-dead "# CONFIG_RTL8367S_GSW is not set" line
from the filogic, mt7623 and mt7629 kernel configs.
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/24861
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-03 18:52:44 +020070c61a29e5acb6afe6c59b5df18eaab0ebc88d0amediatek: remove RTL8367S_GSW driver and disable swconfig on mt7622deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_green.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/svlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/i2c.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mib.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mii_mgr.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/igmp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_hsb.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/led.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_misc.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trunk.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/leaky.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_hsb.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/smi.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_svlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_vlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/dot1x.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/dot1x.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/port.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/l2.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_unknownMulticast.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/stat.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_lut.cdeletetarget/linux/mediatek/patches-6.18/500-gsw-rtl8367s-mt7622-support.patchdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/cpu.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_inbwctrl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eee.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rate.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/ptp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/smi.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_types.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_led.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/led.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_green.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_interrupt.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_igmp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rldp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/ptp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/interrupt.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/acl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_switch.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_igmp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/trap.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/interrupt.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rldp.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_acl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_mdio.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eee.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/mirror.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_phy.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_unknownMulticast.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_interrupt.hedittarget/linux/mediatek/mt7629/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/Makefiledeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_phy.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mib.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_led.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rma.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_reg.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_lut.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_port.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_cputag.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_oam.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_svlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_scheduling.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_portIsolation.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_hal.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/qos.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_storm.cedittarget/linux/mediatek/filogic/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_qos.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_trunking.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_i2c.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_hal.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/storm.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_vlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_i2c.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/i2c.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/stat.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_storm.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_rma.hedittarget/linux/mediatek/mt7622/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_oam.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/cpu.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_meter.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/port.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/leaky.hedittarget/linux/mediatek/mt7623/config-6.18deletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/igmp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/mirror.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rate.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rldp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s_dbg.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_acl.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/storm.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/vlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trap.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_cputag.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_dot1x.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_rldp.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_eav.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_misc.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/oam.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_mirror.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/eee.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/vlan.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/oam.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_eav.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_port.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_fc.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/svlan.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtk_error.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/acl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_meter.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_scheduling.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/trunk.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtk_switch.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_qos.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_inbwctrl.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_base.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/eee.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/qos.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_mirror.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_portIsolation.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367s.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_trunking.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/rtl8367c_asicdrv_fc.cdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/rtl8367c_asicdrv_dot1x.hdeletetarget/linux/mediatek/files/drivers/net/phy/rtk/rtl8367c/include/l2.h
- target/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchtarget/linux/generic/pending-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchtarget/linux/generic/backport-6.18/786-02-v7.4-net-phy-add-notify_phy_attach_detach-hooks-to-struct-mii_bus.patchtarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchtarget/linux/generic/pending-6.18/703-phy-add-detach-callback-to-struct-phy_driver.patchtarget/linux/generic/backport-6.18/786-01-v7.4-net-phy-add-phy_detach_internal-helper.patch5a09fb18589c60ce87189d8c70e0946deb3320d71788456292000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.dekernel: backport (*notify_phy_attach/detach)() hooks
Provide two hooks in struct mii_bus
- notify_phy_attach(): called in phy_attach_direct() after PHY
hardware has been initialized and just before PHY is resumed.
- notify_phy_detach(): called in phy_detach() right after PHY
has been suspended.
Link: https://github.com/openwrt/openwrt/pull/25009
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 19:24:52 +02005a09fb18589c60ce87189d8c70e0946deb3320d7kernel: backport (*notify_phy_attach/detach)() hooksaddtarget/linux/generic/backport-6.18/786-02-v7.4-net-phy-add-notify_phy_attach_detach-hooks-to-struct-mii_bus.patchedittarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchedittarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchedittarget/linux/generic/pending-6.18/703-phy-add-detach-callback-to-struct-phy_driver.patchedittarget/linux/generic/pending-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchaddtarget/linux/generic/backport-6.18/786-01-v7.4-net-phy-add-phy_detach_internal-helper.patch
- target/linux/realtek/patches-6.18/031-31-v7.4-net-mdio-realtek-rtl9300-Open-up-C22-and-C45-space-in-parallel.patchtarget/linux/realtek/patches-6.18/031-33-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL839x.patchtarget/linux/realtek/patches-6.18/031-25-v7.4-net-mdio-realtek-rtl9300-Add-polling-doc.patchtarget/linux/realtek/patches-6.18/031-30-v7.4-net-mdio-realtek-rtl9300-Increase-MDIO-timeout.patchtarget/linux/realtek/patches-6.18/031-28-v7.4-net-mdio-realtek-rtl9300-Configure-hardware-polling-during-probing.patchtarget/linux/realtek/patches-6.18/031-32-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL838x.patchtarget/linux/realtek/patches-6.18/031-34-v7.4-net-mdio-realtek-rtl9300-reword-Kconfig-and-module-description.patchtarget/linux/realtek/patches-6.18/031-27-v7.4-net-mdio-realtek-rtl9300-suppress-sysfs-bind-unbind-attributes.patchtarget/linux/realtek/patches-6.18/031-26-v7.4-net-mdio-realtek-rtl9300-deny-C45-over-C22-access.patchtarget/linux/realtek/patches-6.18/031-29-v7.4-net-mdio-realtek-rtl9300-Add-page-tracking.patchaa66786f38505c80daaec59ed922d420261467fe1788456292000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: backport Realtek Otto MDIO patches
Another bunch of Realtek otto MDIO patches has been
accepted upstream. Add them downstream.
Link: https://github.com/openwrt/openwrt/pull/25009
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-03 19:24:52 +0200aa66786f38505c80daaec59ed922d420261467ferealtek: backport Realtek Otto MDIO patchesaddtarget/linux/realtek/patches-6.18/031-28-v7.4-net-mdio-realtek-rtl9300-Configure-hardware-polling-during-probing.patchaddtarget/linux/realtek/patches-6.18/031-27-v7.4-net-mdio-realtek-rtl9300-suppress-sysfs-bind-unbind-attributes.patchaddtarget/linux/realtek/patches-6.18/031-34-v7.4-net-mdio-realtek-rtl9300-reword-Kconfig-and-module-description.patchaddtarget/linux/realtek/patches-6.18/031-26-v7.4-net-mdio-realtek-rtl9300-deny-C45-over-C22-access.patchaddtarget/linux/realtek/patches-6.18/031-32-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL838x.patchaddtarget/linux/realtek/patches-6.18/031-31-v7.4-net-mdio-realtek-rtl9300-Open-up-C22-and-C45-space-in-parallel.patchaddtarget/linux/realtek/patches-6.18/031-33-v7.4-net-mdio-realtek-rtl9300-Add-support-for-RTL839x.patchaddtarget/linux/realtek/patches-6.18/031-25-v7.4-net-mdio-realtek-rtl9300-Add-polling-doc.patchaddtarget/linux/realtek/patches-6.18/031-30-v7.4-net-mdio-realtek-rtl9300-Increase-MDIO-timeout.patchaddtarget/linux/realtek/patches-6.18/031-29-v7.4-net-mdio-realtek-rtl9300-Add-page-tracking.patch
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.htarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c28ba2708f1f609bfd134975808b2bc6ed9dc97421788509061000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: derive phylink capabilities from SoC config
Replace the separate RTL83xx and RTL93xx phylink capability callbacks
with a common implementation.
Add mac_capabilities to the SoC configuration and use it to advertise
the supported link speeds and corresponding SerDes interface modes.
RTL838x and RTL839x support speeds up to 1 Gbps, while RTL930x and
RTL931x additionally support 2.5, 5 and 10 Gbps.
Continue to advertise PHY_INTERFACE_MODE_INTERNAL for all ports.
Do not advertise PHY_INTERFACE_MODE_GMII, as the RTL83xx and RTL93xx
SoCs do not provide a GMII interface between their MACs and PHYs.
When PCS instances are described for a port, copy the supported SerDes
interface modes to pcs_interfaces and register the callback used to
resolve the available PCS instances.
This removes duplicated capability definitions, prevents phylink from
selecting an unsupported GMII interface and provides the basis for
taking the port-specific MAC-to-SerDes mapping into account.
Assisted-by: ChatGPT (OpenAI GPT-5.6 Sol)
Link: https://github.com/openwrt/openwrt/pull/24992
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 10:04:21 +020028ba2708f1f609bfd134975808b2bc6ed9dc9742realtek: dsa: derive phylink capabilities from SoC configedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.hedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.c
- target/linux/realtek/patches-6.18/039-01-v7.4-gpio-realtek-otto-use-__raw_readl-writel-in-realtek_.patchtarget/linux/realtek/patches-6.18/039-02-v7.4-gpio-realtek-otto-make-bank_read-write-overridable-b.patch0f948c5111d8b55732373a24630daf4311d2bf021788525869000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: backport realtek-otto-gpio patches
Backport the realtek gpio driver patches for that makes it
functional when SWAP_IO_SPACE is enabled.
Signed-off-by: Rustam Adilov <adilov@tutamail.com>
Link: https://github.com/openwrt/openwrt/pull/25015
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 14:44:29 +02000f948c5111d8b55732373a24630daf4311d2bf02realtek: backport realtek-otto-gpio patchesaddtarget/linux/realtek/patches-6.18/039-01-v7.4-gpio-realtek-otto-use-__raw_readl-writel-in-realtek_.patchaddtarget/linux/realtek/patches-6.18/039-02-v7.4-gpio-realtek-otto-make-bank_read-write-overridable-b.patch
- target/linux/realtek/dts/rtl9302_zyxel_xgs1x10-12-common.dtsi2b263a3951b638f183caaf11bb918feaa41028721788545749000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: extend Zyxel XGS1x10-12 SFP LED configuration for 100M/10M
Speeds of 100 Mb/s and 10 Mb/s are possible for SFP ports when SGMII or
USXGMII is used. Extend the LED configuration to include these speeds.
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
Link: https://github.com/openwrt/openwrt/pull/25018
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-04 20:15:49 +02002b263a3951b638f183caaf11bb918feaa4102872realtek: extend Zyxel XGS1x10-12 SFP LED configuration for 100M/10Medittarget/linux/realtek/dts/rtl9302_zyxel_xgs1x10-12-common.dtsi
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cdb825a4e86e984a23a10be1f3a69c07c6e883b3e1788553553000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: make 10gr link helper generic to rtl93xx
Both RTL93xx variants use the same link status bit for 10GR links.
Rename the RTL931x helper to rtl93xx so it can be shared by both
variants.
The link status is latched low, so discard the first read and return
the current state from the second. Use the helper in the RTL930x
state-machine initialization instead of open-coding the two reads.
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:53 +0200db825a4e86e984a23a10be1f3a69c07c6e883b3erealtek: pcs: make 10gr link helper generic to rtl93xxedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c8d14167c132899aed8a947fc7c5c793aae38cafb1788553554000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: split pcs_get_state link state sources
pcs_get_state always read the MAC-side link/speed mirror registers,
regardless of SerDes mode. For Clause 37 modes, that mirror can go stale:
a speed renegotiated purely at the SGMII/PCS level is visible in the SerDes
LPA register immediately, but the MAC-side mirror only refreshes when the
MAC force-enable selector is pulsed.
Read the SerDes Clause 22/37 BMSR and LPA registers directly for SGMII,
1000BASE-X and 2500BASE-X, and decode them with the standard phylink helper.
Read BMSR twice because its link status is latched low. Keep all other
SerDes modes on the existing MAC-side mirror path.
When SGMII operates without in-band negotiation, preserve the speed,
duplex and pause settings supplied by phylink; the PCS decoder only updates
link state in that mode.
This fixes PCS state reporting for the SGMII speed-change bug reported on
RTL930x SFP ports. Refreshing the MAC datapath with a force-enable pulse will
be handled separately later.
Link: https://github.com/openwrt/openwrt/issues/23055
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:54 +02008d14167c132899aed8a947fc7c5c793aae38cafbrealtek: pcs: split pcs_get_state link state sourcesedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c2a9f30361eba0eafd3cbe0c319b08e156b72015e1788553554000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl931x: drop unused link status getter
rtpcs_931x_sds_link_sts_get() is marked __always_unused and has no
callers. The active PCS paths now contain the status handling they
require, so remove the dormant SDK-derived diagnostic helper.
Link: https://github.com/openwrt/openwrt/pull/24986
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:25:54 +02002a9f30361eba0eafd3cbe0c319b08e156b72015erealtek: pcs: rtl931x: drop unused link status getteredittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dtstarget/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mace250cadb9d9be98e286e67cbbea64572ac1ea6931788553798000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commpc85xx: red-15w: use nvmem for wifi MAC
Remove userspace handling for the wifi MAC as nvmem is available to
handle this.
Add label-mac-device support for similar reasons. The ethaddr MAC shows
up on the label on the device.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24699
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:29:58 +0200e250cadb9d9be98e286e67cbbea64572ac1ea693mpc85xx: red-15w: use nvmem for wifi MACedittarget/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dtsedittarget/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
- package/boot/uboot-tools/Makefilepackage/boot/uboot-tools/uboot-envtools/files/mpc85xx3809dfe5c69b43bc9b39f7b75fa493bbc2ad57ac1788553875000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.compackages: uboot-tools: add env config for Sophos RED 15w
Uboot-Envtools is installed by default on the mpc85xx target.
Add the proper configuration for the Sophos RED 15w, so the fw_*env
commands will actually work.
Fix alphabetic sorting in the case statement while we're at it.
Signed-off-by: Shine- GH <4c.fce2@proton.me>
Link: https://github.com/openwrt/openwrt/pull/24939
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-04 22:31:15 +02003809dfe5c69b43bc9b39f7b75fa493bbc2ad57acpackages: uboot-tools: add env config for Sophos RED 15weditpackage/boot/uboot-tools/uboot-envtools/files/mpc85xxeditpackage/boot/uboot-tools/Makefile
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.ca43f44ae3eab5e6c89fdc8b047c51747fa620b381788629188000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: release the LAG table on error paths
rtldsa_93xx_lag_set_group2ports() gets an already locked table handle
from priv->r->lag_table() and releases it only on the success path, so
both error returns leave the mutex held for good.
The lock covers a whole table access register rather than one of its
tables, so the damage is wider than LAG: on RTL930x that register also
carries VLAN, the ingress ACL, spanning tree state, the packet counters
and port isolation, and every later access to any of them blocks. On
RTL931x the LAG table shares its register with port isolation.
Only the -ENOSPC path can be reached today, when a bond has more than
eight member ports; nothing bounds the member count before it.
Callers cannot reach the -EOPNOTSUPP path because
rtldsa_port_lag_join() already rejects any hash type other than
NETDEV_LAG_HASH_L2 and L23 in rtldsa_83xx_lag_can_offload(), and the
remaining callers pass a NULL info, but the missing release is a trap
for whoever changes that guard.
Not reproduced on hardware: the board here has eight ports, one too few
to trigger the reachable path, and no RTL931x is available.
Compile-tested on realtek/rtl930x and realtek/rtl838x.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25036
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 19:26:28 +0200a43f44ae3eab5e6c89fdc8b047c51747fa620b38realtek: dsa: release the LAG table on error pathsedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.c
- target/linux/bcm27xx/patches-6.12/950-0054-Add-dwc_otg-driver.patchtarget/linux/generic/pending-6.12/701-netfilter-nf_tables-ignore-EOPNOTSUPP-on-flowtable-d.patchtarget/linux/generic/pending-6.12/655-increase_skb_pad.patchtarget/linux/generic/kernel-6.12target/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchtarget/linux/generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patchtarget/linux/generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patchca7f2b898f8c34b2f64b33e3dcff06cf67e3d4641788637832000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: bump 6.12 to 6.12.108
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.108
Upstream merged patches:
- generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patch[1]
- generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patch[2]
All other patches are automatically refreshed.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.108&id=b708aa5cb1422fc97b48f6a2598a87d638ad74c3
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.108&id=65b2f6f79753ca285f6c611e457a67812e31816c
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24993
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-05 21:50:32 +0200ca7f2b898f8c34b2f64b33e3dcff06cf67e3d464kernel: bump 6.12 to 6.12.108edittarget/linux/generic/pending-6.12/701-netfilter-nf_tables-ignore-EOPNOTSUPP-on-flowtable-d.patchedittarget/linux/bcm27xx/patches-6.12/950-0054-Add-dwc_otg-driver.patchdeletetarget/linux/generic/backport-6.12/894-v7.3-usb-xhci-handle-port-events-when-there-is-one-roothub.patchedittarget/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchedittarget/linux/generic/pending-6.12/655-increase_skb_pad.patchedittarget/linux/generic/kernel-6.12deletetarget/linux/generic/backport-6.12/501-v7.1-ksmbd-harden-file-lifetime-during-session-teardown.patch
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.caddae4dbfb01a0d92fdfe146ec915b2fe13d9ef21788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl930x: don't clobber adjacent LOG counter
On RTL930x two packet counters share a single LOG table entry, so the
counter ID is halved when addressing the table. rtl930x_packet_cntr_clear()
zeroed one of the two registers and then wrote the whole entry back
without first reading its current contents, wiping the adjacent counter
with whatever stale data happened to be in the table register cache.
Read the entry before modifying one half so the adjacent counter is kept
intact.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200addae4dbfb01a0d92fdfe146ec915b2fe13d9ef2realtek: dsa: rtl930x: don't clobber adjacent LOG counteredittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c27c185120e11e8eb7fbca594d9d629e9b66510241788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: bound PIE rule search by the phase block range
rtl839x_pie_rule_add(), rtl930x_pie_rule_add() and rtl931x_pie_rule_add()
split the PIE blocks into an ingress and an egress half and only scan the
half matching the rule's phase, but the "nothing found" check still
compared against the full block count. For a rule that exhausted its half
the loop then fell through with a stale block/index instead of returning
-EOPNOTSUPP.
Compare against max_block so an exhausted phase range fails cleanly.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +020027c185120e11e8eb7fbca594d9d629e9b6651024realtek: dsa: rtl83xx: bound PIE rule search by the phase block rangeedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.hd8693b19b4379ac0ab34338787e3e8781be7ac271788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: widen pie_rule.ethertype_m to u16
The EtherType value in struct pie_rule is a u16, but its mask field was
only u8, so it cannot express a full 16-bit match. Widen the mask to
match the value it applies to.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d8693b19b4379ac0ab34338787e3e8781be7ac27realtek: dsa: widen pie_rule.ethertype_m to u16edittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl-otto.h
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.cd51cfa41a6d6c9d3a395baaf9457b53a116ea0cb1788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: set fwd_sel for the tc flower TRAP action
The FLOW_ACTION_TRAP handler filled in fwd_data and fwd_act but left
fwd_sel clear, so the PIE never actually selected the forwarding action
and trapped packets were not redirected to the CPU port.
Set fwd_sel like the other forwarding actions do.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d51cfa41a6d6c9d3a395baaf9457b53a116ea0cbrealtek: dsa: rtl83xx: set fwd_sel for the tc flower TRAP actionedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cd6933d6aedc8a8d5aff646ed3fe71135d5a46fcd1788642692000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: check L4 port and VLAN template fields
*_pie_verify_template() rejected a template that lacked the SIP, DIP,
SMAC or DMAC field a rule needs, but silently accepted one missing the
L4 source/destination port or inner-VLAN fields. When such a template
was picked the corresponding match was simply dropped: a
"flower ip_proto udp dst_port 5353" offload installed against an L2-only
template matched every UDP frame instead of just mDNS.
The same gap exists identically in all four PIE-based SoCs (rtl838x,
rtl839x, rtl930x, rtl931x): each verify_template() stops at the SMAC/DMAC
check and never looks at the L4 port or VLAN fields.
Reject a template that does not carry the port/VLAN field the rule masks,
so the block search falls through to one that does.
The failure was observed on an RTL9302C (Zyxel XGS1210-12, rtl930x): a
dst_port 5353 drop rule also counted UDP sent to other ports. rtl838x/
839x/931x share the same verify_template() structure and template
layout, so the fix is applied there too, though only rtl930x hardware
was available to reproduce and verify it.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25024
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-05 23:11:32 +0200d6933d6aedc8a8d5aff646ed3fe71135d5a46fcdrealtek: dsa: rtl83xx: check L4 port and VLAN template fieldsedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- package/network/config/wifi-scripts/files-ucode/usr/share/ucode/wifi/iface.uc93d975fe9c098e39e19f1248c8eabee2e7c66db81788645823000https://taiha.net/jenkins/user/mailmailmail@david-bauer.netwifi-scripts: iface: set auth_type on unset encryption
parse_encryption returns leaves config.auth_type unset in case
encryption is unset. However, the owe_transition_iface config option for
the unencrypted network is currently only set in case encryption is
explicitly set to 'none'.
These two should be identical in their behavior. Set the encryption to
"none" in case it is unset and do not return. This aligns the behavior
of unset encryption with encryption explicitly set to 'none'.
Signed-off-by: David Bauer <mail@david-bauer.net>
2026-09-06 00:03:43 +020093d975fe9c098e39e19f1248c8eabee2e7c66db8wifi-scripts: iface: set auth_type on unset encryptioneditpackage/network/config/wifi-scripts/files-ucode/usr/share/ucode/wifi/iface.uc
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c1be891e4bbccc958ac8f8ff04c55ff1188fb34f51788709386000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl839x: read PIE rules from the IACL table
rtl839x_pie_rule_read() selects table type 2 through RTL8380_TBL_0,
the RTL838x table access block, while its own comment names the IACL
table and the matching rtl839x_pie_rule_write() reaches it through
RTL8390_TBL_0.
The two blocks differ in more than their address. RTL8380_TBL_0 drives
the command register at 0x6914, with the execute bit at 15 and the
inverted read/write polarity rtl_table_exec() applies to RTL838x;
RTL8390_TBL_0 uses 0x1190, execute at 16 and normal polarity. On an
RTL839x the reader therefore drives the RTL838x table register at
0x6914 and takes its seventeen words from 0x6918 instead of 0x1194.
rtl_table_get() also locks the descriptor it is handed, so the reader
holds a different mutex from the one the writer holds and the two do
not serialise against each other.
Nothing reaches this today: .pie_rule_read is populated for RTL838x
and RTL839x but is never invoked through priv->r, so the defect is
latent and no failure has been observed. It is fixed because the
reader and the writer have to agree before either becomes reachable.
Compile-tested on realtek/rtl839x. Not run on hardware, no RTL839x
board here; the change selects the table the writer already selects.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25051
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:06 +02001be891e4bbccc958ac8f8ff04c55ff1188fb34f5realtek: dsa: rtl839x: read PIE rules from the IACL tableedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c3d94c1e94216a05b39d5ff085a58b0e7fda408d91788709431000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: drop the tc flow hashtable ref before HW teardown
rtl83xx_delete_flower() called pie_rule_rm() - which takes pie_mutex -
while still holding rcu_read_lock(), i.e. it could sleep inside an RCU
read-side critical section.
Remove the flow from the hashtable and drop the RCU lock first, then tear
down the hardware rule outside the critical section. Propagate the
rhashtable_remove_fast() error and return -ENOENT (not -EINVAL) when no
flow matches the cookie.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25050
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:51 +02003d94c1e94216a05b39d5ff085a58b0e7fda408d9realtek: dsa: rtl83xx: drop the tc flow hashtable ref before HW teardownedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/tc.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cc197aadfcc0e085b92d9c03216546e55e8132f571788709431000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: rtl83xx: verify the MAC template against the mask, not the value
*_pie_verify_template() gates the SMAC / DMAC template requirement on
ether_addr_to_u64(pr->smac) / pr->dmac, i.e. on the match value, while
every neighbouring field (sip_m, dip_m, ethertype_m, itag_m, sport_m,
dport_m) is gated on its mask. A rule matching the all-zero MAC -
"flower dst_mac 00:00:00:00:00:00", full mask, zero value - then passes
verification against a template that has no DMAC field and is programmed
to match every frame instead of just that address.
Gate on smac_m / dmac_m like the other fields. Pre-existing in all four
*_pie_verify_template() implementations; only rtl930x was exercised
(tc cls_flower offload), the other three are changed for consistency.
Assisted-by: Claude Code (Anthropic Claude Sonnet 5)
Signed-off-by: Mark Abe <github@mab.wien>
Link: https://github.com/openwrt/openwrt/pull/25050
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-06 17:43:51 +0200c197aadfcc0e085b92d9c03216546e55e8132f57realtek: dsa: rtl83xx: verify the MAC template against the mask, not the valueedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl930x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl838x.c
- target/linux/generic/pending-6.18/897-02-net-pse-pd-add-LED-trigger-support.patchtarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchtarget/linux/generic/pending-6.18/897-01-net-pse-pd-add-devm_pse_poll_helper.patche87bdafa704f1bd3238046f2a9473915834134581788710617000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comgeneric: pse-pd: rework the phydev->psec notifier patch to fix rtnl deadlock
The notifier patch attached phydev->psec under rtnl_lock() inside
phy_device_register(). Drivers that register their MDIO bus from
ndo_init() (like the lantiq etop) already hold rtnl at that point, so the
attach tried to take rtnl a second time and deadlocked on probe.
Aleksander hit this on lantiq arx100.
Rework 896-03 to use a dedicated mutex instead of rtnl for the psec
attach, the notifier walks and the ethtool PSE paths, so there is no rtnl
recursion any more.
The mutex lives in pse_core.c rather than in phylib: net/ethtool is always
built into vmlinux while PHYLIB is tristate, so net/ethtool/pse-pd.c must
not call a phylib export or CONFIG_PHYLIB=m fails to link. PSE_CONTROLLER
is bool, so pse_core is either in vmlinux or absent and every config can
reach pse_phy_lock()/pse_phy_unlock(); !PSE_CONTROLLER gets no-op stubs in
pse.h.
phy_device_register_locked() is gone with it. It only existed because the
attach took rtnl, and was identical to phy_device_register() apart from an
ASSERT_RTNL(), so sfp.c calls phy_device_register() again and
include/linux/phy.h stays untouched.
Also refresh 897-01 and 897-02, whose hunks shift.
Tested-by: Aleksander Jan Bajkowski <olek2@wp.pl>
Signed-off-by: Carlo Szelinsky <github@szelinsky.de>
Link: https://github.com/openwrt/openwrt/pull/24945
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 18:03:37 +0200e87bdafa704f1bd3238046f2a947391583413458generic: pse-pd: rework the phydev->psec notifier patch to fix rtnl deadlockedittarget/linux/generic/pending-6.18/897-02-net-pse-pd-add-LED-trigger-support.patchedittarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchedittarget/linux/generic/pending-6.18/897-01-net-pse-pd-add-devm_pse_poll_helper.patch
- target/linux/generic/hack-6.18/790-net-phy-skip-MMD-30-for-RTL8221B-when-reading-C45-PH.patch88dcd8c303b688b344c8f22c24df6a49f6b6b7071788710770000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comkernel: add hack to avoid killing RTL8221B PHYs
RTL8221B unfortunately suffers from a issue where reading registers from
MMD 30 can break the PHY. Once it is in the broken state, recovery is
only possible by hardware reset.
Add a hack which prevents the kernel from reading MMD 30 while probing
for PHYs when a RTL8221B is detected, based on the ID from MMD 1.
Fixes: https://github.com/openwrt/openwrt/issues/22140
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
Link: https://github.com/openwrt/openwrt/pull/25017
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 18:06:10 +020088dcd8c303b688b344c8f22c24df6a49f6b6b707kernel: add hack to avoid killing RTL8221B PHYsaddtarget/linux/generic/hack-6.18/790-net-phy-skip-MMD-30-for-RTL8221B-when-reading-C45-PH.patch
- package/kernel/mac80211/patches/ath11k/951-wifi-ath11k-disable-interrupts-during-firmware-crash-recovery.patchpackage/kernel/mac80211/patches/ath11k/950-wifi-ath11k-implement-CE-interrupt-enable-disable-for-AHB.patchpackage/kernel/mac80211/Makefile3ec9ced6e1fa1a17803ba2da55fe35a6ba5486cc1788714058000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commac80211: ath11k: stop a firmware crash from rebooting the SoC on AHB
On IPQ8074 a firmware assert reboots the SoC.
ath11k_core_reconfigure_on_crash() frees the data path and clears the
ring list while the DP NAPI is still polling, so the NAPI services a ring
whose address pointer has just been cleared:
Unable to handle kernel read from unreadable memory at virtual address 0
pc : ath11k_hal_srng_access_begin+0xc/0x60 [ath11k]
Call trace:
ath11k_hal_srng_access_begin+0xc/0x60 [ath11k] (P)
ath11k_dp_rx_process_mon_rings+0xa0/0x5d4 [ath11k]
ath11k_dp_service_srng+0x1f4/0x348 [ath11k]
ath11k_ahb_ext_grp_napi_poll+0x34/0xd4 [ath11k_ahb]
951 disables the interrupts on the crash path again. 950 is its
prerequisite: it wires up the CE interrupt ops that
ath11k_ahb_hif_ops_ipq8074 never set, which leaves the CE half of the
quiesce a no-op on AHB. Both are in ath-next as commit a7ab5c835e42
("wifi: ath11k: implement CE interrupt enable/disable for AHB") and
commit f7a74e131d3f ("wifi: ath11k: disable interrupts during firmware
crash recovery"), and are carried here verbatim.
Tested on a Xiaomi AX3600 (IPQ8074 hw2.0) with the debugfs
simulate_fw_crash assert trigger: one assert panics and reboots the SoC
before, five asserts recover after.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/24578
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:00:58 +02003ec9ced6e1fa1a17803ba2da55fe35a6ba5486ccmac80211: ath11k: stop a firmware crash from rebooting the SoC on AHBaddpackage/kernel/mac80211/patches/ath11k/950-wifi-ath11k-implement-CE-interrupt-enable-disable-for-AHB.patchaddpackage/kernel/mac80211/patches/ath11k/951-wifi-ath11k-disable-interrupts-during-firmware-crash-recovery.patcheditpackage/kernel/mac80211/Makefile
- target/linux/airoha/an7583/config-6.18target/linux/airoha/an7581/config-6.18e4e7c4f70c0041b4436d8e2ce048114e83b52d031788715771000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comairoha: disable CONFIG_FW_LOADER_USER_HELPER_FALLBACK
NET_AIROHA_NPU is built-in and probes before rootfs is mounted, so
request_firmware() correctly fails with -ENOENT. The driver maps that
to -EPROBE_DEFER and succeeds once /lib/firmware is available.
With CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y (inherited from generic),
a missing firmware instead blocks ~60s on the sysfs userspace helper
and returns -ETIMEDOUT. That is not mapped to -EPROBE_DEFER, so NPU
probe fails permanently:
Direct firmware load for airoha/en7581_MT7996_npu_rv32.bin failed with error -2
Falling back to sysfs fallback for: airoha/en7581_MT7996_npu_rv32.bin
error -ETIMEDOUT: failed to run npu firmware
probe with driver airoha-npu failed with error -110
This shows up on official / firmware-selector images because
CONFIG_ALL_KMODS=y builds kmod-leds-lp55xx-common, which implies
FW_LOADER_USER_HELPER and then FALLBACK from generic takes effect.
Match bcm53xx/gemini/layerscape: keep FW_LOADER_USER_HELPER (from
generic) and unset only FALLBACK on an7581/an7583. Unsetting both is
not refresh-safe — FALLBACK depends on USER_HELPER, so
make target/linux/refresh drops the FALLBACK line when USER_HELPER is
off, and ALL_KMODS builds then reintroduce the -ETIMEDOUT failure.
With FALLBACK disabled, early firmware misses keep returning -ENOENT
and deferred probe can load the NPU firmware after rootfs.
Fixes: https://github.com/openwrt/openwrt/issues/22709
Supersedes: https://github.com/openwrt/openwrt/pull/22697
Signed-off-by: Daniel Pawlik <pawlik.dan@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24571
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:29:31 +0200e4e7c4f70c0041b4436d8e2ce048114e83b52d03airoha: disable CONFIG_FW_LOADER_USER_HELPER_FALLBACKedittarget/linux/airoha/an7583/config-6.18edittarget/linux/airoha/an7581/config-6.18
- target/linux/generic/backport-6.18/786-v7.3-net-phy-air_en8811h-move-LED-GPIO-configuration-to-config_init.patch928f5c5ab860779801e36b036c9c0b319230de411788716107000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comkernel: 6.18: fix EN8811H PHY LED GPIO not surviving MCU restart
Currently, the LAN1 LED usually doesn't work on Nokia XG-040G-MD and
Nokia XG-040G-MF devices: it lights up right after boot but goes dark
again as soon as the link renegotiates. Both boards wire LAN1 to a
discrete Airoha EN8811H PHY, whose LED GPIO pins are only ever
configured as outputs once, in en8811h_probe(); every later call to
en8811h_config_init() restarts the PHY's MD32 MCU, which resets that
GPIO configuration back to inputs.
Backport the fix that moves the GPIO-as-output configuration into
en8811h_config_init() so it is reapplied on every MCU restart. This is
a fix to the generic Linux PHY driver (drivers/net/phy/air_en8811h.c),
not something specific to the airoha target: other targets ship the
same PHY via kmod-phy-airoha-en8811h (e.g. mediatek/filogic boards),
so it belongs in target/linux/generic/backport-6.18/ rather than under
target/linux/airoha/.
Merged upstream into net.git by Paolo Abeni as commit 03b4702fc5e3
("net: phy: air_en8811h: move LED GPIO configuration to config_init"),
expected in v7.3. The patch is functionally identical to that commit,
refreshed into OpenWrt's quilt form.
Suggested-by: Mikhail Zhilkin <csharper2005@gmail.com>
Signed-off-by: Vitaliy Sochnev <sochnev.v.74@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24853
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 19:35:07 +0200928f5c5ab860779801e36b036c9c0b319230de41kernel: 6.18: fix EN8811H PHY LED GPIO not surviving MCU restartaddtarget/linux/generic/backport-6.18/786-v7.3-net-phy-air_en8811h-move-LED-GPIO-configuration-to-config_init.patch
- tools/cmake/Makefile50258d2078d3b3c4fe127f72c8d804fa498c62d21788718129000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comtools/cmake: update to version 4.4.3
Update cmake to version 4.4.3.
(No need for patch changes)
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Link: https://github.com/openwrt/openwrt/pull/25043
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:08:49 +020050258d2078d3b3c4fe127f72c8d804fa498c62d2tools/cmake: update to version 4.4.3edittools/cmake/Makefile
- package/kernel/nat46/Makefile76506c10944cb43df7d7b884c9d4504e76d9a9a71788719170000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comnat46: pass NAT46_VERSION through CFLAGS_MODULE
kbuild dropped EXTRA_CFLAGS in 6.15 (e966ad0edd00, "kbuild: remove
EXTRA_*FLAGS support"), so on 6.18 the define never reaches the
compiler and the module logs "nat46: module (version unknown) loaded".
CFLAGS_MODULE is read by both 6.12 and 6.18.
Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/25057
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:26:10 +020076506c10944cb43df7d7b884c9d4504e76d9a9a7nat46: pass NAT46_VERSION through CFLAGS_MODULEeditpackage/kernel/nat46/Makefile
- target/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_ppe_main.cf1a3f07139853ebce2dad2f1fb17fc91a1e157631788719248000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: qca_ppe: accept a multicast delete that is already done
The bridge drops a port's multicast entries on every leave, STP
transition and membership expiry, per port and without tracking which
entries this switch programmed. A delete therefore arrives both for
entries that were never added - the add path runs only for ports in an
offloaded bridge - and for entries an earlier delete already emptied.
ppe_fdb_lookup() reports those as -ENOENT and the driver returned it.
Nothing acts on that return: the object is deleted through switchdev's
deferred queue, where switchdev_port_obj_del_deferred() turns any error
other than -EOPNOTSUPP into a log line and discards it. The error only
produced kernel noise for a state that already matched the request. A
port that is not in the entry's portmap is the same case one step
further in.
Return success for both. The path that drops an entry once its last
member outside the CPU port leaves is unchanged.
Measured on an ipq8074 board with multicast snooping enabled, one group
joined by lan1, lan2 and lan3, and the three ports then removed from
the bridge in turn:
qca-ppe 3a000000.ppe lan3: Failed to del Port Multicast Database
entry (object id=2) with error: -ENOENT (-2).
twice before this change and not at all after it, the ports returning
to the bridge either way.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
Link: https://github.com/openwrt/openwrt/pull/24968
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:27:28 +0200f1a3f07139853ebce2dad2f1fb17fc91a1e15763qualcommax: qca_ppe: accept a multicast delete that is already doneedittarget/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_ppe_main.c
- package/kernel/mac80211/patches/ath12k/200-Revert-wifi-ath12k-convert-tasklet-to-BH-workqueue-f.patch4ab78459bd8d41d3e4af93ce2c8babd4f1f533c71788721070000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commac80211: ath12k: drop the BH workqueue revert
Patch 200 reverted the ath12k conversion from tasklets to BH workqueues.
It arrived with 88f4c32060 ("mac80211: update to version 6.14.11") in May
2025, when main still built kernel 6.6 on 26 targets; BH workqueues only
exist from 6.9, so the revert was doing real work then.
Main now builds 6.12 and 6.18. Both provide system_bh_wq and from_work(),
so there is nothing left for the revert to paper over.
It also leaves the driver inconsistent. backports 7.2 uses intr_wq in
ce.h, pci.c and ahb.c alike, and patch 200 converts only the first two
back to tasklets -- ahb.c was added to the driver after the conversion
landed and never got the same treatment. Building with ATH12K_AHB enabled
therefore fails.
Against pristine backports 7.2 the mac80211 patch series applies 151/151
with this patch removed, and no intr_tq reference survives in ath12k. An
ipq53xx build with ATH12K_AHB enabled links ahb.o cleanly, and the driver
probes an on-chip radio on real hardware.
Bump PKG_RELEASE so existing installs pick up the rebuilt module: it feeds
ABI_VERSION for the kmod packages.
Signed-off-by: Hideo Sumi <hideo.sumi@mugops.com>
Link: https://github.com/openwrt/openwrt/pull/24978
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 20:57:50 +02004ab78459bd8d41d3e4af93ce2c8babd4f1f533c7mac80211: ath12k: drop the BH workqueue revertdeletepackage/kernel/mac80211/patches/ath12k/200-Revert-wifi-ath12k-convert-tasklet-to-BH-workqueue-f.patch
- package/boot/uboot-rockchip/Makefiletarget/linux/rockchip/image/armv8.mke36c1c0caf018a7e476e40711d9fbf3c13a8eae11788721977000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comuboot-rockchip: switch to dedicated profile for NanoPi R76S
Support for NanoPi R76S has been merged upstream u-boot, so use
it instead of the generic profile.
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
Link: https://github.com/openwrt/openwrt/pull/25047
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:12:57 +0200e36c1c0caf018a7e476e40711d9fbf3c13a8eae1uboot-rockchip: switch to dedicated profile for NanoPi R76Seditpackage/boot/uboot-rockchip/Makefileedittarget/linux/rockchip/image/armv8.mk
- package/kernel/rtl8812au-ct/patches/120-cfg80211-7.2.patchpackage/kernel/rtl8812au-ct/Makefile3c1066f412f672d73345c05963437f4ce5e7856b1788722178000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comrtl8812au-ct: fix build with mac80211 7.2
mac80211 7.2 changes cfg80211 key and station operations to take a
wireless_dev instead of a net_device. It also updates station notification
helpers and the remain-on-channel callback.
Adapt the driver to the new API and bump the package release.
Signed-off-by: Alexander Zaguzin <st7105@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25020
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:16:18 +02003c1066f412f672d73345c05963437f4ce5e7856brtl8812au-ct: fix build with mac80211 7.2addpackage/kernel/rtl8812au-ct/patches/120-cfg80211-7.2.patcheditpackage/kernel/rtl8812au-ct/Makefile
- package/network/config/netifd/files/usr/libexec/network/packet-steering.ucpackage/network/config/netifd/Makefilee801f59cff6bb65a4d9555ad995d9ad9fca9049f1788722749000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comnetifd: avoid pinning mt76 TX worker to NAPI CPU
The packet steering script treats both threaded NAPI and the mt76 TX
worker as tasks belonging to the same wireless device. assign_dev_cpu()
then assigns all of these tasks to the same CPU.
This unnecessarily restricts the mt76 TX worker to the NAPI CPU even
though its affinity does not otherwise need to be constrained.
On MT7988A with MT7996 this caused the TX worker to share CPU3 with the
NAPI thread. Moving it to another CPU increased measured TX throughput
from 1.45 Gbit/s to 2.09 Gbit/s.
Stop matching the mt76 TX worker in the packet steering script. This
leaves its CPU affinity unrestricted and lets the scheduler place it
more appropriately.
Fixes: https://github.com/openwrt/openwrt/issues/24697
Signed-off-by: Gary Dotzler <geldot@protonmail.com>
Link: https://github.com/openwrt/openwrt/pull/25016
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-06 21:25:49 +0200e801f59cff6bb65a4d9555ad995d9ad9fca9049fnetifd: avoid pinning mt76 TX worker to NAPI CPUeditpackage/network/config/netifd/files/usr/libexec/network/packet-steering.uceditpackage/network/config/netifd/Makefile
- package/network/services/dropbear/Makefilepackage/network/services/dropbear/Config.infe4bb132561130e85cc87f27691e55ca9ac5cd201788723090000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comdropbear: enable ECDSA by default for backward compatibility
Enable ECDSA by default to:
- Support login with existing ECDSA keys.
- Ensure compatibility with legacy YubiKey devices (e.g., firmware 5.4)
and PIV-based SSH keys (RSA/ECDSA only).
- Maintain access until Ed25519 adoption is widespread.
Default 'y' for all builds except those with SMALL_FLASH.
This activates:
- DROPBEAR_ECC_256 (via DROPBEAR_ECDH || DROPBEAR_ECDSA), enabling
NIST-curve code for non-SMALL_FLASH builds.
- DROPBEAR_SK_ECDSA (default y), offering
sk-ecdsa-sha2-nistp256@openssh.com by default.
Note: Increases only binary size for non-SMALL_FLASH targets.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Link: https://github.com/openwrt/openwrt/pull/24685
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-09-06 19:31:30 +0000fe4bb132561130e85cc87f27691e55ca9ac5cd20dropbear: enable ECDSA by default for backward compatibilityeditpackage/network/services/dropbear/Config.ineditpackage/network/services/dropbear/Makefile
githttps://taiha.net/jenkins/user/mailmailhttps://taiha.net/jenkins/user/danieldanielhttps://taiha.net/jenkins/user/haukehaukehttps://taiha.net/jenkins/user/jelonek.jonasjelonek.jonashttps://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenhttps://taiha.net/jenkins/user/robimarkorobimarkoビルドの安定性: 最近のビルドは失敗してません。icon-health-80plushealth-80plus.png100falsefalseStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WG1400HP/WG1800HP/WG1800HP2 (QCA9558)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWG1400HP/WG1800HP/WG1800HP2 (QCA9558)487fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/generic/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/generic/feeds.buildinfoopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic.manifestopenwrt-ath79-generic.manifestbin/targets/ath79/generic/openwrt-ath79-generic.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/generic/profiles.jsonsha256sumssha256sumsbin/targets/ath79/generic/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/generic/version.buildinfofalsediffconfig: true, device: WG1400HP/WG1800HP/WG1800HP2 (QCA9558)#48734195273023555OpenWrt (master) for NEC Aterm (NetBSD based) #487487falsefalse48752SUCCESS1788751200654https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/487/home-slave02_taihasvgitStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WG1400HP/WG1800HP/WG1800HP2 (QCA9558)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWG1400HP/WG1800HP/WG1800HP2 (QCA9558)487fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/generic/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/generic/feeds.buildinfoopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic.manifestopenwrt-ath79-generic.manifestbin/targets/ath79/generic/openwrt-ath79-generic.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/generic/profiles.jsonsha256sumssha256sumsbin/targets/ath79/generic/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/generic/version.buildinfofalsediffconfig: true, device: WG1400HP/WG1800HP/WG1800HP2 (QCA9558)#48734195273023555OpenWrt (master) for NEC Aterm (NetBSD based) #487487falsefalse48752SUCCESS1788751200654https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/487/home-slave02_taihasvgitStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WG1400HP/WG1800HP/WG1800HP2 (QCA9558)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWG1400HP/WG1800HP/WG1800HP2 (QCA9558)487fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/generic/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/generic/feeds.buildinfoopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic.manifestopenwrt-ath79-generic.manifestbin/targets/ath79/generic/openwrt-ath79-generic.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/generic/profiles.jsonsha256sumssha256sumsbin/targets/ath79/generic/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/generic/version.buildinfofalsediffconfig: true, device: WG1400HP/WG1800HP/WG1800HP2 (QCA9558)#48734195273023555OpenWrt (master) for NEC Aterm (NetBSD based) #487487falsefalse48752SUCCESS1788751200654https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/487/home-slave02_taihasvgitStarted by timer with parameters: {BUILD_CFG_TARGET_DEV=WG1400HP/WG1800HP/WG1800HP2 (QCA9558)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWG1400HP/WG1800HP/WG1800HP2 (QCA9558)487fe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainfe4bb132561130e85cc87f27691e55ca9ac5cd20fe4bb132561130e85cc87f27691e55ca9ac5cd20refs/remotes/origin/mainhttps://github.com/openwrt/openwrtconfig.buildinfoconfig.buildinfobin/targets/ath79/generic/config.buildinfofeeds.buildinfofeeds.buildinfobin/targets/ath79/generic/feeds.buildinfoopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1400hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1400hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-factory.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-initramfs-kernel.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-squashfs-sysupgrade.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic-nec_wg1800hp2-uboot.binbin/targets/ath79/generic/openwrt-ath79-generic-nec_wg1800hp2-uboot.binopenwrt-ath79-generic.manifestopenwrt-ath79-generic.manifestbin/targets/ath79/generic/openwrt-ath79-generic.manifestprofiles.jsonprofiles.jsonbin/targets/ath79/generic/profiles.jsonsha256sumssha256sumsbin/targets/ath79/generic/sha256sumsversion.buildinfoversion.buildinfobin/targets/ath79/generic/version.buildinfofalsediffconfig: true, device: WG1400HP/WG1800HP/WG1800HP2 (QCA9558)#48734195273023555OpenWrt (master) for NEC Aterm (NetBSD based) #487487falsefalse48752SUCCESS1788751200654https://taiha.net/jenkins/job/OpenWrt-master-NEC-BSD-Aterm/487/home-slave02_taihasvgit488BUILD_CFG_DISTCLEANtrue開始前に <code>make distclean</code> を実施BUILD_CFG_DISTCLEANBooleanParameterDefinitionBUILD_CFG_DIFFCONFIGtruediffconfigを使用してビルドBUILD_CFG_DIFFCONFIGBooleanParameterDefinitionBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)ビルド対象機種系統BUILD_CFG_TARGET_DEVChoiceParameterDefinitionWR8750N/WR9500N/WG600HP (AR9344)WG1400HP/WG1800HP/WG1800HP2 (QCA9558)falsefalsehome-slave02_taihasvhudson.plugins.git.GitSCM--ffdefault