Started by timer with parameters: {BUILD_CFG_TARGET_DEV=WR8750N/WR9500N/WG600HP (AR9344)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)498939a6efb1bfc646454d50433f5fb36ea9f4c5eb0939a6efb1bfc646454d50433f5fb36ea9f4c5eb0refs/remotes/origin/main939a6efb1bfc646454d50433f5fb36ea9f4c5eb0939a6efb1bfc646454d50433f5fb36ea9f4c5eb0refs/remotes/origin/main939a6efb1bfc646454d50433f5fb36ea9f4c5eb0939a6efb1bfc646454d50433f5fb36ea9f4c5eb0refs/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)#49822385442207896OpenWrt (master) for NEC Aterm (NetBSD based) #498498falsefalse49863SUCCESS1790552400260https://taiha.net/jenkins/view/all/job/OpenWrt-master-NEC-BSD-Aterm/498/home-slave02_taihasv- target/linux/generic/backport-6.18/800-04-v7.3-net-phy-realtek-load-firmware-for-RTL8261C_CG.patchtarget/linux/generic/pending-6.18/720-04-net-phy-realtek-setup-aldps.patchtarget/linux/generic/pending-6.18/720-08-net-phy-realtek-rate-adapter-in-C22-mode.patchtarget/linux/generic/backport-6.18/800-05-v7.3-net-phy-realtek-add-support-for-RTL8261D.patchtarget/linux/generic/backport-6.18/800-03-v7.3-net-phy-realtek-add-support-for-RTL8261C_CG.patchtarget/linux/generic/pending-6.18/720-07-net-phy-realtek-disable-MDIO-broadcast.patchtarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchtarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchtarget/linux/generic/pending-6.18/720-03-net-phy-realtek-make-sure-paged-read-is-protected-by.patchtarget/linux/generic/backport-6.18/800-01-v7.3-net-phy-c45-add-genphy_c45_pma_soft_reset.patchtarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchtarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchtarget/linux/generic/backport-6.18/800-02-v7.3-net-phy-c45-add-setup-and-read-master-slave-helpers.patchtarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchtarget/linux/generic/pending-6.18/720-06-net-phy-realtek-mark-existing-MMDs-as-present.patchtarget/linux/generic/pending-6.18/720-05-net-phy-realtek-detect-early-version-of-RTL8221B.patchtarget/linux/generic/pending-6.18/720-01-net-phy-realtek-use-genphy_soft_reset-for-2.5G-PHYs.patchtarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patch51478f312267af5756c076199a0528dcc8f10d221790235209000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.degeneric: 6.18: backport RTL8261C/D PHY support
Backport the upstream series adding support for the Realtek RTL8261C_CG
(PHY ID 0x001cc898) and RTL8261D 10Gbps PHYs, merged for v7.3 as
"add-support-for-rtl8261c-d".
Both parts share the PHY ID and are told apart by a sub-PHY-ID read from
the vendor extension page (0x00 for the RTL8261C, 0x81 for the RTL8261D).
The RTL8261C loads rtl_nic/rtl8261c.bin, the RTL8261D needs no firmware.
Two Clause 45 helpers the driver depends on are backported along with it.
3b63c19e64f8 ("net: phy: c45: add genphy_c45_pma_soft_reset()")
d7722c03089e ("net: phy: c45: add setup and read master/slave helpers")
b772b5ae4537 ("net: phy: realtek: add support for RTL8261C_CG")
a04171a1cf32 ("net: phy: realtek: load firmware for RTL8261C_CG")
f0667918d5fc ("net: phy: realtek: add support for RTL8261D")
Refresh various out-of-tree patches in generic and realtek target.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:29 +020051478f312267af5756c076199a0528dcc8f10d22generic: 6.18: backport RTL8261C/D PHY supportedittarget/linux/generic/pending-6.18/720-03-net-phy-realtek-make-sure-paged-read-is-protected-by.patchaddtarget/linux/generic/backport-6.18/800-05-v7.3-net-phy-realtek-add-support-for-RTL8261D.patchedittarget/linux/generic/pending-6.18/720-01-net-phy-realtek-use-genphy_soft_reset-for-2.5G-PHYs.patchedittarget/linux/generic/pending-6.18/720-06-net-phy-realtek-mark-existing-MMDs-as-present.patchedittarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patchedittarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchaddtarget/linux/generic/backport-6.18/800-01-v7.3-net-phy-c45-add-genphy_c45_pma_soft_reset.patchedittarget/linux/generic/pending-6.18/720-07-net-phy-realtek-disable-MDIO-broadcast.patchedittarget/linux/generic/pending-6.18/720-08-net-phy-realtek-rate-adapter-in-C22-mode.patchaddtarget/linux/generic/backport-6.18/800-04-v7.3-net-phy-realtek-load-firmware-for-RTL8261C_CG.patchaddtarget/linux/generic/backport-6.18/800-02-v7.3-net-phy-c45-add-setup-and-read-master-slave-helpers.patchaddtarget/linux/generic/backport-6.18/800-03-v7.3-net-phy-realtek-add-support-for-RTL8261C_CG.patchedittarget/linux/generic/pending-6.18/720-05-net-phy-realtek-detect-early-version-of-RTL8221B.patchedittarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchedittarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchedittarget/linux/generic/pending-6.18/720-04-net-phy-realtek-setup-aldps.patchedittarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchedittarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patch
- target/linux/generic/pending-6.18/720-04-net-phy-realtek-setup-aldps.patchtarget/linux/generic/pending-6.18/720-08-net-phy-realtek-rate-adapter-in-C22-mode.patchtarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchtarget/linux/generic/pending-6.18/720-07-net-phy-realtek-disable-MDIO-broadcast.patchtarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchtarget/linux/generic/pending-6.18/720-03-net-phy-realtek-make-sure-paged-read-is-protected-by.patchtarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchtarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchtarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchtarget/linux/generic/pending-6.18/720-06-net-phy-realtek-mark-existing-MMDs-as-present.patchtarget/linux/generic/backport-6.18/800-06-v7.4-net-phy-realtek-add-support-for-RTL8261CE_CG.patchtarget/linux/generic/pending-6.18/720-05-net-phy-realtek-detect-early-version-of-RTL8221B.patchtarget/linux/generic/pending-6.18/720-01-net-phy-realtek-use-genphy_soft_reset-for-2.5G-PHYs.patchtarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patch393bd191d4b472627d3f529556cd4af352b094791790235210000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.degeneric: 6.18: backport RTL8261CE_CG PHY support
Backport support for the Realtek RTL8261CE_CG (PHY ID 0x001cc899),
merged for v7.4. It shares the sub-PHY-ID and the firmware with the
RTL8261C_CG.
ca44c21fc117 ("net: phy: realtek: add support for RTL8261CE_CG")
Parts reporting this PHY ID fall through to the generic Clause 45
driver. Both 10G ports of the Gemtek W1700K carry one and never come up.
The patch applies before the out-of-tree
742-net-phy-realtek-add-5G-and-10G-PHY-support.patch, which is where the
RTL_8261N/RTL_8264/RTL_8264B context around the new define comes from, so
742 gains the RTL_8261CE_CG define as context.
Refresh various out-of-tree patches in generic and realtek target.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:30 +0200393bd191d4b472627d3f529556cd4af352b09479generic: 6.18: backport RTL8261CE_CG PHY supportaddtarget/linux/generic/backport-6.18/800-06-v7.4-net-phy-realtek-add-support-for-RTL8261CE_CG.patchedittarget/linux/generic/pending-6.18/720-06-net-phy-realtek-mark-existing-MMDs-as-present.patchedittarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchedittarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchedittarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchedittarget/linux/generic/pending-6.18/720-01-net-phy-realtek-use-genphy_soft_reset-for-2.5G-PHYs.patchedittarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchedittarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchedittarget/linux/generic/pending-6.18/720-03-net-phy-realtek-make-sure-paged-read-is-protected-by.patchedittarget/linux/generic/pending-6.18/720-07-net-phy-realtek-disable-MDIO-broadcast.patchedittarget/linux/generic/pending-6.18/720-04-net-phy-realtek-setup-aldps.patchedittarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patchedittarget/linux/generic/pending-6.18/720-05-net-phy-realtek-detect-early-version-of-RTL8221B.patchedittarget/linux/generic/pending-6.18/720-08-net-phy-realtek-rate-adapter-in-C22-mode.patch
- target/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchtarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchtarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchtarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchtarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchtarget/linux/generic/pending-6.18/721-01-net-phy-realtek-apply-SerDes-lane-polarity-on-RTL8261.patchtarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patchfce07ce378fc5fde27fe0f177f8b769f2d7c51371790235210000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.degeneric: net: phy: realtek: apply SerDes lane polarity on RTL8261C/D
The Gemtek W1700K routes the USXGMII lanes between the AN7581 and its
RTL8261CE inverted and describes that in the device tree, but nothing in
the RTL8261C/D driver reads tx-polarity/rx-polarity and the Airoha PCS
has no polarity handling of its own. The copper side negotiates normally
while the SerDes never trains and the netdev stays NO-CARRIER.
Add a read and a read-modify-write helper for the VEND1 SerDes command
window and program the lane polarity from rtl8261x_config_init().
Submitted upstream as part of a series documenting the RTL8261C/D device
tree bindings and adding SerDes lane polarity and LED support.
Apply it ahead of the out-of-tree
742-net-phy-realtek-add-5G-and-10G-PHY-support.patch so it can be carried
exactly as submitted. 742 drops its own select PHY_COMMON_PROPS and its
phy-common-props.h include, as both come from here now. Once accepted
upstream this patch only moves to backports, so they stay dropped.
Refresh out-of-tree patches in realtek target.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:30 +0200fce07ce378fc5fde27fe0f177f8b769f2d7c5137generic: net: phy: realtek: apply SerDes lane polarity on RTL8261C/Daddtarget/linux/generic/pending-6.18/721-01-net-phy-realtek-apply-SerDes-lane-polarity-on-RTL8261.patchedittarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patchedittarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchedittarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchedittarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchedittarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchedittarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patch
- target/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchtarget/linux/generic/pending-6.18/721-02-net-phy-realtek-add-LED-support-for-RTL8261C-D.patchtarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patchtarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchtarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchtarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchtarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patch714786c3d3f995d53639514279571a28e64b63f81790235210000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.degeneric: net: phy: realtek: add LED support for RTL8261C/D
The RTL8261C/D drive their LEDs through the same register block as the
RTL8221B, with four LEDs instead of three and two more speed bits. Wire
the callbacks to the RTL8261C_CG and RTL8261CE_CG entries so the 10G
ports of the Gemtek W1700K can be driven from the netdev trigger instead
of coming up dark.
Submitted upstream in the same series as the SerDes lane polarity patch.
Apply it ahead of the out-of-tree
742-net-phy-realtek-add-5G-and-10G-PHY-support.patch as well, so it too
can be carried exactly as submitted. 742's realtek_drvs[] hunk is rebased
on top of it, which only moves its leading context.
Refresh out-of-tree patches in realtek target.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:30 +0200714786c3d3f995d53639514279571a28e64b63f8generic: net: phy: realtek: add LED support for RTL8261C/Daddtarget/linux/generic/pending-6.18/721-02-net-phy-realtek-add-LED-support-for-RTL8261C-D.patchedittarget/linux/generic/pending-6.18/742-net-phy-realtek-add-5G-and-10G-PHY-support.patchedittarget/linux/realtek/patches-6.18/030-v7.2-net-phy-realtek-support-MDI-swapping-for-RTL8226-CG.patchedittarget/linux/realtek/patches-6.18/743-net-realtek-serdes-configuration.patchedittarget/linux/realtek/patches-6.18/024-04-v7.1-net-phy-realtek-add-RTL8224-polarity-support.patchedittarget/linux/realtek/patches-6.18/024-02-v7.1-net-phy-realtek-add-RTL8224-pair-order-support.patchedittarget/linux/generic/pending-6.18/743-net-phy-realtek-reset-RTL8261N-USXGMII-SerDes-on-lin.patch
- package/firmware/linux-firmware/realtek.mkpackage/firmware/linux-firmware/Makefilee14c7032256e98d92608378a0e8978fb8cd1ecc71790235211000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.delinux-firmware: add rtl8261c-firmware package
The realtek PHY driver requests rtl_nic/rtl8261c.bin for the RTL8261C.
The blob has been in linux-firmware since 2026-05-28 and is present in
the 20260910 tarball already used here, but it is not matched by any of
the r8169-firmware globs, so nothing installs it today.
The RTL8261D handled by the same phy_driver entry needs no firmware, so
this stays a standalone package rather than a kmod-phy-realtek
dependency, which would pull the blob onto every board with any Realtek
PHY.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:31 +0200e14c7032256e98d92608378a0e8978fb8cd1ecc7linux-firmware: add rtl8261c-firmware packageeditpackage/firmware/linux-firmware/Makefileeditpackage/firmware/linux-firmware/realtek.mk
- target/linux/airoha/image/an7581.mk5d0c4349adcb2204785fd3117999d97238d584e71790235211000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deairoha: an7581: add rtl8261c-firmware to the Gemtek W1700K
Hardware revisions of this board ship either an RTL8261N, handled by the
out-of-tree RTL826x driver, or an RTL8261CE, handled by the mainline
driver. The two need different firmware and the revision is not known at
image build time, so ship both.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:31 +02005d0c4349adcb2204785fd3117999d97238d584e7airoha: an7581: add rtl8261c-firmware to the Gemtek W1700Kedittarget/linux/airoha/image/an7581.mk
- target/linux/airoha/dts/an7581-w1700k-ubi.dtstarget/linux/airoha/an7581/base-files/etc/board.d/01_leds18304dd7474dcc2df040f1426c4e6d3f0dedb9b51790235212000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deairoha: an7581: add PHY LEDs for the Gemtek W1700K
Both 10G ports have a yellow and a green LED driven by the RTL8261CE
rather than by GPIO. Index 2 is yellow, index 3 green. The
index-to-colour mapping was determined empirically by inverting the
polarity bits in VEND2 0xd044 one at a time.
Configure the triggers to match the 1G ports on this board, where green
means gigabit: yellow for 10/100, green from 1000 up, and both together
for 10000. Without this the LEDs come up with no trigger and stay dark,
losing the firmware defaults they had before.
The indices were only verified on an RTL8261CE. Board revisions carrying an
RTL8261N are unaffected for now since that driver has no LED callbacks, but
the mapping should be rechecked there before relying on it.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Simon Polack <spolack+git@mailbox.org>
Link: https://github.com/openwrt/openwrt/pull/25092
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-24 09:33:32 +020018304dd7474dcc2df040f1426c4e6d3f0dedb9b5airoha: an7581: add PHY LEDs for the Gemtek W1700Kedittarget/linux/airoha/dts/an7581-w1700k-ubi.dtsedittarget/linux/airoha/an7581/base-files/etc/board.d/01_leds
- scripts/belkin-header.py98bc30d154f67557598a2114463e9b97c915463d1790249809000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgrealtek: take the Belkin header time from SOURCE_DATE_EPOCH
The factory images of the Linksys LGS3xxC switches differ between
builds in the Belkin header:
-00000000: 0780 0001 7917 f807 6ab3 0fe3 0058 2000 ....y...j....X .
+00000000: 0780 0001 2a5a 3f79 6ab3 d0c7 0058 2000 ....*Z?yj....X .
belkin-header.py stores time.time() as the image time, which also
changes the header checksum. Use SOURCE_DATE_EPOCH when it is set, like
linksys-image.sh does for the tarball inside.
Link: https://github.com/openwrt/openwrt/pull/25355
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-24 13:36:49 +020098bc30d154f67557598a2114463e9b97c915463drealtek: take the Belkin header time from SOURCE_DATE_EPOCHeditscripts/belkin-header.py
- target/linux/generic/hack-6.18/780-usb-net-MeigLink_modem_support.patchtarget/linux/generic/backport-6.18/787-v7.3-net-usb-qmi_wwan-add-Quectel-EG120K-EA.patch23bebd5c32f994ca44a23aff65dff878f82fb7ba1790255078000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comkernel: qmi_wwan: add support for Quectel EG120K-EA
The Quectel EG120K-EA (LTE Cat.12) reports USB ID 2c7c:030b and exposes
its QMI/RMNET function on a vendor-specific ff/ff/ff interface. The same
product ID is already known to the option driver as EM060K, which claims
the serial interfaces, but without a qmi_wwan entry the data interface is
left unbound and no cdc-wdm node appears.
Add the device using QMI_MATCH_FF_FF_FF so the DTR quirk is applied.
Tested on a GL.iNet GL-X2000, where the modem enumerates at SuperSpeed and
now brings up cdc-wdm0 and wwan0. A data session over MEO (268-06) was
verified end to end.
Accepted upstream via netdev/net, so this is carried as a backport and can
be dropped once the kernel is bumped to 7.3 or later. Inserting it ahead of
the MeigLink hack shifts that patch's offsets, so
780-usb-net-MeigLink_modem_support.patch is refreshed as well.
Link: https://patch.msgid.link/20260921093426.2870266-1-gilbertorconde@gmail.com
Signed-off-by: Gilberto Conde <gilbertorconde@gmail.com>
2026-09-24 15:04:38 +020023bebd5c32f994ca44a23aff65dff878f82fb7bakernel: qmi_wwan: add support for Quectel EG120K-EAedittarget/linux/generic/hack-6.18/780-usb-net-MeigLink_modem_support.patchaddtarget/linux/generic/backport-6.18/787-v7.3-net-usb-qmi_wwan-add-Quectel-EG120K-EA.patch
- target/linux/airoha/patches-6.18/402-06-thermal-drivers-airoha-serialise-access-to-the-shared-ADC.patch53e165762c16ad6891efe20f36ba3a3e7f2e0fef1790255135000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comairoha: thermal: serialise access to the shared ADC
Two thermal zones reading the shared ADC at once interleave and convert
another sensor's diodes with the wrong constants. On AN7583 the zone
carrying the critical trip crossed 120 C on a chip at 55 C, shutting the
board down.
Serialise the sequence, read the mux selection back instead of caching
it, check it again after sampling and refuse to divide by a zero gain.
Signed-off-by: Vitaliy Sochnev <sochnev.v.74@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25147
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 15:05:35 +020053e165762c16ad6891efe20f36ba3a3e7f2e0fefairoha: thermal: serialise access to the shared ADCaddtarget/linux/airoha/patches-6.18/402-06-thermal-drivers-airoha-serialise-access-to-the-shared-ADC.patch
- target/linux/airoha/dts/an7583.dtsitarget/linux/airoha/patches-6.18/402-07-thermal-drivers-airoha-read-all-three-AN7583-sensors.patch0a7d2ceb9b65df14fe0f70f2d26c939a324161951790255135000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comairoha: an7583: expose all three temperature sensors
The driver carried the constants for all three sensors but registered
one zone and read only the bandgap one. Register a zone per sensor and
add two zones to the device tree.
The bandgap sensor stays zone 0 with its trips and cooling map.
#thermal-sensor-cells goes from 0 to 1.
Signed-off-by: Vitaliy Sochnev <sochnev.v.74@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25147
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 15:05:35 +02000a7d2ceb9b65df14fe0f70f2d26c939a32416195airoha: an7583: expose all three temperature sensorsedittarget/linux/airoha/dts/an7583.dtsiaddtarget/linux/airoha/patches-6.18/402-07-thermal-drivers-airoha-read-all-three-AN7583-sensors.patch
- target/linux/qualcommbe/image/ipq95xx.mk2c0a72ffe9c8ccd62e6b2214e5101605f89caabf1790255278000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommbe: ipq95xx: SBE1V1K: fix boot failure via kernel loadaddr
The Charter Spectrum SBE1V1K fails to boot with the default kernel
load address. The device gets stuck early in the boot process due to
the stock bootloader encountering memory overlap or alignment issues
with the default `0x41000000` address.
Changing `KERNEL_LOADADDR` to `0x42200000` resolves the boot failure
and ensures stable operation.
Why `0x42200000` instead of `0x42000000`?
While testing showed that `0x42000000` also boots successfully,
`0x42200000` was explicitly chosen for two primary safety reasons:
1. Avoid U-Boot `loadaddr` Overlap: On many QCA/IPQ platforms,
`0x42000000` is commonly used as the default `loadaddr` to fetch
the FIT image into memory. Setting the extraction destination
(`KERNEL_LOADADDR`) to the exact same base address risks in-place
decompression overlaps.
2. Reserved Memory Buffer: The memory range below `0x42000000`
is heavily utilized by TZ, SMEM, and vendor-specific reserved
memory in newer Askey firmwares. Adding a 2MB aligned offset
(`0x200000`) provides a safer buffer against shifting vendor
memory boundaries in future OEM bootloader updates, while still
strictly satisfying the ARM64 2MB alignment requirement.
This fix and the `0x42200000` address have been successfully tested
on actual SBE1V1K hardware by community member motolav.
Link: https://forum.openwrt.org/t/spectrum-sbe1v1k-ipq9574-openwrt-support/245244/262
Tested-by: motolav <https://forum.openwrt.org/u/motolav>
Signed-off-by: Jackie Han <jackie.han@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25344
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 15:07:58 +02002c0a72ffe9c8ccd62e6b2214e5101605f89caabfqualcommbe: ipq95xx: SBE1V1K: fix boot failure via kernel loadaddredittarget/linux/qualcommbe/image/ipq95xx.mk
- target/linux/generic/backport-6.18/950-v7.3-cgroup-fix-spurious-SIGKILL-of-CLONE_INTO_CGROUP-children.patchtarget/linux/bcm27xx/patches-6.18/0504-cgroup-Add-cgroup_enable-option.patch8b7604f90a872366e956333001ac16960832b80b1790257260000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orggeneric: backport cgroup CLONE_INTO_CGROUP SIGKILL fix
Since b69bb476dee9 ("cgroup: fix race between fork and cgroup.kill") the
fork path snapshots kill_seq in cgroup_css_set_fork() before the
CLONE_INTO_CGROUP target has been resolved, so it always records the
forking task's own cgroup while cgroup_post_fork() reads the target's
and compares the two. Once cgroup.kill has been written to a cgroup,
every child later cloned out of it into another cgroup is SIGKILLed
before it runs a single instruction, for as long as that cgroup exists.
This breaks re-creating an OCI container under procd, whose service
supervisor kills the instance cgroup on exit and leaves it in place: the
container init ujail clones with CLONE_INTO_CGROUP is killed at birth and
the create fails with no diagnostic. The fix is in mainline from v7.3-rc2
and carries Cc: stable, so it is expected to reach 6.18.y with a future
stable release, at which point this patch can be dropped.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2026-09-24 14:41:00 +01008b7604f90a872366e956333001ac16960832b80bgeneric: backport cgroup CLONE_INTO_CGROUP SIGKILL fixedittarget/linux/bcm27xx/patches-6.18/0504-cgroup-Add-cgroup_enable-option.patchaddtarget/linux/generic/backport-6.18/950-v7.3-cgroup-fix-spurious-SIGKILL-of-CLONE_INTO_CGROUP-children.patch
- package/boot/apex/Makefilee2aa1d759647837a9e82e22ed5db9a3b79b27cc21790263388000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgapex: take the build date from SOURCE_DATE_EPOCH
The APEX boot loader embeds the time of the build in its version
banner, which makes the Iomega NAS100D factory image differ between
builds:
-compiled for OpenWrt NAS100D/BE on 2026.Sep.23-04:17:21
+compiled for OpenWrt NAS100D/BE on 2026.Sep.23-11:06:03
APEX sets BUILDDATE with $(shell date) in its top level Makefile. Pass
BUILDDATE on the command line, formatted from SOURCE_DATE_EPOCH in UTC
and the C locale, which overrides it for all sub-makes.
Link: https://github.com/openwrt/openwrt/pull/25354
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-24 17:23:08 +0200e2aa1d759647837a9e82e22ed5db9a3b79b27cc2apex: take the build date from SOURCE_DATE_EPOCHeditpackage/boot/apex/Makefile
- target/linux/ath79/dts/qca9558_jjplus_jwap230.dtstarget/linux/ath79/dts/qca9558_tplink_tl-wr1043nd.dtsitarget/linux/ath79/dts/ar9344_mikrotik_routerboard-2011uias-2hnd.dtstarget/linux/ath79/dts/ar9344_tplink_tl-wdr4300.dtsitarget/linux/ath79/dts/ar7242_ubnt_edgeswitch-5xp.dts50d7282818513e4116a042065d678fdece41a4741790269024000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comath79: fix switch addresses for atheros switches
The driver doesn't really care about the address in dts, but might as
well fix it anyway.
0 is just wrong.
1f is the address for the builtin FE switch, not the external gigabit
switch.
10 is the driver default.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25370
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 18:57:04 +020050d7282818513e4116a042065d678fdece41a474ath79: fix switch addresses for atheros switchesedittarget/linux/ath79/dts/qca9558_jjplus_jwap230.dtsedittarget/linux/ath79/dts/ar9344_mikrotik_routerboard-2011uias-2hnd.dtsedittarget/linux/ath79/dts/ar9344_tplink_tl-wdr4300.dtsiedittarget/linux/ath79/dts/qca9558_tplink_tl-wr1043nd.dtsiedittarget/linux/ath79/dts/ar7242_ubnt_edgeswitch-5xp.dts
- target/linux/ramips/image/mt7621.mkeb2bd0cc0875b05fc0bc18129aa12d8bb277f6051790269126000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comramips: mt7621: add MMC driver for SD compatible MikroTik devices
These devices have SD card slots. Add MMC driver package by default
so that users can use it out of the box.
Closes: https://github.com/openwrt/openwrt/issues/25099
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/25351
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 18:58:46 +0200eb2bd0cc0875b05fc0bc18129aa12d8bb277f605ramips: mt7621: add MMC driver for SD compatible MikroTik devicesedittarget/linux/ramips/image/mt7621.mk
- target/linux/mediatek/filogic/base-files/etc/board.d/01_ledsbafaf2665a7f57ce7ea1fb3e0532f382635ced231790269434000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commediatek: filogic: light the Internet LED on Cudy WR3000S v1
The WR3000S has a GPIO LED behind its front-panel "Internet" lamp
(white:wan-online, &pio 11), but no board.d entry, so no trigger is ever
set and the lamp stays dark. Give it the same netdev trigger the WR3000H
and WR3000P already use for their white:wan-online LED: follow the link
state of the wan port. As on those boards, "link" means the wan port has
carrier, not that connectivity works.
The panel's WAN and LAN1-4 lamps are not GPIO LEDs and are not registered
as Linux LEDs at all; they light on link in hardware, so board.d cannot
address them and they are untouched here. The -ubootmod variant includes
the same mt7981b-cudy-wr3000s-v1.dtsi, and so the identical LED, and is
listed alongside.
Tested on a WR3000S v1 (OEM layout), on an image built from main at
6727587d24 plus this commit: after a config-wipe sysupgrade the board.d
entry is applied automatically (board.json -> system.led_internet), the
lamp lights while the WAN port has link, and it goes dark when it loses
link. Only the OEM-layout variant was flashed.
Signed-off-by: Ivan Rainbolt <ivan@github.ivanthegeek.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Link: https://github.com/openwrt/openwrt/pull/25335
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 19:03:54 +0200bafaf2665a7f57ce7ea1fb3e0532f382635ced23mediatek: filogic: light the Internet LED on Cudy WR3000S v1edittarget/linux/mediatek/filogic/base-files/etc/board.d/01_leds
- target/linux/mvebu/patches-6.18/303-mvebu-armada-38x-errata.patchtarget/linux/mvebu/config-6.18bebe3e4588aa63bd1e6a62229fef87f06e84f0691790269545000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.commvebu: fix Armada 38x errata
Armada 38x uses Cortex-A9 r4p1, but the current kernel config selects
erratum 720789, which was fixed in r2p0, and omits some errata that
still affect r4p1. Fix the config.
Signed-off-by: Qingfang Deng <dqfext@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25297
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 19:05:45 +0200bebe3e4588aa63bd1e6a62229fef87f06e84f069mvebu: fix Armada 38x errataedittarget/linux/mvebu/config-6.18addtarget/linux/mvebu/patches-6.18/303-mvebu-armada-38x-errata.patch
- target/linux/kirkwood/config-6.188f4161ef6ee1955e6fbad1382f2c7077bf3d1ca01790269847000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comkirkwood: enable cpufreq and cpuidle
This appears to reduce the CPU temp by at least a few degrees C on
Linksys EA4500, which is notorious for its thermal challenges.
Tested only on EA4500 by running without issues for a few weeks under a
light workload.
Signed-off-by: Will Mortensen <willmo@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25276
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-24 19:10:47 +02008f4161ef6ee1955e6fbad1382f2c7077bf3d1ca0kirkwood: enable cpufreq and cpuidleedittarget/linux/kirkwood/config-6.18
- package/network/services/hostapd/patches/780-Implement-APuP-Access-Point-Micro-Peering.patchd6c5598e2ff78e2ae18656ace00a7c84f6ee74f61790277650000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dehostapd: fix NULL pointer dereference in APuP beacon handling
apup_process_beacon() dereferenced the return value of ap_sta_add()
without checking it. ap_sta_add() returns NULL when the station table is
full, when the allocation fails or when accounting_sta_get_id() fails,
so the following read of sta_ret->aid dereferences NULL.
The station table filling up is remotely triggerable. Beacons reach
handle_beacon() on every softmac driver, because hostapd subscribes to
them per wiphy with NL80211_CMD_REGISTER_BEACONS when it starts the AP.
An adjacent station can therefore beacon the target's SSID from
successive spoofed BSSIDs, each of which is added as an APuP peer, until
max_num_sta is reached and hostapd crashes.
CONFIG_APUP=y is set unconditionally in DRIVER_MAKEOPTS, so the code is
compiled into every wpad variant, but the call is gated on
hapd->conf->apup at runtime and wifi-scripts defaults apup to 0. Only
configurations that opt into APuP are affected.
Reported-by: JuliusBairaktaris
Fixes: e80520197c9c ("hostapd: Add support for APuP")
Assisted-by: Claude:claude-opus-5
Link: https://github.com/openwrt/openwrt/pull/25242
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-24 21:20:50 +0200d6c5598e2ff78e2ae18656ace00a7c84f6ee74f6hostapd: fix NULL pointer dereference in APuP beacon handlingeditpackage/network/services/hostapd/patches/780-Implement-APuP-Access-Point-Micro-Peering.patch
- package/network/services/hostapd/patches/780-Implement-APuP-Access-Point-Micro-Peering.patch73e10e74328d58930577f100b9dd01bc8ea6edd51790277658000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dehostapd: free the APuP peer when no AID is available
apup_process_beacon() adds the peer with ap_sta_add() and only asks for
an AID with hostapd_get_aid() further down. When that fails the function
returns without undoing anything, leaving the station in hapd->sta_list
with WLAN_STA_AUTH set but with no AID, no WLAN_STA_ASSOC and no WDS
interface. The driver entry added by the preceding hostapd_sta_add() and
the hapd->num_sta reference are leaked as well.
The leftover entry is then found by the ap_get_sta() check at the top of
the function, so every later beacon from that BSSID returns early and
the peer can never be set up again until hostapd is restarted.
Release the half-initialised station with ap_free_sta(), which removes
the driver entry, cancels the inactivity timer registered by
ap_sta_add(), unlinks it from the list and drops the counters.
Fixes: e80520197c9c ("hostapd: Add support for APuP")
Assisted-by: Claude:claude-opus-5
Link: https://github.com/openwrt/openwrt/pull/25242
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-24 21:20:58 +020073e10e74328d58930577f100b9dd01bc8ea6edd5hostapd: free the APuP peer when no AID is availableeditpackage/network/services/hostapd/patches/780-Implement-APuP-Access-Point-Micro-Peering.patch
- package/network/services/hostapd/patches/600-ubus_support.patchpackage/network/services/hostapd/Makefile18a969c475807ed384b20e02c6adf80e48fc09ca1790277658000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dehostapd: restore Link Measurement Report handling
The ubus notification for link measurements was added by replacing the
call to hostapd_handle_link_mesr_report() instead of adding to it, so
upstream's handler lost its only caller and is compiled out as dead
code, which the build shows as:
src/ap/rrm.c:354:13: warning: 'hostapd_handle_link_mesr_report'
defined but not used [-Wunused-function]
As a result nothing clears hapd->link_mesr_req_active or cancels
hostapd_link_mesr_rep_timeout_handler() when a report arrives, so a
REQ_LINK_MEASUREMENT issued over the control interface always ends in a
timeout even though the report was received, and the LINK-MSR-RESP-RX
event carrying the report is never emitted.
Call both handlers, which is how the ubus hook for beacon reports a few
lines above is wired up too.
Fixes: f6445cfa1acb ("hostapd: add ubus link-measurements notifications")
Assisted-by: Claude:claude-opus-5
Link: https://github.com/openwrt/openwrt/pull/25242
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-24 21:20:58 +020018a969c475807ed384b20e02c6adf80e48fc09cahostapd: restore Link Measurement Report handlingeditpackage/network/services/hostapd/Makefileeditpackage/network/services/hostapd/patches/600-ubus_support.patch
- scripts/target-metadata.pl1b85ec12b37dcc70be71671be5773d2e3e2c3f061790285608000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orgbuild: indent the generated PWM_SUPPORT select
"\s" is not an escape sequence in a Perl double-quoted string, so the
pwm feature emits its select statement without the leading tab that
every other feature gets. Kconfig accepts the unindented line, but the
generated target/Config.in is inconsistent.
Fixes: f6fbc397066e ("build: define PWM_SUPPORT arch feature flag")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2026-09-24 22:33:28 +01001b85ec12b37dcc70be71671be5773d2e3e2c3f06build: indent the generated PWM_SUPPORT selecteditscripts/target-metadata.pl
- target/linux/lantiq/xrx200_legacy/target.mktarget/linux/lantiq/xway_legacy/target.mktarget/linux/lantiq/xway/target.mktarget/linux/lantiq/ase/target.mktarget/linux/lantiq/xrx200/target.mk9489ba0163bb9e0bea004c8b11885b86f3c3cf111790285608000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orglantiq: drop the unread atm target feature
The atm feature has no entry in target_config_features(), so it selects
no symbol, and nothing else reads the feature list beyond the broken and
source-only filters. It has never gated anything. The kmod-ltq-atm-*
packages are unrelated name matches, pulled in through DEFAULT_PACKAGES.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2026-09-24 22:33:28 +01009489ba0163bb9e0bea004c8b11885b86f3c3cf11lantiq: drop the unread atm target featureedittarget/linux/lantiq/ase/target.mkedittarget/linux/lantiq/xrx200_legacy/target.mkedittarget/linux/lantiq/xrx200/target.mkedittarget/linux/lantiq/xway_legacy/target.mkedittarget/linux/lantiq/xway/target.mk
- scripts/target-metadata.plconfig/Config-images.intarget/Config.inad1b1f2d36aacf13e3f983a1bdf4d699ef929ae31790285608000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orgbuild: gate the VM image formats on their target features
The x86 and armsr targets declare the vdi, vmdk and vhdx features, but
VDI_IMAGES, VMDK_IMAGES and VHDX_IMAGES depend on a hardcoded target
list instead, so the features select nothing and a target opting in has
to edit config/Config-images.in.
Give them USES_VDI, USES_VMDK and USES_VHDX in the same shape as the
other image formats and depend on those. The set of targets offering
each format is unchanged.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2026-09-24 22:33:28 +0100ad1b1f2d36aacf13e3f983a1bdf4d699ef929ae3build: gate the VM image formats on their target featureseditscripts/target-metadata.pleditconfig/Config-images.inedittarget/Config.in
- include/bpf.mkrules.mk6c03a267b09b2d8bd7ddd4f6e7e702efe71202f11790320427000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgbuild: bpf: remap build paths in BTF line info
CompileBPF calls clang with -g but without any prefix map. Stripping debug info
keeps .BTF and .BTF.ext, since libbpf needs them, and their line info carries
the absolute path of each source file. This makes BPF objects like qosify-bpf.o
depend on the build directory and breaks reproducibility:
-/builder/shared-workdir/build/build_dir/.../qosify-bpf.c
+/tmp/rebuilderd-openwrt.juCsuQ/src/build_dir/.../qosify-bpf.c
IREMAP_CFLAGS is not enough here: without CONFIG_REPRODUCIBLE_DEBUG_INFO it
only sets -fmacro-prefix-map, which leaves the line info alone, and it is empty
for external toolchains, which have no say over the host clang. Unlike regular
debug info, BTF ships with the package, so always pass -ffile-prefix-map for
the build and staging directories.
Add an fremap helper next to iremap for that, and let IREMAP_STAGING_DIR and
CompileBPF share the map of the staging directory, so they cannot drift apart.
Link: https://github.com/openwrt/openwrt/pull/25359
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-25 09:13:47 +02006c03a267b09b2d8bd7ddd4f6e7e702efe71202f1build: bpf: remap build paths in BTF line infoeditinclude/bpf.mkeditrules.mk
- target/linux/realtek/base-files/etc/board.d/02_networktarget/linux/realtek/dts/rtl8380_netgear_gs110tpp-v1.dtstarget/linux/realtek/image/rtl838x.mkded52f63db1bcf72880159d20d511f4b1a6629cb1790322181000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: gs110tpp: switch to PSE driver
Use the realtek-pse-mcu kernel driver instead of realtek-poe. The MCU
is a Nuvoton M05xx using the gen1 protocol over UART at 19200 baud.
realtek-poe turns off the MCU's port mapping at startup, which reversed
the PoE port numbering and the front-panel PoE LEDs. The kernel driver
leaves the mapping alone, so both now match the front panel. The MCU
keeps this state across a warm reboot, so a unit sysupgraded from a
realtek-poe image stays reversed until its first power cycle.
Tested on a GS110TPP v1: the driver probes the MCU and its BCM59121,
and a PoE device on lan1 is powered.
Signed-off-by: Kel Modderman <kelvmod@gmail.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Link: https://github.com/openwrt/openwrt/pull/25298
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:43:01 +0200ded52f63db1bcf72880159d20d511f4b1a6629cbrealtek: gs110tpp: switch to PSE driveredittarget/linux/realtek/dts/rtl8380_netgear_gs110tpp-v1.dtsedittarget/linux/realtek/image/rtl838x.mkedittarget/linux/realtek/base-files/etc/board.d/02_network
- target/linux/bcm53xx/config-6.18target/linux/bcm53xx/patches-6.18/370-usb-bcma-add-regulator-support.patchtarget/linux/bcm53xx/patches-6.18/310-ARM-BCM5301X-Add-DT-for-Netgear-R7900.patchtarget/linux/bcm53xx/patches-6.18/352-v7.2-ARM-dts-BCM5301X-EA9200-fix-nvram-size.patchtarget/linux/bcm53xx/patches-6.18/371-ARM-dts-broadcom-model-USB-VBUS-power-with-regulator.patchtarget/linux/bcm53xx/patches-6.18/362-ARM-dts-BCM5301X-EA6300-fix-USB3.patchtarget/linux/bcm53xx/patches-6.18/352-ARM-dts-BCM5301X-EA9200-fix-nvram-size.patchd2595dff03ea1b690815d25d8e680594c8e9e27e1790322526000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debcm53xx: use regulators for USB control
Some of these GPIOs are shared between interfaces. Use a regulator to be
able to share them. Enable Kconfig options so that they work.
Backport one patch upstream so the patch applies. Rename another to
clarify it's in 7.2.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25296
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:48:46 +0200d2595dff03ea1b690815d25d8e680594c8e9e27ebcm53xx: use regulators for USB controldeletetarget/linux/bcm53xx/patches-6.18/352-ARM-dts-BCM5301X-EA9200-fix-nvram-size.patchaddtarget/linux/bcm53xx/patches-6.18/371-ARM-dts-broadcom-model-USB-VBUS-power-with-regulator.patchaddtarget/linux/bcm53xx/patches-6.18/370-usb-bcma-add-regulator-support.patchedittarget/linux/bcm53xx/config-6.18addtarget/linux/bcm53xx/patches-6.18/362-ARM-dts-BCM5301X-EA6300-fix-USB3.patchedittarget/linux/bcm53xx/patches-6.18/310-ARM-BCM5301X-Add-DT-for-Netgear-R7900.patchaddtarget/linux/bcm53xx/patches-6.18/352-v7.2-ARM-dts-BCM5301X-EA9200-fix-nvram-size.patch
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c87fc39518a0ccc737de29a80ae70dd14a630ae751790322856000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: configure forced 1000BASE-X speed after disabling AN
RTL93xx ignores BMCR speed-selection updates while BMCR_ANENABLE is
set. The RTL931x mode setup therefore cannot reliably select 1000 Mbps
for forced 1000BASE-X before generic autonegotiation handling runs.
Move forced 1000BASE-X speed selection into the generic helper and
perform it after disabling autonegotiation. This also removes the
ineffective RTL931x-specific write.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:16 +020087fc39518a0ccc737de29a80ae70dd14a630ae75realtek: pcs: configure forced 1000BASE-X speed after disabling ANedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cd11e939d9f98641382e94d94eb96835c8854ba001790322857000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: configure BMCR for 100BASE-X
100BASE-X does not use in-band autonegotiation and requires BMCR to
select 100 Mbps. Extend the generic autonegotiation helper to always
disable AN for this mode and then program BMCR_SPEED100.
This ordering is required on RTL93xx, which ignores speed-selection
updates while BMCR_ANENABLE is set.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:17 +0200d11e939d9f98641382e94d94eb96835c8854ba00realtek: pcs: configure BMCR for 100BASE-Xedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c4c8e2912ec4d39c90aef540e6a3ea90bd9b33c481790322857000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: prepare generic helpers for 100BASE-X
100BASE-X uses a direct SerDes attachment and the same 1G-class PLL
configuration as 1000BASE-X on the supported hardware.
Teach the common attachment and PLL selectors about the mode. This is
preparation only; no additional SerDes advertises support yet.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:17 +02004c8e2912ec4d39c90aef540e6a3ea90bd9b33c48realtek: pcs: prepare generic helpers for 100BASE-Xedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cf019b2b5d59cdec4ae7abe3774f7ef82af788ed71790322857000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: rtl930x: prepare 100BASE-X support
RTL930x uses the IP-driven mode setup for Base-X links and the 1G
analog configuration for SGMII and 1000BASE-X.
Route 100BASE-X through the same IP-driven and 1G analog setup paths.
Keep the mode unavailable until all RTL93xx support is in place.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:17 +0200f019b2b5d59cdec4ae7abe3774f7ef82af788ed7realtek: pcs: rtl930x: prepare 100BASE-X supportedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c1a5e8733a01ac6d79c61463337a2d7e688cb77cf1790322858000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: rtl931x: prepare 100BASE-X support
RTL931x handles 100BASE-X through its 1G fiber digital path, but the
FIB1G link detector must remain disabled at 100 Mbps.
Add 100BASE-X to the fiber setup and symbol-error handling paths. Share
the 1000BASE-X setup while selecting the appropriate FIB1G link-enable
value for each mode. Keep the mode unavailable until the shared
RTL93xx support is enabled.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:18 +02001a5e8733a01ac6d79c61463337a2d7e688cb77cfrealtek: pcs: rtl931x: prepare 100BASE-X supportedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c446ca9fd630d54572f360ea42f852fe0ed66cf241790322858000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: rtl93xx: enable 100BASE-X support
The generic, RTL930x, and RTL931x setup paths now handle 100BASE-X.
Add the RTL93xx hardware mode value and mapping, select the 1G analog
CMU page, and advertise the mode from RTL93xx SerDes instances.
This makes the prepared support available to PCS consumers.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:18 +0200446ca9fd630d54572f360ea42f852fe0ed66cf24realtek: pcs: rtl93xx: enable 100BASE-X supportedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.c0f0d9c05b895daf8995e15997f7e5f802dd002271790322859000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: dsa: advertise 100BASE-X support
Phylink can only request interface modes advertised by the DSA port.
Expose 100BASE-X when the SoC MAC capabilities include MAC_100 so that
ports backed by a capable PCS can select the newly supported mode.
Keep this independent of MAC_1000FD because the 100 Mbps and 1 Gbps MAC
capabilities are reported separately.
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:19 +02000f0d9c05b895daf8995e15997f7e5f802dd00227realtek: dsa: advertise 100BASE-X supportedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.ca3676bf9ca89187fe192f5924a1c5e59a3f26c851790322859000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: pcs: configure autoneg before post_config
The post_config hooks finalize a powered-up SerDes and may calibrate
its receiver. Configure autonegotiation and the BMCR speed first so
finalization runs with the requested PCS state.
This is required for 100BASE-X on RTL930x. Calibrating with the default
1000 Mbps BMCR setting produced symbol errors until BMCR was switched
to 100 Mbps.
Preserve the changed result from set_autoneg across the post_config
callback so pcs_config keeps its existing return semantics.
Tested runtime mode transitions and cold boot on RTL838x, RTL930x and
RTL931x. Links came up and passed traffic in all tested modes with no
regressions observed.
Assisted-by: ChatGPT (OpenAI GPT-5.6 Sol)
Link: https://github.com/openwrt/openwrt/pull/25378
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 09:54:19 +0200a3676bf9ca89187fe192f5924a1c5e59a3f26c85realtek: pcs: configure autoneg before post_configedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- tools/mkimage/patches/030-allow-to-use-different-magic.patchf9a75af7436428a7316332037e178b43c2c0c4391790323504000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comtools/mkimage: support custom magic in dumpimage
OpenWrt's custom uImage magic patch makes legacy image verification use
params.magic instead of IH_MAGIC.
mkimage initializes this field, while dumpimage leaves it zeroed. This
causes dumpimage to reject valid legacy uImages using the standard
IH_MAGIC with FDT_ERR_BADMAGIC.
Initialize dumpimage's magic to IH_MAGIC so the normal verification path
works by default. Also add -M handling matching mkimage, allowing
dumpimage to verify and extract uImages built with a custom magic.
Tested with the patched U-Boot 2026.07 host tools. Standard-magic images
list and extract correctly, custom-magic images are accepted with the
matching -M value, and are rejected without it or with an incorrect
magic. Extracted payloads were verified byte-for-byte.
Fixes: #25287
Signed-off-by: Massimo Mazzariol <mazzariol.massimo@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25288
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-25 10:05:04 +0200f9a75af7436428a7316332037e178b43c2c0c439tools/mkimage: support custom magic in dumpimageedittools/mkimage/patches/030-allow-to-use-different-magic.patch
- tools/mkimage/patches/030-allow-to-use-different-magic.patch36efe835fdddaf61ae75e2d442af2abb02d45dd01790323504000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comtools/mkimage: validate custom magic range
strtoull() can parse values wider than the 32-bit uImage magic field.
Reject values above UINT32_MAX before assigning the parsed value to
params.magic.
Signed-off-by: Massimo Mazzariol <mazzariol.massimo@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25288
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-25 10:05:04 +020036efe835fdddaf61ae75e2d442af2abb02d45dd0tools/mkimage: validate custom magic rangeedittools/mkimage/patches/030-allow-to-use-different-magic.patch
- tools/mkimage/patches/030-allow-to-use-different-magic.patch6f684052de875c61db37682c306cf024ca164d4c1790323504000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comtools/mkimage: reject empty custom magic
Reject custom magic values when strtoull() does not parse any
digits, in addition to values outside the 32-bit uImage magic range.
Signed-off-by: Massimo Mazzariol <mazzariol.massimo@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25288
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-25 10:05:04 +02006f684052de875c61db37682c306cf024ca164d4ctools/mkimage: reject empty custom magicedittools/mkimage/patches/030-allow-to-use-different-magic.patch
- target/linux/mediatek/dts/thermal-trips-cooling-maps.dtsi5feb530ed37598eefb2384a2e22cff37855e5a9f1790323997000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: filogic: add dtsi for shared thermal trip levels & cooling maps
Add a common dtsi with macros for thermal trip levels and cooling maps that can be included in other
device trees.
The trip levels are spaced 1.25C apart with double that (2.5C) for the hysteresis, with 5C
hysteresis for the lowest trip level (65C) because it is preferable for the fan to run for longer at
low speed than to stop and start repeatedly.
In the absence of continuous proportional feedback control, tightly grouping the trip levels and
cooling maps minimises the frequency and amplitude of temperature and fan speed oscillations.
There are 36 trip levels and the cooling maps start from cooling state 1 (0-index) so cooling-levels
must have at least 37 elements. If greater increments between trip levels/cooling-levels are desired
or needed the cooling-levels can be padded with repeated values.
The THERMAL_TRIPS_COMMON and THERMAL_COOLING_MAPS_COMMON macros take one argument as the prefix to
the trip levels node labels. The prefix must be the same within a thermal zone.
Signed-off-by: Ryan Leung <untilscour@protonmail.com>
Link: https://github.com/openwrt/openwrt/pull/22936
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 10:13:17 +02005feb530ed37598eefb2384a2e22cff37855e5a9fmediatek: filogic: add dtsi for shared thermal trip levels & cooling mapsaddtarget/linux/mediatek/dts/thermal-trips-cooling-maps.dtsi
- target/linux/mediatek/dts/mt7981b-comfast-cf-wr632ax-common.dtsi8060e1d5683a82053bd096ec2788cdcb72c9d1511790323997000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: filogic: comfast cf-wr632ax: adjust fan behavior & monitor Wi-Fi temps
Add thermal zone for the Wi-Fi chip using the same trip levels and cooling maps as the CPU. The
kernel thermal governor will act on whichever temperature is the highest. There is only a single
heatsink and fan to cover both the SoC and Wi-Fi chip, so tracking both CPU and Wi-Fi temperatures
ensures that neither chip will overheat from low fan speed.
The trip levels are spaced 1.25C apart with double that (2.5C) for the hysteresis, with 5C
hysteresis for the lowest trip level (65C) because it is preferable for the fan to run for longer at
low speed than to stop and start repeatedly.
In the absence of continuous proportional feedback control, tightly grouping the trip levels and
cooling maps minimises the frequency and amplitude of temperature and fan speed oscillations.
The cooling states are set to increments of 5 (out of 255) from 12% to 61% and then increments of 10
from 61% to 100% with kick start speed at 15%. In comparison, the default in mt7981b.dtsi starts at
50% fan speed and leads to constant on/off cycles within a short period of time (every ~2 minutes).
Signed-off-by: Ryan Leung <untilscour@protonmail.com>
Link: https://github.com/openwrt/openwrt/pull/22936
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 10:13:17 +02008060e1d5683a82053bd096ec2788cdcb72c9d151mediatek: filogic: comfast cf-wr632ax: adjust fan behavior & monitor Wi-Fi tempsedittarget/linux/mediatek/dts/mt7981b-comfast-cf-wr632ax-common.dtsi
- target/linux/mediatek/dts/mt7981b-comfast-cf-wr632ax-common.dtsid733b2148c2a63ca7e5c36bb87ef1f2d38b010c61790323997000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: filogic: comfast cf-wr632ax: replace label with openwrt,netdev-name
Replace the label property for ethernet interface names with the property openwrt,netdev-name added
in commit d4d6c48b6e05 ("mediatek: filogic: support openwrt,netdev-name for renaming interfaces").
Signed-off-by: Ryan Leung <untilscour@protonmail.com>
Link: https://github.com/openwrt/openwrt/pull/22936
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-25 10:13:17 +0200d733b2148c2a63ca7e5c36bb87ef1f2d38b010c6mediatek: filogic: comfast cf-wr632ax: replace label with openwrt,netdev-nameedittarget/linux/mediatek/dts/mt7981b-comfast-cf-wr632ax-common.dtsi
- target/linux/qualcommax/patches-6.18/0723-clk-qcom-gcc-ipq5018-fix-uniphy-soft-reset-issue.patchtarget/linux/qualcommax/patches-6.18/0191-clk-qcom-ipq-cmn-pll-keep-the-CMN-block-bus-clocks-enabled.patchtarget/linux/qualcommax/patches-6.18/0721-clk-gcc-ipq5018-remove-the-unsupported-clk-combinati.patchtarget/linux/qualcommax/patches-6.18/0090-v7.4-clk-qcom-gcc-ipq5018-mark-gpll0_main-clock-as-critical.patchbbe5cbb665ec1db69e9171e35d4aaa6d3ac0f1461790327645000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: fix gpll0_main clock disable hang on ipq5018
Add upstream patch marking the 'gpll0_main' clock as critical on
IPQ5018 (gcc-ipq5018 driver), backported from upstream commit
33f9cb56cc28 ("clk: qcom: gcc-ipq5018: mark 'gpll0_main' clock as
critical").
During boot the APCS core clock feeding the CPUs can use GPLL0 as
its parent. On some boards (e.g. TP-Link Archer AX55 v1 using the
in-tree DTS since v6.18), the ipq-cmn-pll driver's pm_runtime_put()
call in its probe function asynchronously disables
'gcc_cmn_blk_ahb_clk', which in turn disables 'gpll0_main' as well,
hanging the system until the hardware watchdog restarts the board.
Marking gpll0_main as CLK_IS_CRITICAL fixes the underlying issue
directly in the GCC driver, making the previous workaround in
0191-clk-qcom-ipq-cmn-pll-keep-the-CMN-block-bus-clocks-enabled.patch
unnecessary. Drop that patch, as it addressed the same symptom by
keeping the CMN PLL block's bus clocks permanently enabled via a
devres-managed runtime PM reference instead of fixing the actual
critical clock.
Refresh the context in
0721-clk-gcc-ipq5018-remove-the-unsupported-clk-combinati.patch and
0723-clk-qcom-gcc-ipq5018-fix-uniphy-soft-reset-issue.patch, whose
hunks shifted by 9 lines due to the newly inserted patch.
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/25386
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-25 11:14:05 +0200bbe5cbb665ec1db69e9171e35d4aaa6d3ac0f146qualcommax: fix gpll0_main clock disable hang on ipq5018edittarget/linux/qualcommax/patches-6.18/0723-clk-qcom-gcc-ipq5018-fix-uniphy-soft-reset-issue.patchdeletetarget/linux/qualcommax/patches-6.18/0191-clk-qcom-ipq-cmn-pll-keep-the-CMN-block-bus-clocks-enabled.patchedittarget/linux/qualcommax/patches-6.18/0721-clk-gcc-ipq5018-remove-the-unsupported-clk-combinati.patchaddtarget/linux/qualcommax/patches-6.18/0090-v7.4-clk-qcom-gcc-ipq5018-mark-gpll0_main-clock-as-critical.patch
- target/linux/generic/pending-6.18/206-kbuild-map-the-kernel-tree-for-external-modules.patch50ec6f218ab9d2b507c0c74ed0e14535257dc7991790352203000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgkernel: map the kernel tree out of __FILE__ for external modules
Kernel modules from the packages feed differ between builds on 6.18,
e.g. kmod-v4l2loopback, kmod-jool-netfilter, kmod-pf-ring and
kmod-usb-serial-dmx_usb_module:
-/builder/shared-workdir/build/build_dir/.../linux-6.18.52/include/linux/ucopysize.h
+/tmp/rebuilderd-openwrt.Xebb8P/src/build_dir/.../linux-6.18.52/include/linux/ucopysize.h
These packages call make -C $(LINUX_DIR) M=... without
KERNEL_MAKE_FLAGS, so they get none of the OpenWrt prefix maps. With
6.12 that did not matter, since srctree stayed "." and the kernel
headers were included by a relative path. Since 6.13 srctree holds the
absolute path of the kernel tree for external modules, while kbuild
only maps srcroot, the module directory.
Add a pending patch that maps the kernel tree for external modules too.
It is added before the map of srcroot and before KCFLAGS, and GCC uses
the last matching map, so modules built through KERNEL_MAKE_FLAGS keep
their current output.
Link: https://github.com/openwrt/openwrt/pull/25356
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-25 18:03:23 +020050ec6f218ab9d2b507c0c74ed0e14535257dc799kernel: map the kernel tree out of __FILE__ for external modulesaddtarget/linux/generic/pending-6.18/206-kbuild-map-the-kernel-tree-for-external-modules.patch
- target/linux/qualcommbe/patches-6.18/0324-arm64-dts-qcom-ipq9574-add-PCS-uniphy-nodes.patchtarget/linux/qualcommbe/patches-6.18/0100-arm64-dts-qcom-ipq9574-add-reset-to-SDHC.patchtarget/linux/qualcommbe/patches-6.18/0344-arm64-dts-qcom-Add-EDMA-node-for-IPQ9574.patchtarget/linux/qualcommbe/patches-6.18/0353-arm64-dts-qcom-ipq9574-add-NSSNOC-clock-to-nss-node.patchtarget/linux/qualcommbe/patches-6.18/0346-arm64-dts-qcom-ipq9574-Use-usb-phy-for-node-names.patchtarget/linux/qualcommbe/patches-6.18/0356-arm64-dts-qcom-ipq9574-describe-remaining-uniphy-resets.patchtarget/linux/qualcommbe/patches-6.18/0355-arm64-dts-qcom-ipq9574-add-NSSNOC-interconnects-to-n.patchtarget/linux/qualcommbe/patches-6.18/0343-arm64-dts-qcom-Add-IPQ9574-PPE-base-device-node.patchda141cba5c52cc45d2b7413ad3ed7c587491141d1790364090000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommbe: ipq957x: add reset to SDHCI controller
Add a pending upstream patch[1] to add the reset to the SDHCI controller.
This allows it to reset itself on probe and avoids warnings due to leftover
bootloader configuration.
[1] https://patchwork.kernel.org/project/linux-arm-msm/patch/20260925191706.1579990-1-robert.marko@sartura.hr/
Signed-off-by: Robert Marko <robert.marko@sartura.hr>
2026-09-25 21:21:30 +0200da141cba5c52cc45d2b7413ad3ed7c587491141dqualcommbe: ipq957x: add reset to SDHCI controlleredittarget/linux/qualcommbe/patches-6.18/0353-arm64-dts-qcom-ipq9574-add-NSSNOC-clock-to-nss-node.patchedittarget/linux/qualcommbe/patches-6.18/0324-arm64-dts-qcom-ipq9574-add-PCS-uniphy-nodes.patchedittarget/linux/qualcommbe/patches-6.18/0355-arm64-dts-qcom-ipq9574-add-NSSNOC-interconnects-to-n.patchaddtarget/linux/qualcommbe/patches-6.18/0100-arm64-dts-qcom-ipq9574-add-reset-to-SDHC.patchedittarget/linux/qualcommbe/patches-6.18/0346-arm64-dts-qcom-ipq9574-Use-usb-phy-for-node-names.patchedittarget/linux/qualcommbe/patches-6.18/0344-arm64-dts-qcom-Add-EDMA-node-for-IPQ9574.patchedittarget/linux/qualcommbe/patches-6.18/0343-arm64-dts-qcom-Add-IPQ9574-PPE-base-device-node.patchedittarget/linux/qualcommbe/patches-6.18/0356-arm64-dts-qcom-ipq9574-describe-remaining-uniphy-resets.patch
- target/linux/qualcommbe/patches-6.18/0362-net-ethernet-qualcomm-ppe-fix-rx-dma-mapping-direction.patche8ca976eff4fe2ea9ac433ae615e4384b155b7831790365598000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommbe: fix PPE EDMA RX DMA mappings
EDMA maps RX fill buffers with DMA_TO_DEVICE but unmaps them with DMA_FROM_DEVICE. Use DMA_FROM_DEVICE consistently, release mappings left on RX rings during teardown, and flush ring-disable writes before descriptor cleanup.
Signed-off-by: krava <igor.kravchenko05@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24218
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-25 21:46:38 +0200e8ca976eff4fe2ea9ac433ae615e4384b155b783qualcommbe: fix PPE EDMA RX DMA mappingsaddtarget/linux/qualcommbe/patches-6.18/0362-net-ethernet-qualcomm-ppe-fix-rx-dma-mapping-direction.patch
- package/system/procd/Makefile3ab520425b127d66617bfeb1e2805b4f20109f951790380392000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orgprocd: jail/seccomp: complete the pre-main syscall allowlists
Add missing syscall names needed on 32-bit platforms to the pre-main
pre-main syscall allowlists.
Fixes: #25392
Fixes: ee526dbf01 ("procd: update to git HEAD of 2026-09-13")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2026-09-26 00:53:12 +01003ab520425b127d66617bfeb1e2805b4f20109f95procd: jail/seccomp: complete the pre-main syscall allowlistseditpackage/system/procd/Makefile
- package/system/mtd/src/trx.c83c18c360eaf0ba35c267536d4294195a13598ba1790450768000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.demtd: fix fd and mapping leak in trx_fixup() error path
When the TRX magic check fails, trx_fixup() jumps straight to the err
label, which only returns -1. At that point the mtd device has already
been opened and the whole partition has been mmap()ed, so both the file
descriptor and the mapping are leaked.
Add an err2 label that unwinds the mapping before falling through to the
existing close(bfd), so the error path unwinds in reverse order of
acquisition like the success path does.
Fixes: bbd9eb4669fa ("clean up mtd, fix up trx header when integrating jffs2 data on broadcom devices")
Assisted-by: Claude:claude-opus-5
Link: https://github.com/openwrt/openwrt/pull/25284
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 21:26:08 +020083c18c360eaf0ba35c267536d4294195a13598bamtd: fix fd and mapping leak in trx_fixup() error patheditpackage/system/mtd/src/trx.c
- package/system/mtd/src/trx.cpackage/system/mtd/Makefilee056c32ed0042b54d567059420454a4864b2222e1790450789000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.demtd: validate trx->len in trx_fixup()
trx_fixup() computed the CRC32 range from the on-flash TRX header
without validating it:
scan = ptr + offsetof(struct trx_header, flag_version);
trx->crc32 = crc32buf(scan, trx->len - (scan - ptr));
trx->len is read from the mmap()ed partition and is only sanity checked
in trx_check(), which is a separate entry point. A trx->len larger than
the partition therefore makes crc32buf() walk that many bytes past the
end of the mapping and crash mtd with SIGSEGV.
The mirror case of a trx->len below the 12 byte offset does not overread
in practice: crc32buf() takes a size_t but passes it to crc32(), which
takes an int len and loops on "while (--len >= 0)". The wrapped value
truncates to a negative int, so the loop body never runs and a zero
length CRC32 is written instead. Values at or above 0x8000000c truncate
the same way. Only the range from sizeof(struct trx_header) to roughly
0x8000000b stays positive through the truncation and reads out of
bounds, which is exactly the range a plausible bad length falls into.
Bound trx->len on both sides before computing the range, using the same
lower limit trx_check() already applies. Both comparisons are unsigned,
so the wrapping cases are rejected as well.
trx_fixup() runs as root on the contents of the flash, so this is a
robustness fix rather than a privilege boundary: it is reachable through
"mtd jffs2write" and the jffs2_replaced path of "mtd write", not through
"mtd fixtrx", which uses mtd_fixtrx() and derives its length from
erasesize instead. The practical benefit is not crashing on a truncated
or corrupted header during sysupgrade.
Link: https://github.com/openwrt/openwrt/security/advisories/GHSA-wch3-f5gc-mw2h
Reported-by: @tonoyx91
Reported-by: @0xROI
Fixes: bbd9eb4669fa ("clean up mtd, fix up trx header when integrating jffs2 data on broadcom devices")
Assisted-by: Claude:claude-opus-5
Link: https://github.com/openwrt/openwrt/pull/25284
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 21:26:29 +0200e056c32ed0042b54d567059420454a4864b2222emtd: validate trx->len in trx_fixup()editpackage/system/mtd/src/trx.ceditpackage/system/mtd/Makefile
- package/libs/libpcap/patches/100-no-openssl.patchpackage/libs/libpcap/patches/102-skip-manpages.patchpackage/libs/libpcap/Makefilepackage/libs/libpcap/patches/300-Add-support-for-B.A.T.M.A.N.-Advanced.patchb36d01c69682adf3eaf00f9e9414e99a6d0a0d411790452540000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.delibpcap: update to 1.10.7
Changelog: https://github.com/the-tcpdump-group/libpcap/blob/libpcap-1.10/CHANGES
CVE fixes:
- CVE-2026-0799: Access M[] safely in the BPF interpreter.
- CVE-2026-31912: Mind the program bounds in pcap_offline_filter().
- CVE-2026-31911: Fail opcodes safely in the BPF interpreter.
- CVE-2026-6244: Avoid division by zero via pcap_offline_filter().
- CVE-2026-6554: Limit "ja L" looping in pcap_offline_filter().
- CVE-2026-18313: Fix a memory leak in rpcapd.
- CVE-2026-18238: Fix RPCAP_MSG_PACKET validation.
Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25384
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 21:55:40 +0200b36d01c69682adf3eaf00f9e9414e99a6d0a0d41libpcap: update to 1.10.7editpackage/libs/libpcap/patches/102-skip-manpages.patcheditpackage/libs/libpcap/patches/100-no-openssl.patcheditpackage/libs/libpcap/Makefileeditpackage/libs/libpcap/patches/300-Add-support-for-B.A.T.M.A.N.-Advanced.patch
- package/network/utils/tcpdump/patches/001-remove_pcap_debug.patchpackage/network/utils/tcpdump/patches/100-tcpdump_mini.patchpackage/network/utils/tcpdump/Makefileb6bb254a85fe375cf923bc9da3eeceefd15268891790452684000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.detcpdump: update to 4.99.7
Changelog: https://github.com/the-tcpdump-group/tcpdump/blob/tcpdump-4.99/CHANGES
001-remove_pcap_debug.patch - rebased manually
Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25385
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 21:58:04 +0200b6bb254a85fe375cf923bc9da3eeceefd1526889tcpdump: update to 4.99.7editpackage/network/utils/tcpdump/patches/001-remove_pcap_debug.patcheditpackage/network/utils/tcpdump/Makefileeditpackage/network/utils/tcpdump/patches/100-tcpdump_mini.patch
- package/libs/elfutils/patches/003-libintl-compatibility.patchpackage/libs/elfutils/Makefileb3bd04ddb1dc6664ead64d72380f6a8b4f1c8db61790453552000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.deelfutils: update to 0.196
Release notes: https://inbox.sourceware.org/elfutils-devel/CAJDtP-QXj15OOpBxLdU+V1PZKM8YmnsE1eVy-R2R5xbE7Shk5A@mail.gmail.com/T/#u
Patches refreshed automatically.
Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25387
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 22:12:32 +0200b3bd04ddb1dc6664ead64d72380f6a8b4f1c8db6elfutils: update to 0.196editpackage/libs/elfutils/patches/003-libintl-compatibility.patcheditpackage/libs/elfutils/Makefile
- package/boot/uboot-mediatek/patches/459-add-mercusys-mr90x-v1.patch9fba5528d6c5a87440c42392f49f5a0b2abc34f11790453686000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.deuboot-mediatek: increase SPI-NAND frequency for Mercusys MR90X v1
Increase the spi-max-frequency from 20MHz to 52MHz for the SPI-NAND flash
on the Mercusys MR90X v1. The underlying GigaDevice GD5F1GQ5UEYIGY
SPI-NAND flash chip natively supports clock speeds up to 133MHz and the
MediaTek MT7986B SoC handles 52MHz safely.
Signed-off-by: Mikhail Zhilkin <csharper2005@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25246
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 22:14:46 +02009fba5528d6c5a87440c42392f49f5a0b2abc34f1uboot-mediatek: increase SPI-NAND frequency for Mercusys MR90X v1editpackage/boot/uboot-mediatek/patches/459-add-mercusys-mr90x-v1.patch
- target/linux/mediatek/dts/mt7986b-mercusys-mr90x-v1-common.dtsiea78c9d915efb066df3e2873edef0ae86946fd121790453686000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.demediatek: increase SPI-NAND frequency for Mercusys MR90X v1
Increase the spi-max-frequency from 20MHz to 52MHz for the SPI-NAND flash
on the Mercusys MR90X v1. The underlying GigaDevice GD5F1GQ5UEYIGY
SPI-NAND flash chip natively supports clock speeds up to 133MHz and the
MediaTek MT7986B SoC handles 52MHz safely.
Testing with 'dd' reading 16MB from /dev/mtd3 shows a significant
performance improvement (~49% reduction in read time):
Before (20MHz):
256+0 records in
256+0 records out
real 0m 2.71s
After (52MHz):
256+0 records in
256+0 records out
real 0m 1.37s
Signed-off-by: Mikhail Zhilkin <csharper2005@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25246
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-26 22:14:46 +0200ea78c9d915efb066df3e2873edef0ae86946fd12mediatek: increase SPI-NAND frequency for Mercusys MR90X v1edittarget/linux/mediatek/dts/mt7986b-mercusys-mr90x-v1-common.dtsi
- target/linux/bmips/bcm63268/config-6.12target/linux/bmips/bcm6362/config-6.18target/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchtarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchtarget/linux/bmips/patches-6.18/600-mips-bmips-add-pci-support.patchtarget/linux/bmips/bcm6362/config-6.12target/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patchtarget/linux/bmips/patches-6.18/502-net-mdio-mux-bcm6368-allow-disabling.patchtarget/linux/bmips/patches-6.18/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchtarget/linux/bmips/bcm63268/config-6.18target/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchtarget/linux/bmips/patches-6.18/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchtarget/linux/bmips/patches-6.18/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchtarget/linux/bmips/patches-6.18/501-net-broadcom-add-BCM6348-enet-controller-driver.patchtarget/linux/bmips/patches-6.18/201-mips-bmips-automatically-detect-RAM-size.patchtarget/linux/bmips/bcm6358/config-6.18target/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchtarget/linux/bmips/bcm6328/config-6.18target/linux/bmips/patches-6.18/200-mips-bmips-automatically-detect-CPU-frequency.patchtarget/linux/bmips/patches-6.18/100-irqchip-add-support-for-bcm6345-style-external-inter.patchtarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchtarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patchtarget/linux/bmips/bcm6318/config-6.18target/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchtarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchtarget/linux/bmips/patches-6.18/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchtarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patchtarget/linux/bmips/bcm6318/config-6.12target/linux/bmips/patches-6.18/601-pci-controllers-add-bcm6328-pcie-support.patchtarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchtarget/linux/bmips/bcm6358/config-6.12target/linux/bmips/bcm6328/config-6.12target/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchtarget/linux/bmips/patches-6.18/202-mips-bmips-tweak-Kconfig-options.patchtarget/linux/bmips/patches-6.18/603-pci-controllers-add-bcm6348-pci-support.patchtarget/linux/bmips/bcm6368/config-6.18target/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchtarget/linux/bmips/bcm6368/config-6.12target/linux/bmips/patches-6.18/602-pci-controllers-add-bcm6318-pcie-support.patchtarget/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patch5da13ae692fd9de648e0366671d67151335d90491790467286000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dekernel/bmips: create files for v6.18 (from v6.12)
This is an automatically generated commit.
When doing `git bisect`, consider `git bisect --skip`.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:26 +02005da13ae692fd9de648e0366671d67151335d9049kernel/bmips: create files for v6.18 (from v6.12)deletetarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchaddtarget/linux/bmips/bcm6328/config-6.18deletetarget/linux/bmips/bcm6368/config-6.12addtarget/linux/bmips/patches-6.18/100-irqchip-add-support-for-bcm6345-style-external-inter.patchaddtarget/linux/bmips/patches-6.18/202-mips-bmips-tweak-Kconfig-options.patchdeletetarget/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchdeletetarget/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchaddtarget/linux/bmips/patches-6.18/603-pci-controllers-add-bcm6348-pci-support.patchaddtarget/linux/bmips/patches-6.18/600-mips-bmips-add-pci-support.patchdeletetarget/linux/bmips/bcm6328/config-6.12addtarget/linux/bmips/patches-6.18/200-mips-bmips-automatically-detect-CPU-frequency.patchaddtarget/linux/bmips/bcm6318/config-6.18deletetarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchdeletetarget/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patchaddtarget/linux/bmips/patches-6.18/201-mips-bmips-automatically-detect-RAM-size.patchaddtarget/linux/bmips/patches-6.18/602-pci-controllers-add-bcm6318-pcie-support.patchdeletetarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchaddtarget/linux/bmips/patches-6.18/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchaddtarget/linux/bmips/patches-6.18/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchdeletetarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patchdeletetarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patchdeletetarget/linux/bmips/bcm63268/config-6.12deletetarget/linux/bmips/bcm6362/config-6.12deletetarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchdeletetarget/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchaddtarget/linux/bmips/bcm6362/config-6.18deletetarget/linux/bmips/bcm6358/config-6.12addtarget/linux/bmips/patches-6.18/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchdeletetarget/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchaddtarget/linux/bmips/bcm6358/config-6.18deletetarget/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patchdeletetarget/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchaddtarget/linux/bmips/patches-6.18/502-net-mdio-mux-bcm6368-allow-disabling.patchdeletetarget/linux/bmips/bcm6318/config-6.12addtarget/linux/bmips/patches-6.18/601-pci-controllers-add-bcm6328-pcie-support.patchaddtarget/linux/bmips/patches-6.18/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchdeletetarget/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchaddtarget/linux/bmips/patches-6.18/501-net-broadcom-add-BCM6348-enet-controller-driver.patchaddtarget/linux/bmips/bcm63268/config-6.18addtarget/linux/bmips/bcm6368/config-6.18
- target/linux/bmips/bcm63268/config-6.12target/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchtarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchtarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patchtarget/linux/bmips/bcm6318/config-6.12target/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchtarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchtarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchtarget/linux/bmips/bcm6362/config-6.12target/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patchtarget/linux/bmips/bcm6358/config-6.12target/linux/bmips/bcm6328/config-6.12target/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchtarget/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchtarget/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchtarget/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchtarget/linux/bmips/bcm6368/config-6.12target/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patchtarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchtarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patche829831c057b528040035743d457a86458937be31790467287000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dekernel/bmips: restore files for v6.12
This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.
For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:27 +0200e829831c057b528040035743d457a86458937be3kernel/bmips: restore files for v6.12addtarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchaddtarget/linux/bmips/bcm63268/config-6.12addtarget/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patchaddtarget/linux/bmips/bcm6368/config-6.12addtarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchaddtarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchaddtarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patchaddtarget/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchaddtarget/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchaddtarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patchaddtarget/linux/bmips/bcm6362/config-6.12addtarget/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchaddtarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchaddtarget/linux/bmips/bcm6318/config-6.12addtarget/linux/bmips/bcm6328/config-6.12addtarget/linux/bmips/bcm6358/config-6.12addtarget/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchaddtarget/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchaddtarget/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchaddtarget/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patch
- target/linux/bmips/Makefile97790a5ba0e643f60497603fef57652cabd8906a1790467287000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: enable 6.18 testing kernel
Enable the 6.18 testing kernel for bmips.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:27 +020097790a5ba0e643f60497603fef57652cabd8906abmips: enable 6.18 testing kerneledittarget/linux/bmips/Makefile
- target/linux/bmips/patches-6.18/202-mips-bmips-tweak-Kconfig-options.patchtarget/linux/bmips/patches-6.18/603-pci-controllers-add-bcm6348-pci-support.patchtarget/linux/bmips/patches-6.18/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchtarget/linux/bmips/patches-6.18/602-pci-controllers-add-bcm6318-pcie-support.patchtarget/linux/bmips/patches-6.18/100-irqchip-add-support-for-bcm6345-style-external-inter.patchtarget/linux/bmips/patches-6.18/601-pci-controllers-add-bcm6328-pcie-support.patchtarget/linux/bmips/patches-6.18/600-mips-bmips-add-pci-support.patchtarget/linux/bmips/patches-6.18/502-net-mdio-mux-bcm6368-allow-disabling.patch547f8a86bb7832922ad57e831874676ea7fbe6ea1790467287000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: refresh 6.18 patches
Refresh patches for 6.18.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:27 +0200547f8a86bb7832922ad57e831874676ea7fbe6eabmips: refresh 6.18 patchesedittarget/linux/bmips/patches-6.18/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchedittarget/linux/bmips/patches-6.18/202-mips-bmips-tweak-Kconfig-options.patchedittarget/linux/bmips/patches-6.18/603-pci-controllers-add-bcm6348-pci-support.patchedittarget/linux/bmips/patches-6.18/100-irqchip-add-support-for-bcm6345-style-external-inter.patchedittarget/linux/bmips/patches-6.18/600-mips-bmips-add-pci-support.patchedittarget/linux/bmips/patches-6.18/602-pci-controllers-add-bcm6318-pcie-support.patchedittarget/linux/bmips/patches-6.18/502-net-mdio-mux-bcm6368-allow-disabling.patchedittarget/linux/bmips/patches-6.18/601-pci-controllers-add-bcm6328-pcie-support.patch
- target/linux/bmips/bcm6358/config-6.18target/linux/bmips/bcm6368/config-6.18target/linux/bmips/bcm63268/config-6.18target/linux/bmips/bcm6362/config-6.18target/linux/bmips/bcm6318/config-6.18target/linux/bmips/bcm6328/config-6.18a1d76643c8a669fa0de5bedb656ecc67b744dd891790467288000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: refresh kernel config
Add missing symbols for bmips
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:28 +0200a1d76643c8a669fa0de5bedb656ecc67b744dd89bmips: refresh kernel configedittarget/linux/bmips/bcm6368/config-6.18edittarget/linux/bmips/bcm63268/config-6.18edittarget/linux/bmips/bcm6362/config-6.18edittarget/linux/bmips/bcm6318/config-6.18edittarget/linux/bmips/bcm6328/config-6.18edittarget/linux/bmips/bcm6358/config-6.18
- target/linux/bmips/files/drivers/pci/controller/pcie-bcm6318.ctarget/linux/bmips/files/drivers/pci/controller/pci-bcm6348.ctarget/linux/bmips/files/drivers/pci/controller/pcie-bcm6328.cd5472fb9abd68075bd5b57d9d41be41b2e81fb941790467288000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: add of_pci_parse_bus_range() version guard
Kernel 6.14 no longer exports of_pci_parse_bus_range(). Re-add a local
version to the bmips pci(e) drivers.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:28 +0200d5472fb9abd68075bd5b57d9d41be41b2e81fb94bmips: add of_pci_parse_bus_range() version guardedittarget/linux/bmips/files/drivers/pci/controller/pcie-bcm6318.cedittarget/linux/bmips/files/drivers/pci/controller/pci-bcm6348.cedittarget/linux/bmips/files/drivers/pci/controller/pcie-bcm6328.c
- target/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6348-enet.ctarget/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6368-enetsw.c7abedbd60268b92229c1f6be20800970a43d53561790467288000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: add enet timer guards and use modern timers
Guard from_timer() to kernels < 6.16 and migrate del_timer_sync to
timer_delete_sync() in favor of modern APIs.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:28 +02007abedbd60268b92229c1f6be20800970a43d5356bmips: add enet timer guards and use modern timersedittarget/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6368-enetsw.cedittarget/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6348-enet.c
- target/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6348-enet.c220866c5cf36269c3099b955d7b0de3d080bcade1790467289000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: fix iudma table match
Match the correct bcm6348_iudma_of_match table instead of
bcm6348_emac_of_match.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25293
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 02:01:29 +0200220866c5cf36269c3099b955d7b0de3d080bcadebmips: fix iudma table matchedittarget/linux/bmips/files/drivers/net/ethernet/broadcom/bcm6348-enet.c
- target/linux/ath79/image/generic.mk177bc19f275908572805e36d9e5debe8b32ef4711790496754000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgath79: make the ZyXEL NWA11xx factory tarball reproducible
The factory images of the ZyXEL NWA11xx devices differ between builds
in the tar.bz2 they wrap:
-drwxr-xr-x 0 buildbot (1000) buildbot (1000) 0 2026-09-24 21:39:18 ./
-rw-r--r-- 0 buildbot (1000) buildbot (1000) 3387 2026-09-24 21:39:18 ./vmlinux_mi124_f1e.lzma.uImage
-rw-r--r-- 0 buildbot (1000) buildbot (1000) 8388608 2026-09-24 21:39:18 ./mi124_f1e-jffs2
+drwxr-xr-x 0 rebuilder (1000) rebuilder (1000) 0 2026-09-25 01:03:01 ./
+-rw-r--r-- 0 rebuilder (1000) rebuilder (1000) 8388608 2026-09-25 01:03:01 ./mi124_f1e-jffs2
+-rw-r--r-- 0 rebuilder (1000) rebuilder (1000) 3387 2026-09-25 01:03:01 ./vmlinux_mi124_f1e.lzma.uImage
zyxel-tar-bz2 archives the staging directory as it is, so owner, mtime
and the order of the members come from the build host.
Store the members as root with the mtime set to SOURCE_DATE_EPOCH and
without group or other write permission. List them explicitly, kernel
first, which is the order of the images built so far, instead of
sorting them by name.
Link: https://github.com/openwrt/openwrt/pull/25389
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-27 10:12:34 +0200177bc19f275908572805e36d9e5debe8b32ef471ath79: make the ZyXEL NWA11xx factory tarball reproducibleedittarget/linux/ath79/image/generic.mk
- target/linux/apm821xx/image/Makefile4092869bc87d62c6f67236f59c13e3b9a255cdbe1790497092000https://taiha.net/jenkins/user/mailmailmail@aparcar.orgsata: make the boot partition reproducible
The ext2 boot partition of the WD My Book Live images differs between
builds:
-Linux rev 1.0 ext2 filesystem data, UUID=8474430c-7c37-4000-95a5-1d8f4f0607d1
+Linux rev 1.0 ext2 filesystem data, UUID=4b8e89bb-aee0-4fde-971c-893df8d8fcd1
-drwxr-xr-x 0 1000 1000 0 2026-09-23 08:27:40.000000 ./boot/
+drwxr-xr-x 0 1000 1000 0 2026-09-23 10:17:28.000000 ./boot/
genext2fs copies owner, mode and mtime of the staged files from the host
and adds them in readdir() order, which also decides their inode numbers
and blocks. It leaves the UUID empty, so e2fsck fills in a random one,
and e2fsck stamps the last check with the current time.
Pass genext2fs a name sorted tarball with root ownership, group and
other write permission dropped and mtimes clamped to SOURCE_DATE_EPOCH,
derive the UUID from the file system contents and run e2fsck with
E2FSCK_TIME set to SOURCE_DATE_EPOCH. Remove the staging directory and
the tarball afterwards.
Link: https://github.com/openwrt/openwrt/pull/25357
Signed-off-by: Paul Spooren <mail@aparcar.org>
2026-09-27 10:18:12 +02004092869bc87d62c6f67236f59c13e3b9a255cdbesata: make the boot partition reproducibleedittarget/linux/apm821xx/image/Makefile
- target/linux/bcm27xx/patches-6.18/0933-staging-vc04_services-vchiq-mmal-Bound-check-the-par.patchtarget/linux/bcm27xx/patches-6.18/0971-media-hevc_d-Do-not-reject-slice-header-with-bad-ref.patchtarget/linux/bcm27xx/patches-6.18/0937-media-hevc_d-Improve-checking-and-cleanup-of-decoder.patchtarget/linux/bcm27xx/patches-6.18/0958-usb-xhci-pci-Limit-VL805-DMA-address-to-40-bits.patchtarget/linux/bcm27xx/patches-6.18/0906-overlays-mcp2515-Cosmetic-tweaks.patchtarget/linux/bcm27xx/patches-6.18/0955-usb-storage-pick-better-defaults-for-max_sectors.patchtarget/linux/bcm27xx/patches-6.18/0542-usb-xhci-default-to-Intel-scheme-for-calculating-U1-.patchtarget/linux/bcm27xx/patches-6.18/0020-BCM2708-Add-core-Device-Tree-support.patchtarget/linux/bcm27xx/patches-6.18/0950-overlays-Add-gpclk-and-gpclk-pi5-overlays.patchtarget/linux/bcm27xx/patches-6.18/0655-DOWNSTREAM-drm-v3d-Delete-downstream-CLK-management.patchtarget/linux/bcm27xx/patches-6.18/0953-ARM-dts-overlays-waveshare-dsi-Add-auto_detect-panel.patchtarget/linux/bcm27xx/patches-6.18/0941-arm64-dts-broadcom-bcm2712-rpi.dtsi-add-light-DMAs.patchtarget/linux/bcm27xx/patches-6.18/0959-net-macb-Add-PHY-post-reset-settle-delay.patchtarget/linux/bcm27xx/patches-6.18/0970-media-rp1-cfe-Add-an-unbind-callback-to-tear-down-th.patchtarget/linux/bcm27xx/patches-6.18/0798-Revert-arm64-errata-Mitigate-TLBI-errata-on-various-.patchtarget/linux/bcm27xx/patches-6.18/0912-media-i2c-vd55g1-Add-support-for-vd65g4-RGB-variant.patchtarget/linux/bcm27xx/patches-6.18/0911-media-dt-bindings-vd55g1-Add-vd65g4-compatible.patchtarget/linux/bcm27xx/patches-6.18/0968-media-rp1-cfe-Release-the-vb2-queue-when-unregisteri.patchtarget/linux/bcm27xx/patches-6.18/0930-overlays-wm8960-soundcard-Add-media-parameter.patchtarget/linux/bcm27xx/patches-6.18/0922-dtoverlays-sdhost-Add-preserve_mmc-parameter.patchtarget/linux/bcm27xx/patches-6.18/0509-mmc-sd-filter-card-CQ-support-based-on-an-allow-list.patchtarget/linux/bcm27xx/patches-6.18/0913-media-i2c-vd55g1-Fix-media-bus-code-initialization.patchtarget/linux/bcm27xx/patches-6.18/0884-nvme-host-pci-Revert-to-upstream.patchtarget/linux/bcm27xx/patches-6.18/0905-dtoverlays-mcp2515-Add-spi6-support.patchtarget/linux/bcm27xx/patches-6.18/0926-gpiolib-Don-t-bypass-SRCU-when-CONFIG_LOCKDEP-is-ena.patchtarget/linux/bcm27xx/patches-6.18/0944-misc-rp1-pio-add-cyclic-DMA-support.patchtarget/linux/bcm27xx/patches-6.18/0936-bcm2835-i2s-fail-capture-open-cleanly-when-FIFO-clea.patchtarget/linux/bcm27xx/patches-6.18/0948-clk-Add-clk-hog-driver.patchtarget/linux/bcm27xx/patches-6.18/0969-media-rp1-cfe-Reset-the-video_device-before-re-regis.patchtarget/linux/bcm27xx/patches-6.18/0957-drm-vc4-hdmi-Only-offer-even-channel-counts.patchtarget/linux/bcm27xx/patches-6.18/0929-overlays-rt5616-Add-RT5616-audio-codec-overlay.patchtarget/linux/bcm27xx/patches-6.18/0905-Post-Merge-Fixup-up-to-825dba6c63eeb40a62699d1f8a4aa.patchtarget/linux/bcm27xx/patches-6.18/0940-dma-dw-axi-dmac-fix-cyclic-DMA.patchtarget/linux/bcm27xx/patches-6.18/0942-misc-rp1-pio-add-PIO_IOC_SM_CONFIG_XFER_V2.patchtarget/linux/bcm27xx/patches-6.18/0952-drm-panel-waveshare-Add-automatic-panel-detection-su.patchtarget/linux/bcm27xx/patches-6.18/0965-media-i2c-imx296-Add-strobe-outputs-controlled-by-mo.patchtarget/linux/bcm27xx/patches-6.18/0925-drm-vblank-do-not-halve-the-frame-duration-twice-for.patchtarget/linux/bcm27xx/patches-6.18/0923-dmaengine-dw-axi-dmac-Simplify-segmentation-calc-754.patchtarget/linux/bcm27xx/patches-6.18/0924-ASoC-dwc-Raise-sample-rate-limit-to-768kHz.patchtarget/linux/bcm27xx/patches-6.18/0918-media-i2c-vd55g1-Fix-wrong-output-FPS-value.patchtarget/linux/bcm27xx/patches-6.18/0915-media-i2c-vd55g1-Fix-manual-digital-gain-on-color-va.patchtarget/linux/bcm27xx/patches-6.18/0943-misc-rp1-pio-disable-SM-before-freeing-DMA.patchtarget/linux/bcm27xx/patches-6.18/0914-media-i2c-vd55g1-Remove-spurious-pad-format-update-o.patchtarget/linux/bcm27xx/patches-6.18/0951-usb-xhci-pci-Limit-VL805-DMA-address-to-37-bits.patchtarget/linux/bcm27xx/patches-6.18/0939-overlays-ed-backlight-pwm-Add-EDATEC-PWM-backlight-o.patchtarget/linux/bcm27xx/patches-6.18/0935-drm-vc4-hdmi-Don-t-write-past-the-end-of-a-packet-RA.patchtarget/linux/bcm27xx/patches-6.18/0954-DT-rp1-remove-dwc3-parkmode-disable-hs-quirk.patchtarget/linux/bcm27xx/patches-6.18/0346-serial-sc16is7xx-Don-t-spin-if-no-data-received.patchtarget/linux/generic/config-6.18target/linux/bcm27xx/patches-6.18/0956-ASoC-hdmi-codec-Always-allow-stereo-playback.patchtarget/linux/bcm27xx/patches-6.18/0947-overlays-Add-pwm-fan.patchtarget/linux/bcm27xx/patches-6.18/0927-media-bcm2835-unicam-Drop-setting-colorspace-when-in.patchtarget/linux/bcm27xx/patches-6.18/0916-media-dt-bindings-vd55g1-Add-vd55g4-compatible.patchtarget/linux/bcm27xx/patches-6.18/0934-staging-vc04_services-vc-sm-cma-Fix-fd-handling-when.patchtarget/linux/bcm27xx/patches-6.18/0917-media-i2c-vd55g1-Add-support-for-vd55g4.patchtarget/linux/bcm27xx/patches-6.18/0945-staging-vc04_services-fix-pointer-arithmetic-in-crea.patchbbab063e48bd0bafa2e732471c68dbf81cd36a0b1790497111000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debcm27xx: update patches up to Git HEAD as of 2026-09-17
These patches were generated from:
https://github.com/raspberrypi/linux/commits/rpi-6.18.y
Patches were generated from the diff between linux kernel branch linux-6.18.y
and rpi-6.18.y from raspberry pi kernel source:
git format-patch -N linux-6.18.y..rpi-6.18.y (HEAD)
(HEAD -> 4bb240615790ea5bd939484f4595b6952ac94ef4) as of 20260917
"Commit: media/hevc_d: Do not reject slice header with bad ref_idx entries"
Exceptions:
- github workflow patches
- applied and reverted patches
- README patches
- (def)configs
- patches merged upstream
Patches refreshed against current OpenWrt-kernel.
Previously, exporting patches from rpi-6.18.y via 'git format-patch' missed
content whenever the branch had merged commits from mainline, because
format-patch does not linearize merge history. The final patch in the series
(manual fixup-patch) restored that missing content (e.g.
mmc_card_working_sd_cq() in drivers/mmc/core/card.h) after each export.
This cycle, the patches touching the affected merge points were adjusted
around those points so that the full diff is captured directly by the
regular format-patch export - the content that the fixup-patch used to
reintroduce is now already present in the reworked series. A diff against
the upstream rpi-6.18.y tree confirms no delta remains, so the fixup is no
longer required and has been dropped.
Note: a normal 'quilt refresh' across the series still shifts hunk
offsets/context in unrelated patches as usual; that's expected housekeeping
and is unrelated to the merge-commit gap this fixup was compensating for.
Add the new CONFIG_CLK_HOG symbol, disabled by default, to
the generic config.
Fixes: https://github.com/openwrt/openwrt/issues/24951
Signed-off-by: Joshua Covington <joshuacov@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25243
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:18:31 +0200bbab063e48bd0bafa2e732471c68dbf81cd36a0bbcm27xx: update patches up to Git HEAD as of 2026-09-17addtarget/linux/bcm27xx/patches-6.18/0929-overlays-rt5616-Add-RT5616-audio-codec-overlay.patchaddtarget/linux/bcm27xx/patches-6.18/0948-clk-Add-clk-hog-driver.patchaddtarget/linux/bcm27xx/patches-6.18/0970-media-rp1-cfe-Add-an-unbind-callback-to-tear-down-th.patchaddtarget/linux/bcm27xx/patches-6.18/0906-overlays-mcp2515-Cosmetic-tweaks.patchaddtarget/linux/bcm27xx/patches-6.18/0933-staging-vc04_services-vchiq-mmal-Bound-check-the-par.patchaddtarget/linux/bcm27xx/patches-6.18/0945-staging-vc04_services-fix-pointer-arithmetic-in-crea.patchaddtarget/linux/bcm27xx/patches-6.18/0950-overlays-Add-gpclk-and-gpclk-pi5-overlays.patchaddtarget/linux/bcm27xx/patches-6.18/0965-media-i2c-imx296-Add-strobe-outputs-controlled-by-mo.patchaddtarget/linux/bcm27xx/patches-6.18/0951-usb-xhci-pci-Limit-VL805-DMA-address-to-37-bits.patchedittarget/linux/bcm27xx/patches-6.18/0542-usb-xhci-default-to-Intel-scheme-for-calculating-U1-.patchaddtarget/linux/bcm27xx/patches-6.18/0924-ASoC-dwc-Raise-sample-rate-limit-to-768kHz.patchaddtarget/linux/bcm27xx/patches-6.18/0915-media-i2c-vd55g1-Fix-manual-digital-gain-on-color-va.patchaddtarget/linux/bcm27xx/patches-6.18/0959-net-macb-Add-PHY-post-reset-settle-delay.patchedittarget/linux/bcm27xx/patches-6.18/0798-Revert-arm64-errata-Mitigate-TLBI-errata-on-various-.patchaddtarget/linux/bcm27xx/patches-6.18/0969-media-rp1-cfe-Reset-the-video_device-before-re-regis.patchaddtarget/linux/bcm27xx/patches-6.18/0952-drm-panel-waveshare-Add-automatic-panel-detection-su.patchedittarget/linux/bcm27xx/patches-6.18/0509-mmc-sd-filter-card-CQ-support-based-on-an-allow-list.patchdeletetarget/linux/bcm27xx/patches-6.18/0905-Post-Merge-Fixup-up-to-825dba6c63eeb40a62699d1f8a4aa.patchaddtarget/linux/bcm27xx/patches-6.18/0911-media-dt-bindings-vd55g1-Add-vd65g4-compatible.patchaddtarget/linux/bcm27xx/patches-6.18/0922-dtoverlays-sdhost-Add-preserve_mmc-parameter.patchaddtarget/linux/bcm27xx/patches-6.18/0918-media-i2c-vd55g1-Fix-wrong-output-FPS-value.patchaddtarget/linux/bcm27xx/patches-6.18/0947-overlays-Add-pwm-fan.patchaddtarget/linux/bcm27xx/patches-6.18/0916-media-dt-bindings-vd55g1-Add-vd55g4-compatible.patchaddtarget/linux/bcm27xx/patches-6.18/0955-usb-storage-pick-better-defaults-for-max_sectors.patchaddtarget/linux/bcm27xx/patches-6.18/0968-media-rp1-cfe-Release-the-vb2-queue-when-unregisteri.patchaddtarget/linux/bcm27xx/patches-6.18/0971-media-hevc_d-Do-not-reject-slice-header-with-bad-ref.patchaddtarget/linux/bcm27xx/patches-6.18/0913-media-i2c-vd55g1-Fix-media-bus-code-initialization.patchedittarget/linux/bcm27xx/patches-6.18/0884-nvme-host-pci-Revert-to-upstream.patchaddtarget/linux/bcm27xx/patches-6.18/0935-drm-vc4-hdmi-Don-t-write-past-the-end-of-a-packet-RA.patchedittarget/linux/bcm27xx/patches-6.18/0655-DOWNSTREAM-drm-v3d-Delete-downstream-CLK-management.patchaddtarget/linux/bcm27xx/patches-6.18/0943-misc-rp1-pio-disable-SM-before-freeing-DMA.patchaddtarget/linux/bcm27xx/patches-6.18/0914-media-i2c-vd55g1-Remove-spurious-pad-format-update-o.patchaddtarget/linux/bcm27xx/patches-6.18/0926-gpiolib-Don-t-bypass-SRCU-when-CONFIG_LOCKDEP-is-ena.patchaddtarget/linux/bcm27xx/patches-6.18/0927-media-bcm2835-unicam-Drop-setting-colorspace-when-in.patchaddtarget/linux/bcm27xx/patches-6.18/0912-media-i2c-vd55g1-Add-support-for-vd65g4-RGB-variant.patchaddtarget/linux/bcm27xx/patches-6.18/0936-bcm2835-i2s-fail-capture-open-cleanly-when-FIFO-clea.patchaddtarget/linux/bcm27xx/patches-6.18/0957-drm-vc4-hdmi-Only-offer-even-channel-counts.patchaddtarget/linux/bcm27xx/patches-6.18/0944-misc-rp1-pio-add-cyclic-DMA-support.patchaddtarget/linux/bcm27xx/patches-6.18/0953-ARM-dts-overlays-waveshare-dsi-Add-auto_detect-panel.patchaddtarget/linux/bcm27xx/patches-6.18/0905-dtoverlays-mcp2515-Add-spi6-support.patchaddtarget/linux/bcm27xx/patches-6.18/0941-arm64-dts-broadcom-bcm2712-rpi.dtsi-add-light-DMAs.patchaddtarget/linux/bcm27xx/patches-6.18/0930-overlays-wm8960-soundcard-Add-media-parameter.patchaddtarget/linux/bcm27xx/patches-6.18/0937-media-hevc_d-Improve-checking-and-cleanup-of-decoder.patchaddtarget/linux/bcm27xx/patches-6.18/0925-drm-vblank-do-not-halve-the-frame-duration-twice-for.patchaddtarget/linux/bcm27xx/patches-6.18/0954-DT-rp1-remove-dwc3-parkmode-disable-hs-quirk.patchaddtarget/linux/bcm27xx/patches-6.18/0934-staging-vc04_services-vc-sm-cma-Fix-fd-handling-when.patchaddtarget/linux/bcm27xx/patches-6.18/0917-media-i2c-vd55g1-Add-support-for-vd55g4.patchaddtarget/linux/bcm27xx/patches-6.18/0958-usb-xhci-pci-Limit-VL805-DMA-address-to-40-bits.patchedittarget/linux/bcm27xx/patches-6.18/0346-serial-sc16is7xx-Don-t-spin-if-no-data-received.patchedittarget/linux/generic/config-6.18edittarget/linux/bcm27xx/patches-6.18/0020-BCM2708-Add-core-Device-Tree-support.patchaddtarget/linux/bcm27xx/patches-6.18/0923-dmaengine-dw-axi-dmac-Simplify-segmentation-calc-754.patchaddtarget/linux/bcm27xx/patches-6.18/0939-overlays-ed-backlight-pwm-Add-EDATEC-PWM-backlight-o.patchaddtarget/linux/bcm27xx/patches-6.18/0942-misc-rp1-pio-add-PIO_IOC_SM_CONFIG_XFER_V2.patchaddtarget/linux/bcm27xx/patches-6.18/0940-dma-dw-axi-dmac-fix-cyclic-DMA.patchaddtarget/linux/bcm27xx/patches-6.18/0956-ASoC-hdmi-codec-Always-allow-stereo-playback.patch
- target/linux/bcm27xx/modules/other.mk3f50262abc28df67540b3c17ecea49d74f3b0d6f1790497111000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debcm27xx: add kmod-clk-hog package
Package CONFIG_CLK_HOG as kmod-clk-hog. The gpclk and gpclk-pi5
overlays rely on this driver to keep a GPCLK output enabled with no
other consumer, so it needs to be selectable for those overlays to
actually work. Not selected by default; built only for images that
ask for it, or under CONFIG_ALL_KMODS.
Signed-off-by: Joshua Covington <joshuacov@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25243
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:18:31 +02003f50262abc28df67540b3c17ecea49d74f3b0d6fbcm27xx: add kmod-clk-hog packageedittarget/linux/bcm27xx/modules/other.mk
- package/utils/bcm27xx-utils/patches/1002-piolib-make-piolib-a-shared-library.patchpackage/utils/bcm27xx-utils/patches/1001-rpifwcrypto-switch-from-GnuTLS-to-OpenSSL.patchpackage/utils/bcm27xx-utils/Makefilepackage/utils/bcm27xx-utils/patches/1003-cmake-disable-splashasm.patchpackage/utils/bcm27xx-utils/patches/0001-raspinfo-adapt-to-OpenWrt.patchafe0f08a6fc85d7c824691a9e6c432cb8ae2bca91790497112000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debcm27xx-utils: update to Git HEAD as of 2026.09.17
Update to Git HEAD as of 2026-09-17
Update patches:
- 0001-raspinfo-adapt-to-OpenWrt.patch: rebase, note vclog alongside
vcdbg when neither is found
- 1001-rpifwcrypto-switch-from-GnuTLS-to-OpenSSL.patch: add proper
commit message; update documentation where needed; fix hash_file()
to bound the memcpy by the actual digest length instead of always
copying SHA256_HASH_SIZE bytes
- 1002-piolib-make-piolib-a-shared-library.patch: add proper commit
message and update documentation where needed
- Add 1003-cmake-disable-splashasm.patch: splashasm is not needed
for the OpenWrt build at this time
Fixes: a296a5adf7a3 ("bcm27xx-utils: update to 20260621, add rpi-fw-crypto and piolib")
Signed-off-by: Joshua Covington <joshuacov@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25243
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:18:32 +0200afe0f08a6fc85d7c824691a9e6c432cb8ae2bca9bcm27xx-utils: update to Git HEAD as of 2026.09.17editpackage/utils/bcm27xx-utils/patches/1001-rpifwcrypto-switch-from-GnuTLS-to-OpenSSL.patcheditpackage/utils/bcm27xx-utils/patches/1002-piolib-make-piolib-a-shared-library.patchaddpackage/utils/bcm27xx-utils/patches/1003-cmake-disable-splashasm.patcheditpackage/utils/bcm27xx-utils/Makefileeditpackage/utils/bcm27xx-utils/patches/0001-raspinfo-adapt-to-OpenWrt.patch
- package/kernel/bcm27xx-gpu-fw/Makefile74d6a3a0a40ad5ecc6739eb9149d11fe62b463f01790497112000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debcm27xx-gpu-fw: update to 2026.09.15
Update to 2026-09-15
Signed-off-by: Joshua Covington <joshuacov@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25243
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:18:32 +020074d6a3a0a40ad5ecc6739eb9149d11fe62b463f0bcm27xx-gpu-fw: update to 2026.09.15editpackage/kernel/bcm27xx-gpu-fw/Makefile
- target/linux/bmips/bcm63268/config-6.12target/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchtarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchtarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patchtarget/linux/bmips/bcm6318/config-6.12target/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchtarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchtarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchtarget/linux/bmips/bcm6362/config-6.12target/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patchtarget/linux/bmips/bcm6358/config-6.12target/linux/bmips/bcm6328/config-6.12target/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchtarget/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchtarget/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchtarget/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchtarget/linux/bmips/bcm6368/config-6.12target/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patchtarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchtarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patchtarget/linux/bmips/Makefilec54aabf4efa4d1b1db65870cfae618d812e53e531790497373000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.debmips: drop v6.12 and default to 6.18
Switch the bmips target to kernel v6.18 and drop v6.12.
Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/25423
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:22:53 +0200c54aabf4efa4d1b1db65870cfae618d812e53e53bmips: drop v6.12 and default to 6.18deletetarget/linux/bmips/bcm6328/config-6.12deletetarget/linux/bmips/patches-6.12/201-mips-bmips-automatically-detect-RAM-size.patchdeletetarget/linux/bmips/bcm63268/config-6.12deletetarget/linux/bmips/patches-6.12/800-jffs2-work-around-unaligned-accesses-failing-on-bcm6.patchdeletetarget/linux/bmips/bcm6318/config-6.12deletetarget/linux/bmips/bcm6358/config-6.12deletetarget/linux/bmips/patches-6.12/200-mips-bmips-automatically-detect-CPU-frequency.patchdeletetarget/linux/bmips/patches-6.12/501-net-broadcom-add-BCM6348-enet-controller-driver.patchdeletetarget/linux/bmips/patches-6.12/202-mips-bmips-tweak-Kconfig-options.patchdeletetarget/linux/bmips/patches-6.12/603-pci-controllers-add-bcm6348-pci-support.patchdeletetarget/linux/bmips/patches-6.12/601-pci-controllers-add-bcm6328-pcie-support.patchdeletetarget/linux/bmips/patches-6.12/110-net-dsa-b53-bcm531x5-fix-cpu-rgmii-mode-interpretation.patchdeletetarget/linux/bmips/patches-6.12/600-mips-bmips-add-pci-support.patchdeletetarget/linux/bmips/bcm6368/config-6.12deletetarget/linux/bmips/bcm6362/config-6.12deletetarget/linux/bmips/patches-6.12/500-net-broadcom-add-BCM6368-enetsw-controller-driver.patchedittarget/linux/bmips/Makefiledeletetarget/linux/bmips/patches-6.12/100-irqchip-add-support-for-bcm6345-style-external-inter.patchdeletetarget/linux/bmips/patches-6.12/700-leds-add-support-for-Sercomm-MSP430-LED-controller.patchdeletetarget/linux/bmips/patches-6.12/502-net-mdio-mux-bcm6368-allow-disabling.patchdeletetarget/linux/bmips/patches-6.12/602-pci-controllers-add-bcm6318-pcie-support.patch
- target/linux/qualcommax/dts/ipq5018-archer-ax55-v1.dts836734f67477b7ef26ad935db70a439fbfdf39b01790497916000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ax55-v1: use hex for switch address
Change the Realtek switch MDIO node unit address and reg property from
decimal (29) to hexadecimal (0x1d) to comply with standard Device Tree
coding conventions. This is a cosmetic fix and does not change the actual
hardware address.
Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Link: https://github.com/openwrt/openwrt/pull/25382
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:31:56 +0200836734f67477b7ef26ad935db70a439fbfdf39b0qualcommax: ax55-v1: use hex for switch addressedittarget/linux/qualcommax/dts/ipq5018-archer-ax55-v1.dts
- package/boot/arm-trusted-firmware-mediatek/Makefilepackage/boot/arm-trusted-firmware-mediatek/patches/0008-mediatek-spi-nand-add-DS35Q1GB-flash.patch10030f85ff9d903dd236825ad90505ddf17890141790497932000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dearm-trusted-firmware-mediatek: add DS35Q1GB flash
The DS35Q1GB is similar to the MX35LF1GE4AB, has issues accessing
the parameter page. The DS35Q1GA does not have this issue. So add
SPI-NAND ID for DS35Q1GB as a workaround.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:12 +020010030f85ff9d903dd236825ad90505ddf1789014arm-trusted-firmware-mediatek: add DS35Q1GB flashaddpackage/boot/arm-trusted-firmware-mediatek/patches/0008-mediatek-spi-nand-add-DS35Q1GB-flash.patcheditpackage/boot/arm-trusted-firmware-mediatek/Makefile
- package/boot/uboot-mediatek/patches/115-mtd-spinand-add-support-for-Dosilicon-DS35Q1GA.patchpackage/boot/uboot-mediatek/patches/116-mtd-spinand-dosilicon-support-new-devices.patch619fc0813de941ce36fb19d83cae7ab6e1246fce1790497932000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deuboot-mediatek: add Dosilicon spi-nand flash
Port the Dosilicon SPI-NAND flash driver from the kernel to U-Boot.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:12 +0200619fc0813de941ce36fb19d83cae7ab6e1246fceuboot-mediatek: add Dosilicon spi-nand flashaddpackage/boot/uboot-mediatek/patches/115-mtd-spinand-add-support-for-Dosilicon-DS35Q1GA.patchaddpackage/boot/uboot-mediatek/patches/116-mtd-spinand-dosilicon-support-new-devices.patch
- package/boot/uboot-tools/uboot-envtools/files/mediatek_filogicpackage/boot/uboot-mediatek/patches/480-add-tplink-7dr72xx.patchpackage/boot/uboot-mediatek/Makefiledff4a9d049b32e6c37c793131b1bf7259a85fcc71790497932000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deuboot-mediatek: add TP-Link TL-7DR7230/7250
Add custom U-Boot build for the following device:
- TP-Link TL-7DR7230 v1
- TP-Link TL-7DR7230 v2
- TP-Link TL-7DR7250 v1
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:12 +0200dff4a9d049b32e6c37c793131b1bf7259a85fcc7uboot-mediatek: add TP-Link TL-7DR7230/7250editpackage/boot/uboot-mediatek/Makefileeditpackage/boot/uboot-tools/uboot-envtools/files/mediatek_filogicaddpackage/boot/uboot-mediatek/patches/480-add-tplink-7dr72xx.patch
- target/linux/mediatek/patches-6.18/412-mtd-spinand-dosilicon-support-new-devices.patch4dd69c754fededacaa4eb42deff107991a91fbce1790497933000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: add Dosilicon DS35Q1GB-IB support
Add the DS35Q1GB flash driver from the Rockchip kernel.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:13 +02004dd69c754fededacaa4eb42deff107991a91fbcemediatek: add Dosilicon DS35Q1GB-IB supportaddtarget/linux/mediatek/patches-6.18/412-mtd-spinand-dosilicon-support-new-devices.patch
- target/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230.dtsitarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230-v1.dtstarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr72xx.dtsitarget/linux/mediatek/image/filogic.mktarget/linux/mediatek/dts/mt7988-tplink-tl-common.dtsitarget/linux/mediatek/filogic/base-files/lib/upgrade/platform.shtarget/linux/mediatek/filogic/base-files/etc/board.d/02_networkaf8ba9b4263d330ac830cdac7334323a2c8d284a1790497933000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: add TP-Link TL-7DR7230 v1 support
Hardware specification:
SoC: MediaTek MT7988D 3x A73
Flash: ESMT F50L1G41LB 128MB
RAM: GDQ2BFAA-CJ DDR4 512MB
Ethernet: 1x 2.5G Wan, 4x 1G Lan
WiFi1: MT7975N 2.4GHz 4T4R
WiFi2: MT7979N 5GHz 4T5R
Button: Reset, WPS
Power: DC 12V 2A
MAC addresses map:
LAN 4C:xx:xx:xx:xx:A7
WAN 4C:xx:xx:xx:xx:A8
2G 4C:xx:xx:xx:xx:A7
5G 4C:xx:xx:xx:xx:A9
Flash instructions:
1. Update 7dr7230mv1-middleware.bin in vendor uboot
2. Update factory.bin in the middleware firmware
3. After openwrt boots up, install kmod-mtd-rw and
execute: insmod mtd-rw i_want_a_brick=1
4. Replace the stock bootloader to OpenWrt's:
mtd write openwrt-mediatek-filogic-tplink_tl-7dr7230-v1-preloader.bin bl2
mtd write openwrt-mediatek-filogic-tplink_tl-7dr7230-v1-bl31-uboot.fip fip
5. Run the following command to remove the OEM UBI volume:
ubirmvol /dev/ubi0 -N kernel
ubirmvol /dev/ubi0 -N rootfs
ubimkvol /dev/ubi0 -N ubootenv -s 1MiB
ubimkvol /dev/ubi0 -N ubootenv2 -s 1MiB
6. Upload sysupgrade.bin to perform the upgrade.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:13 +0200af8ba9b4263d330ac830cdac7334323a2c8d284amediatek: add TP-Link TL-7DR7230 v1 supportaddtarget/linux/mediatek/dts/mt7988-tplink-tl-common.dtsiedittarget/linux/mediatek/filogic/base-files/etc/board.d/02_networkaddtarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr72xx.dtsiedittarget/linux/mediatek/filogic/base-files/lib/upgrade/platform.shaddtarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230-v1.dtsedittarget/linux/mediatek/image/filogic.mkaddtarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230.dtsi
- target/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230-v2.dtstarget/linux/mediatek/image/filogic.mk820662d91773953947eac2bda34830272a015aff1790497933000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: add TP-Link TL-7DR7230 v2 support
Hardware specification:
SoC: MediaTek MT7988D 3x A73
Flash: Dosilicon DS35Q1GB-IB 128MB
RAM: Zentel A3T4GF40BBF DDR3 512MB
Ethernet: 1x 2.5G Wan, 4x 1G Lan
WiFi1: MT7975N 2.4GHz 4T4R
WiFi2: MT7979N 5GHz 4T5R
Button: Reset, WPS
Power: DC 12V 2A
MAC addresses map:
LAN 80:xx:xx:xx:19:FE
WAN 80:xx:xx:xx:19:FF
2G 80:xx:xx:xx:19:FE
5G 80:xx:xx:xx:1A:00
Flash instructions:
1. Connect to your PC via the Gigabit port of the router,
set a static ip on the ethernet interface of your PC.
(ip 192.168.1.254, gateway 192.168.1.1)
2. Execute the following operation to open nc shell:
https://forum.openwrt.org/t/tp-link-china-routers-rce-vuln
3. Download the preloader.bin and uboot.fip, host them with
the HTTP server: python3 -m http.server
4. Replace the stock bootloader to OpenWrt's:
ln -sf opt/game_acc/rootfs/bin/busybox wget && cd tmp
/wget http://192.168.1.254:8000/openwrt-mediatek-filogic-tplink_tl-7dr7230-v2-preloader.bin
/wget http://192.168.1.254:8000/openwrt-mediatek-filogic-tplink_tl-7dr7230-v2-bl31-uboot.fip
dd bs=131072 conv=sync of=/dev/mtdblock15 if=openwrt-mediatek-filogic-tplink_tl-7dr7230-v2-preloader.bin
dd bs=131072 conv=sync of=/dev/mtdblock15 seek=44 if=openwrt-mediatek-filogic-tplink_tl-7dr7230-v2-bl31-uboot.fip
5. Download the initramfs image, host it with the tftp server,
and restart the router, waiting for tftp recovery to complete.
6. After openwrt boots up, upload sysupgrade.bin to upgrade.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:13 +0200820662d91773953947eac2bda34830272a015affmediatek: add TP-Link TL-7DR7230 v2 supportaddtarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr7230-v2.dtsedittarget/linux/mediatek/image/filogic.mk
- target/linux/mediatek/dts/mt7988d-tplink-tl-7dr7250-v1.dtstarget/linux/mediatek/image/filogic.mktarget/linux/mediatek/filogic/base-files/lib/upgrade/platform.shtarget/linux/mediatek/filogic/base-files/etc/board.d/02_network7e2bacd43fbe9cf8833be02e1ec3ae3fc4cb63521790497934000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: add TP-Link TL-7DR7250 v1 support
Hardware specification:
SoC: MediaTek MT7988D 3x A73
Flash: ESMT F50L1G41LB 128MB
RAM: NT5AD256M16E4 DDR4 512MB
Ethernet: 2x 2.5G + 2x 1G Lan
WiFi1: MT7975N 2.4GHz 4T4R
WiFi2: MT7979N 5GHz 4T5R
Button: Reset, WPS
Power: DC 12V 2A
MAC addresses map:
LAN 4C:xx:xx:xx:xx:57
WAN 4C:xx:xx:xx:xx:58
2G 4C:xx:xx:xx:xx:57
5G 4C:xx:xx:xx:xx:59
Flash instructions:
1. Connect to your PC via the Gigabit port of the router,
set a static ip on the ethernet interface of your PC.
(ip 192.168.1.254, gateway 192.168.1.1)
2. Execute the following operation to open nc shell:
https://forum.openwrt.org/t/tp-link-china-routers-rce-vuln
3. Download the preloader.bin and uboot.fip, host them with
the HTTP server: python3 -m http.server
4. Replace the stock bootloader to OpenWrt's:
ln -sf opt/game_acc/rootfs/bin/busybox wget && cd tmp
/wget http://192.168.1.254:8000/openwrt-mediatek-filogic-tplink_tl-7dr7250-v1-preloader.bin
/wget http://192.168.1.254:8000/openwrt-mediatek-filogic-tplink_tl-7dr7250-v1-bl31-uboot.fip
dd bs=131072 conv=sync of=/dev/mtdblock15 if=openwrt-mediatek-filogic-tplink_tl-7dr7250-v1-preloader.bin
dd bs=131072 conv=sync of=/dev/mtdblock15 seek=44 if=openwrt-mediatek-filogic-tplink_tl-7dr7250-v1-bl31-uboot.fip
5. Download the initramfs image, host it with the tftp server,
and restart the router, waiting for tftp recovery to complete.
6. After openwrt boots up, upload sysupgrade.bin to upgrade.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Link: https://github.com/openwrt/openwrt/pull/24200
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 10:32:14 +02007e2bacd43fbe9cf8833be02e1ec3ae3fc4cb6352mediatek: add TP-Link TL-7DR7250 v1 supportedittarget/linux/mediatek/image/filogic.mkedittarget/linux/mediatek/filogic/base-files/lib/upgrade/platform.shaddtarget/linux/mediatek/dts/mt7988d-tplink-tl-7dr7250-v1.dtsedittarget/linux/mediatek/filogic/base-files/etc/board.d/02_network
- target/linux/qualcommax/dts/ipq5018-ax6000.dts88d3c30f182601f9e63f59fe4888c2576928d7df1790498001000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq5018-ax6000: set explicit NAND ECC strength/step-size
Some Xiaomi AX6000 (RA72) units use SPI-NAND with page size 2048 and
OOB size 128, requiring ECC strength 8 with step size 512 (matching
stock firmware). Without explicit ECC settings, the kernel defaults
to strength 4, causing UBI ECC errors and a boot loop after
sysupgrade to squashfs on affected units.
Signed-off-by: Sergey Dubow <killerpelmeney@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24959
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:33:21 +020088d3c30f182601f9e63f59fe4888c2576928d7dfqualcommax: ipq5018-ax6000: set explicit NAND ECC strength/step-sizeedittarget/linux/qualcommax/dts/ipq5018-ax6000.dts
- target/linux/qualcommax/dts/ipq5018-wrc-x3000gs2.dtstarget/linux/qualcommax/dts/ipq5018-wrc-x3000gst2.dtstarget/linux/qualcommax/dts/ipq5018-wrc-x3000.dtsie5c3f4569de572e7fee27158a19c3d33014012a41790498058000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: create a shared dtsi for ELECOM WRC-X3000GS(T)2
Create a shared dtsi for ELECOM WRC-X3000GS2 and WRC-X3000GST2.
They have the almost identical hardware, except for memory (256M vs.
512M).
Additionally, disable "q6_region" in reserved-memory of WRC-X3000GS2.
This was disabled before, but accidentally activated by 1f879b88398b
("qualcommax: ipq50xx: split firmware variants and refactor QCN6122
support").
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24937
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:34:18 +0200e5c3f4569de572e7fee27158a19c3d33014012a4qualcommax: create a shared dtsi for ELECOM WRC-X3000GS(T)2addtarget/linux/qualcommax/dts/ipq5018-wrc-x3000.dtsiedittarget/linux/qualcommax/dts/ipq5018-wrc-x3000gs2.dtsedittarget/linux/qualcommax/dts/ipq5018-wrc-x3000gst2.dts
- target/linux/generic/backport-6.18/438-v7.3-mtd-spinand-Do-not-update-the-QE-bit-on-devices-without-one.patchd42c59d039555f6d68e68dc3ff6731d9650603e81790498143000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comgeneric: 6.18: backport SPI-NAND QE bit fix
Backport upstream commit 1c1a342aceec ("mtd: spinand: Do not update
the QE bit on devices without one") to OpenWrt's Linux 6.18 series.
On the Winbond W25N02KV, configuration register bit 0 is H-DIS, not
a QE bit. Clearing it can enable HOLD and cause flash commands to stall.
On the JioRouter JIDU6401, this caused sysupgrade failures and a
subsequent warm reboot hang in BL2.
Upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/commit/?id=1c1a342aceec79528b3ba51f376eca2be5928fe7
Validation:
- Patch prepared and refreshed against OpenWrt Linux 6.18.52.
- `target/linux/compile` passed for mediatek/filogic.
- The upstream patch reports successful sysupgrade and warm reboot on
JioRouter JIDU6401 with W25N02KV.
Signed-off-by: Sagnik Sasmal <sagnik@sagnik.me>
Link: https://github.com/openwrt/openwrt/pull/25428
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:35:43 +0200d42c59d039555f6d68e68dc3ff6731d9650603e8generic: 6.18: backport SPI-NAND QE bit fixaddtarget/linux/generic/backport-6.18/438-v7.3-mtd-spinand-Do-not-update-the-QE-bit-on-devices-without-one.patch
- package/firmware/ipq-wifi/Makefileca3701cb149c261a56cbcbba1fd81b02cc6bba1d1790498626000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comipq-wifi: update to Git HEAD (2026-09-27)
3d9c15abc376 ipq5018: add TP-Link EAP650-Outdoor-v1
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:43:46 +0200ca3701cb149c261a56cbcbba1fd81b02cc6bba1dipq-wifi: update to Git HEAD (2026-09-27)editpackage/firmware/ipq-wifi/Makefile
- target/linux/qualcommax/ipq50xx/base-files/etc/hotplug.d/firmware/11-ath11k-caldatatarget/linux/qualcommax/ipq50xx/base-files/etc/board.d/02_networktarget/linux/qualcommax/ipq50xx/base-files/lib/preinit/09_mount_factory_datatarget/linux/qualcommax/ipq50xx/base-files/lib/upgrade/platform.shpackage/firmware/ipq-wifi/Makefiletarget/linux/qualcommax/dts/ipq5018-eap650-outdoor-v1.dtstarget/linux/qualcommax/image/ipq50xx.mkpackage/boot/uboot-tools/uboot-envtools/files/qualcommax_ipq50xxc4543e374d291b3d2c711ae02e5dbe8e168e18251790498648000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq50xx: add support for TP-Link EAP650-Outdoor-v1
TP-Link EAP650-Outdoor is a 802.11ax AP claiming AX3000 support. It is
wall or pole mountable, and rated for outdoor use. It can only be
powered via PoE.
Specifications:
---------------
* CPU: Qualcomm IPQ5018 Dual core Cortex-A53
* RAM: 512 MB
* Storage: 128MB NAND GigaDevice F50D1G41LB-83YIG2M
* Ethernet: 1x Gigabit RJ45 port with PoE input
* 2.4GHz: IPQ5018 802.11b/g/n/ax (2x 4dBi)
* 5GHz: QCN6024 802.11n/ac/ax (2x 5dBi)
* LEDs: 1x Status LED (Green/Yellow)
* Buttons: 1x Reset
* UART: 4-pin unpopulated header
TX RX GND VCC - JP2 (3.3V, 115200/8)
MAC addresses:
LAN : B0:19:21:xx:xx:02
2.4GHz : B0:19:21:xx:xx:02
5GHz : B0:19:21:xx:xx:03
The procedures to 'backup your stock firmware' and 'stock firmware recovery'
described in the commit "qualcommax: ipq50xx: Add support for Yuncore AX850"
are equivalent for this device.
https://git.openwrt.org/openwrt/openwrt/commit/?id=5d2994a73e20ba840d3096e1ad52add6937fe86d
Installation:
=============
TFTP method
-----------
To flash via tftp, first place the initramfs image on the TFTP server.
setenv serverip <ip of tftp server>
setenv ipaddr <ip in same subnet as tftp server>
tftpboot tplink_eap650-outdoor-v1-initramfs-uImage.itb
bootm
This should boot OpenWRT. Once booted, flash the sysupgrade.bin image
using either luci or the commandline.
Signed-off-by: Samuele Longhi <agave@dracaena.it>
Link: https://github.com/openwrt/openwrt/pull/23056
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 10:44:08 +0200c4543e374d291b3d2c711ae02e5dbe8e168e1825qualcommax: ipq50xx: add support for TP-Link EAP650-Outdoor-v1addtarget/linux/qualcommax/dts/ipq5018-eap650-outdoor-v1.dtsedittarget/linux/qualcommax/ipq50xx/base-files/etc/board.d/02_networkedittarget/linux/qualcommax/ipq50xx/base-files/lib/upgrade/platform.shedittarget/linux/qualcommax/image/ipq50xx.mkeditpackage/boot/uboot-tools/uboot-envtools/files/qualcommax_ipq50xxedittarget/linux/qualcommax/ipq50xx/base-files/etc/hotplug.d/firmware/11-ath11k-caldataeditpackage/firmware/ipq-wifi/Makefileaddtarget/linux/qualcommax/ipq50xx/base-files/lib/preinit/09_mount_factory_data
- target/linux/qualcommax/ipq50xx/base-files/etc/board.d/02_networktarget/linux/qualcommax/ipq50xx/base-files/lib/upgrade/platform.shtarget/linux/qualcommax/ipq50xx/base-files/etc/board.d/01_ledstarget/linux/qualcommax/dts/ipq5018-rax3000q.dtstarget/linux/qualcommax/image/ipq50xx.mkpackage/boot/uboot-tools/uboot-envtools/files/qualcommax_ipq50xxd592680cc501cd7decdffb50b80c964d128c22ef1790499491000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq50xx: add support for CMCC RAX3000Q/QY
Add support for the CMCC RAX3000Q/QY platform based on Qualcomm IPQ5000.
Both hardware variants are identical and share the same device tree.
Hardware Specifications:
- SoC: Qualcomm IPQ5000
- RAM: 256 MiB, integrated in SoC
- Flash: GigaDevice GD5F1GQ5REYIG (Dosilicon variant is not supported)
- 2.4 GHz Wi-Fi: SoC integrated, with 2 FEMs
- 5 GHz Wi-Fi: QCN6102, with 2 FEMs
- Switch: QCA8337, 1 WAN + 3 LAN
- LEDs: 3 RGB LEDs
- Keys: reset and mesh pairing
- UART: 3-pin, 115200n8
The vendor flash layout is documented and the ART partition contains
calibration data, which must be preserved carefully.
Due to the limited 256 MiB RAM, ath11k is disabled in the DTS to avoid
OOM issues on this device.
The MAC address location in flash could not be identified reliably.
As a temporary workaround, the MAC addresses (WAN LAN 2.4G 5G WiFi) are derived from the ART
partition start, with vendor/default values being invalid and falling
back to random generation if left unchanged (FF).
Flash Guide
Requirements
- UART access (3-pin, 115200n8)
- Ethernet cable
- TFTP server running on your computer
- OpenWrt `.ubi` firmware image
Step 0: Backup all partitions (strongly recommended)
Step 1: Connect UART and interrupt U-Boot
Step 2: Configure PC network
Step 3: Start TFTP server
Step 4: Load firmware via U-Boot
tftpboot 192.168.10.19:<your_firmware>.ubi
Step 5: Flash firmware
flash rootfs
Step 6: Reboot device
reset
Signed-off-by: Mark Jia <mark304188@hotmail.com>
2026-09-27 10:58:11 +0200d592680cc501cd7decdffb50b80c964d128c22efqualcommax: ipq50xx: add support for CMCC RAX3000Q/QYedittarget/linux/qualcommax/image/ipq50xx.mkeditpackage/boot/uboot-tools/uboot-envtools/files/qualcommax_ipq50xxedittarget/linux/qualcommax/ipq50xx/base-files/etc/board.d/01_ledsedittarget/linux/qualcommax/ipq50xx/base-files/lib/upgrade/platform.shedittarget/linux/qualcommax/ipq50xx/base-files/etc/board.d/02_networkaddtarget/linux/qualcommax/dts/ipq5018-rax3000q.dts
- package/boot/uboot-mediatek/patches/110-mtd-spinand-fmsh-add-support-for-FM25G02B.patch72f1965140672a2db2a941c3d626c0bb79d6fb1e1790500355000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deuboot-mediatek: add FudanMicro FM25G02B SPI-NAND support
The chip ships on Keenetic KN-1012 units and is not in the fmsh table,
so U-Boot finds no flash at all. Add the ID and geometry, along with the
ECC status decode its 3-bit status field needs and a read-cache list
whose quad-I/O read takes a single dummy byte.
The driver change is ported from Linux commits d5a5c9eb2ee9 ("mtd:
spinand: fmsh: add support for FM25G{01,02}B") and 8211f2d74b35 ("mtd:
spinand: fmsh: fix FM25G01B/FM25G02B Quad I/O read dummy cycles").
Only the FM25G02B entry is carried, the part in hand; the identifiers
keep upstream's FM25G01B names so that the file stays textually in step
with Linux.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Link: https://github.com/openwrt/openwrt/pull/24820
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 11:12:35 +020072f1965140672a2db2a941c3d626c0bb79d6fb1euboot-mediatek: add FudanMicro FM25G02B SPI-NAND supportaddpackage/boot/uboot-mediatek/patches/110-mtd-spinand-fmsh-add-support-for-FM25G02B.patch
- package/boot/uboot-mediatek/patches/112-nmbm-add-Kconfig-entries-for-ENABLE_NAND_NMBM.patchpackage/boot/uboot-mediatek/patches/409-arm-mediatek-allow-a-board-to-carry-the-arm64-kernel-image-header.patchpackage/boot/uboot-mediatek/Makefilepackage/boot/uboot-mediatek/patches/504-add-keenetic_kn-1012.patch99e87a79312505ca9a15a469332c74b5423a50f21790500355000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deuboot-mediatek: add Keenetic KN-1012 chainload build
The stock bootloader stays in place, so U-Boot is packaged as the
payload it accepts as a kernel and chainloaded from it.
It brings up NAND through NMBM, reads the kernel FIT from flash and
applies the device tree overlay matching the media present in the combo
port, so a single image serves both the copper PHY and the SFP cage. The
media is sensed on pio 23, the cage's mod-def0, which a seated module
pulls low. The environment tests it with "if gpio input 23", and that
reads as true for a low pin: gpio input returns the pin level as its
exit status.
The SPI-NAND is driven four-bit. The stock loader, shipped in the vendor
SDK as target/linux/mt7981/KN-1012/boot.bin, embeds an FDT whose
spi_nand@0 reads
spi-max-frequency = <0x3197500>;
spi-rx-bus-width = <0x04>;
spi-tx-bus-width = <0x04>;
on the same spi@1100a000 declaring support_quad, tick_dly = <2> and
sample_sel = <0>; MediaTek's own mt7981-rfb device tree carries the
identical pair at the identical 52 MHz. Without the two properties
spi-uclass defaults the slave to one lane and the SPI-NAND core silently
picks the single-bit read variant. The tx width also selects the
four-lane program op, which this build reaches only when NMBM has to
create its management table; the stock loader programs this part
four-bit already.
The same build serves the Keenetic and the Netcraze variant of the
board. The board support commits add a device profile for each brand,
and the two profiles produce differently named images, so the TFTP
recovery loop asks for each name in turn: the board has no populated
console to correct the name from. A single brand-neutral name was
rejected because it would match no built artifact, which breaks the
default tftpboot for both variants rather than for one. The U-Boot
device tree names the board Keenetic KN-1012 for both: the hardware is
the same and the build does not read the brand from flash.
The Kconfig entries the build relies on come as separate patches, and
both stay local: the NMBM symbols belong to the NMBM code this tree
carries, and a MediaTek bool that selects the kernel image header, with
the generic text offset base redeclared under it so the defconfig can
set it, was declined upstream. U-Boot wants a board there instead, and
this board cannot load its OS from upstream U-Boot without NMBM.
The kernel image header carries a text_offset of 0x80000: the stock
kernel FIT loads at 0x48080000, 0x80000 above the 2 MiB base the loader
works from, and the chainloader mirrors that placement. A zero offset,
which TEXT_BASE alone would give, has not been tried on this loader.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Link: https://github.com/openwrt/openwrt/pull/24820
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 11:12:35 +020099e87a79312505ca9a15a469332c74b5423a50f2uboot-mediatek: add Keenetic KN-1012 chainload buildeditpackage/boot/uboot-mediatek/Makefileaddpackage/boot/uboot-mediatek/patches/504-add-keenetic_kn-1012.patchaddpackage/boot/uboot-mediatek/patches/112-nmbm-add-Kconfig-entries-for-ENABLE_NAND_NMBM.patchaddpackage/boot/uboot-mediatek/patches/409-arm-mediatek-allow-a-board-to-carry-the-arm64-kernel-image-header.patch
- target/linux/mediatek/filogic/base-files/etc/hotplug.d/ieee80211/11_fix_wifi_mactarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012-copper.dtsotarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012-sfp.dtsotarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012.dtstarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012.dtsitarget/linux/mediatek/filogic/base-files/etc/board.d/01_ledstarget/linux/mediatek/image/filogic.mk87d7b11bd5b422e6e6b6b43dde137d75460ac15a1790500356000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: filogic: add support for Keenetic KN-1012
Keenetic KN-1012 is a 2.4/5 GHz band 11ax (Wi-Fi 6) router with a
combo SFP/copper port, based on MT7981B.
The copper side of the combo port does not come up on this tree yet. It
needs the pending phylink change that defers the PHY attach for PHYs
marked needs-host-firmware until their driver has bound,
https://lore.kernel.org/r/20260914211137.2760618-1-f@lex.la/, and that
property on the PHY node, which goes in together with the change.
Everything else on the board, the SFP side of the same port included,
works without them.
Specification:
- SoC : MediaTek MT7981B
- RAM : 512 MiB
- Flash : SPI-NAND 256 MiB (chip varies by production run,
Fudan Micro FM25G02B seen)
- WLAN : 2.4/5 GHz 2T2R (MediaTek MT7981B (SoC))
- Ethernet : 4x 10/100/1000 Mbps + 1x combo port
- switch : MediaTek MT7531
- combo port : SFP cage and an Airoha EN8811H 2.5G copper PHY
share one SerDes, selected by a GPIO mux
- USB : USB 2.0 through a GL850G-OHY60 hub, two switchable
power rails
- LEDs/Keys (GPIO): 6x/4x
- UART : through-hole on PCB (J500), unconfirmed
- assignment : 5V, TX, RX, NC, GND
- settings : 115200n8
- Power : 12 VDC, 2.5 A, center positive
The vendor bootloader stays in place, so U-Boot is chainloaded from it
as the payload it accepts as a kernel. It reads the GPIO reporting
whether an SFP module is present and boots the device tree matching the
medium, so one image serves both the copper PHY and the SFP cage. The
chainloader itself is wrapped into a FIT shaped like the vendor kernel
image, kernel@1 / fdt@1 / config@1 with the "Linux 4.9" description,
because the stock loader accepted a payload generated by mkits.sh with
its default node names and descriptions but never ran it. Both vendor
firmware slots (firmware_1, storage_a, firmware_2, storage_b) are
concatenated into one virtual flash, its first 8 MiB the kernel
partition and the rest UBI, so the second slot no longer holds a vendor-
bootable image; u-state stays read-only. The factory image is bounded to
the first firmware slot, where the stock recovery writes it; whether the
recovery writes past that slot is untested.
Flash instruction using the vendor recovery mode:
1. Connect the TFTP host to one of the LAN ports, address 192.168.1.2
2. Rename the factory image to "KN-1012_recovery.bin" and put it in
the TFTP directory
3. Power off the device, hold the "Reset" button, power it on and keep
the button held for ~10 seconds
4. The bootloader downloads the image over TFTP and writes it to flash
5. Wait for the device to reboot, it comes up on 192.168.1.1
Reverting to stock image:
1. Download the official recovery package for the model and take the
.bin image out of it
2. Follow the same steps as above with that image in place of the
OpenWrt one
MAC addresses:
use source
LAN rf-eeprom 0x4
WAN rf-eeprom 0xa, also the address on the label
2g rf-eeprom 0x4, the first MAC slot of the WiFi EEPROM
5g rf-eeprom 0x4 with the locally administered bit set and bit 7
flipped
Left alone, mt76 would read the second EEPROM slot at 0xa for phy1
and collide with the WAN address, so the board joins the Keenetic
family entry in 11_fix_wifi_mac, which derives phy1 from the 0x4 slot
the way mt76 would on its own: LA bit set, bit 7 flipped.
The P and N of the SerDes lane from the switch to the EN8811H are
swapped on this board, like on the BPI-R3 mini, so the copper PHY node
sets rx-polarity to PHY_POL_INVERT, the current form of the
airoha,pnswap-rx property the BPI-R3 mini still carries. Without it the
copper side links up at any speed but transmits nothing, while receive
works.
The copper PHY's INTB is on pio 0 and the PHY node declares it; the
vendor tree hangs the same line on the switch node and calls it level
low. This uses edge falling, as the BPI-R3 mini does for its EN8811H
PHYs. On this tree the line is not used yet: phylib sets phydev->irq to
PHY_POLL when the port attaches the PHY with the generic driver still
bound at switch probe, and nothing restores it when the EN8811H driver
binds later. With the phylink change named at the top and the phylib
change that keeps the interrupt across the driver swap,
https://lore.kernel.org/r/20260919015326.499479-1-f@lex.la/, forced
renegotiations on this board delivered the link-down and link-up events
over INTB and left no interrupt unhandled.
The copper port stays down on this tree because the switch attaches the
PHY at probe, before the EN8811H driver can load its firmware from the
root filesystem, and phylink refuses 2500base-x against the generic
driver, so DSA drops the port. The copper results above were taken with
the phylink change named at the top applied; SFP, lan1 to lan3, WAN and
wifi do not depend on it. The SFP side was booted with a DAC in the
cage: the loader picked the SFP configuration, the module EEPROM read
over I2C, lan4 came up over the cage without the PHY race and the cage's
indicator LED lit; on copper that LED stays off. Link and traffic over
the SFP path stand on the earlier two-tree form of the image, 1 Gbit/s
against a 1 Gbit/s partner, with the module pulled bringing the board
back on copper.
The board support (pin map, SFP node, copper PHY description, image
recipe parameters and LED assignments) is based on the out-of-tree port
by Maxim Anisimov, branch main_keenetic_kn1012 of Linaro1985/openwrt.
The chainloader and the U-Boot side are new relative to that port, as
is the split into a shared dtsi with a device tree overlay per medium,
which the chainloader applies.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Link: https://github.com/openwrt/openwrt/pull/24820
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 11:12:36 +020087d7b11bd5b422e6e6b6b43dde137d75460ac15amediatek: filogic: add support for Keenetic KN-1012edittarget/linux/mediatek/filogic/base-files/etc/board.d/01_ledsaddtarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012-sfp.dtsoedittarget/linux/mediatek/image/filogic.mkaddtarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012.dtsedittarget/linux/mediatek/filogic/base-files/etc/hotplug.d/ieee80211/11_fix_wifi_macaddtarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012-copper.dtsoaddtarget/linux/mediatek/dts/mt7981b-keenetic-kn-1012.dtsi
- target/linux/mediatek/filogic/base-files/etc/board.d/01_ledstarget/linux/mediatek/filogic/base-files/etc/hotplug.d/ieee80211/11_fix_wifi_mactarget/linux/mediatek/dts/mt7981b-netcraze-nc-1012.dtstarget/linux/mediatek/image/filogic.mk492a0ff6b13aead1dc2a54def9160cc38550c0321790500356000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.demediatek: filogic: add support for Netcraze NC-1012
The Netcraze NC-1012 is a rebrand of the Keenetic KN-1012 with identical
hardware. The stock recovery accepts only images signed with the NC-1012
zyimage device id, taken here from the official NC-1012 recovery image.
It shares the KN-1012 device tree through the common dtsi and the copper
and SFP overlays, and the image recipe through the common device define,
following the KN-3411/NC-3411 pattern. The recovery procedure is the
KN-1012 one with the image named NC-1012_recovery.bin.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Link: https://github.com/openwrt/openwrt/pull/24820
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 11:12:36 +0200492a0ff6b13aead1dc2a54def9160cc38550c032mediatek: filogic: add support for Netcraze NC-1012addtarget/linux/mediatek/dts/mt7981b-netcraze-nc-1012.dtsedittarget/linux/mediatek/filogic/base-files/etc/board.d/01_ledsedittarget/linux/mediatek/filogic/base-files/etc/hotplug.d/ieee80211/11_fix_wifi_macedittarget/linux/mediatek/image/filogic.mk
- package/firmware/ipq-wifi/Makefile6e7bccd2a38a63c4f4925492449e826438bf80371790500662000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comipq-wifi: update to Git HEAD (2026-09-27)
a215395b9338 ipq5018: add BDF for GL.iNet GL-X2000
7b66ac970c91 qcn6122: add BDF for GL.iNet GL-X2000
3eba07d9b5c9 ipq5018: add AVM FRITZ!Box 4050 BDFs
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 11:17:42 +02006e7bccd2a38a63c4f4925492449e826438bf8037ipq-wifi: update to Git HEAD (2026-09-27)editpackage/firmware/ipq-wifi/Makefile
- package/boot/uboot-tools/Makefilepackage/boot/uboot-tools/uboot-envtools/files/qualcommbe_ipq95xx6fb5b53af27e03abe80abeacc346a733bb6deb861790501300000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comuboot-envtools: add Linksys LN6001 support
Map the existing 256 KiB u_env eMMC partition for the Linksys LN6001.
This lets the device upgrade path read and update the existing boot-slot
environment through fw_printenv and fw_setenv.
Increment the package release for the functional board-map addition.
Signed-off-by: Satoshi Ikeuchi <satosan.ikm@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24736
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 11:28:20 +02006fb5b53af27e03abe80abeacc346a733bb6deb86uboot-envtools: add Linksys LN6001 supporteditpackage/boot/uboot-tools/Makefileeditpackage/boot/uboot-tools/uboot-envtools/files/qualcommbe_ipq95xx
- target/linux/qualcommbe/dts/ipq9554-linksys-ln6001.dtstarget/linux/qualcommbe/ipq95xx/base-files/lib/upgrade/platform.shtarget/linux/qualcommbe/image/ipq95xx.mktarget/linux/qualcommbe/config-6.18target/linux/qualcommbe/ipq95xx/base-files/etc/board.d/02_networktarget/linux/qualcommbe/ipq95xx/base-files/etc/init.d/bootcounttarget/linux/qualcommbe/ipq95xx/base-files/lib/upgrade/ln6001.sh614d968227780f497164538234531d62bcb587f71790501300000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommbe: add Linksys LN6001 support
Add wired support and an eMMC A/B sysupgrade path for the Linksys LN6001.
Write and verify the inactive kernel/rootfs pair before changing the boot
selectors. Confirm an installed boot by clearing the s_env boot counter
and updating its checksum.
Identify the board as IPQ9554, using the shared ipq9574.dtsi and family
fallback compatible. Disable the absent UNIPHY1 block and provide the
board clocks required by eMMC, MDIO and PWM. Let U-Boot populate memory
size, use the default GPIO-key debounce and allow 10 ms for QCA8081 reset
assertion while retaining the 150 ms deassertion delay. Use decimal 28
for the QCA8081 PHY address. The assertion delay follows the QCA8081
precedent in 904aa4386548.
Return to common upgrade cleanup and reboot after safe staging failures,
while stopping on uncertain boot selector state.
Hardware specification:
- SoC: Qualcomm IPQ9554
- RAM: 1 GiB DDR4
- Flash: 8 GB Samsung 8GTF4R eMMC
- Ethernet: four 1 GbE LAN ports through QCA8075 over PSGMII
- Ethernet: one 2.5 GbE WAN port through QCA8081
- LEDs: red, green, blue and white PWM status channels
- Buttons: reset and WPS GPIO keys
- UART: 115200 8N1
- Power: 12 V, 2.5 A
- Wireless and Bluetooth: not enabled
Installation:
The initial installation uses serial access and an OpenWrt RAM boot.
Keep a bootable stock slot and start with that slot selected. The updater
accepts only the observed retail GPT geometry, matching bootconfig copies,
boot_part_ready=3, auto_recovery=yes and matching Wi-Fi firmware slots.
It does not repair an inconsistent layout or selector state.
Copy this image to the TFTP server as ln6001-initramfs.itb:
openwrt-qualcommbe-ipq95xx-linksys_ln6001-initramfs-uImage.itb
Connect Ethernet to LAN4 and configure the TFTP server as 192.168.1.254/24.
Interrupt U-Boot autoboot through the serial console and run:
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.254
setenv netmask 255.255.255.0
tftp 0x4d100000 ln6001-initramfs.itb
bootm 0x4d100000#config@1
Do not save these temporary network settings or write the initramfs FIT
to eMMC. In RAM-booted OpenWrt, transfer the following image to
/tmp/ln6001-sysupgrade.bin:
openwrt-qualcommbe-ipq95xx-linksys_ln6001-squashfs-sysupgrade.bin
Check the selected slot and validate the image, then install:
fw_printenv boot_part boot_part_ready auto_recovery
sysupgrade -T /tmp/ln6001-sysupgrade.bin
sysupgrade -n /tmp/ln6001-sysupgrade.bin
Run the last command only after validation succeeds. boot_part=1 selects
A and installation writes B; boot_part=2 selects B and installation
writes A. Do not force a failed check. The sysupgrade archive is not a
Linksys web-update image. Subsequent OpenWrt sysupgrades use the same
inactive-slot path; omit -n to request preservation of OpenWrt settings.
Recovery:
The serial TFTP/bootm procedure remains available without depending on
the installed rootfs. Before installation, resetting a RAM-only session
returns to the selected existing firmware. After installation, a normal
reboot uses the newly selected slot and does not itself return to stock.
With consistent selector copies and environment, a recovery RAM boot can
run the same checked sysupgrade path. Inconsistent selectors are rejected;
do not bypass these checks. Keep serial access and a bootable other slot.
Partition and MAC address handling:
Discover the existing GPT at runtime and require the retail partition
labels, starts and sizes before writing. Preserve the GPT, bootloader,
devinfo and both Wi-Fi firmware payloads. The upgrade writes the inactive
HLOS/rootfs pair, then updates both bootconfig selector sectors and the
boot_part environment variable. Successful installed boots clear the
boot counter and update its checksum in s_env after verifying the active
slot. A stale checksum on an already-zero counter is repaired as well.
Read hw_mac_addr from devinfo through read-only block NVMEM. Stock LAN
and WAN use the same base address; assign offset zero to all five wired
ports. Configuration persists in a per-slot F2FS overlay.
Validation:
Retail-hardware testing passed RAM boot with U-Boot supplying 1
GiB RAM, and sysupgrade -n from stock-selected A into B followed
by two successful installed boots. The boot-count record
contained a zero count and valid checksum after both boots. F2FS
remained writable and a UCI setting persisted across reboot.
Kernel/rootfs readback matched the image; full stock A hashes and
non-selector protected partition hashes were unchanged.
LAN4 linked at 1 Gbps. WAN-to-WAN testing against a stock LN6001
negotiated 2500 Mbps full duplex at both ends and recovered to
that rate after cable replug without reboot or interface reset.
Normal and full-MTU IPv6 pings passed without loss before and
after replug. Separate four-stream TCP endpoint tests measured
2.313 Gbit/s received by this image and 2.311 Gbit/s by the peer,
then 2.316 Gbit/s received after replug. These are router-local
tests, not forwarding benchmarks. One RX error at the
disconnected checkpoint did not increase during subsequent
traffic; TX and peer RX/TX error counters remained zero.
Fifteen local synthetic tests cover boot-counter checksum
validation and repair, write/readback failures, upgrade guards
and safe return versus deliberate halt. Seven temporary-file
bootcount test groups also passed on the device. Real boot
selectors were not corrupted for failure tests. Image-macro
checks confirm sysupgrade.bin only with the size guard retained.
Signed-off-by: Satoshi Ikeuchi <satosan.ikm@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24736
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 11:28:20 +0200614d968227780f497164538234531d62bcb587f7qualcommbe: add Linksys LN6001 supportedittarget/linux/qualcommbe/image/ipq95xx.mkaddtarget/linux/qualcommbe/ipq95xx/base-files/lib/upgrade/ln6001.shaddtarget/linux/qualcommbe/dts/ipq9554-linksys-ln6001.dtsedittarget/linux/qualcommbe/ipq95xx/base-files/etc/board.d/02_networkaddtarget/linux/qualcommbe/ipq95xx/base-files/etc/init.d/bootcountedittarget/linux/qualcommbe/ipq95xx/base-files/lib/upgrade/platform.shedittarget/linux/qualcommbe/config-6.18
- target/linux/generic/pending-6.12/711-04-net-dsa-qca8k-skip-host-FDB-entries-on-CPU-ports-purge-stale.patchtarget/linux/generic/pending-6.18/711-04-net-dsa-qca8k-no-program-unicast-host-FDB-entries.patchtarget/linux/generic/pending-6.12/711-04-net-dsa-qca8k-no-program-unicast-host-FDB-entries.patchtarget/linux/generic/pending-6.18/711-04-net-dsa-qca8k-skip-host-FDB-entries-on-CPU-ports-purge-stale.patchtarget/linux/ipq40xx/patches-6.18/706-net-dsa-qca8k-add-IPQ4019-built-in-switch-support.patch42656fee2244bdf07a3652c6f311355a5630df381790501405000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dekernel: qca8k: skip host FDB entries on CPU ports, purge stale dynamic ones
Rework 711-04-net-dsa-qca8k-no-program-unicast-host-FDB-entries.patch:
host FDB adds on CPU ports are skipped, relying on unknown-unicast
flooding to deliver host-bound frames to the CPU. That assumption
breaks when a station roams from a wired user port onto an interface
behind the CPU (wireless AP and WDS setups): a stale dynamically
learned ATU entry still points at the old user port, so downstream
frames hit it and are dropped by same-port filtering instead of being
flooded to the CPU. With CPU-port hardware learning disabled (assisted
learning), nothing ever corrects the entry - clients roaming onto the
device stay blackholed while the device itself stays reachable.
Purge any dynamically learned ATU entry for {addr, vid} when the host
add is skipped, so the address becomes unknown unicast again - exactly
the delivery mechanism the skip relies on. Static entries are left
untouched, and the companion skip in qca8k_port_fdb_del is kept so
host address removal does not purge legitimately learned entries.
Also refresh ipq40xx's 706 patch for the shifted hunk offsets.
Tested on IPQ4019 (Google WiFi APs): stale entries are purged at
association time and roaming recovers instantly.
Fixes: 9716066e80 ("kernel: add qualcommax patches to generic")
Signed-off-by: Brandon Mahdavi <brandon.mahdavi@mahcom.com>
Link: https://github.com/openwrt/openwrt/pull/24162
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 11:30:05 +020042656fee2244bdf07a3652c6f311355a5630df38kernel: qca8k: skip host FDB entries on CPU ports, purge stale dynamic onesdeletetarget/linux/generic/pending-6.18/711-04-net-dsa-qca8k-no-program-unicast-host-FDB-entries.patchedittarget/linux/ipq40xx/patches-6.18/706-net-dsa-qca8k-add-IPQ4019-built-in-switch-support.patchdeletetarget/linux/generic/pending-6.12/711-04-net-dsa-qca8k-no-program-unicast-host-FDB-entries.patchaddtarget/linux/generic/pending-6.12/711-04-net-dsa-qca8k-skip-host-FDB-entries-on-CPU-ports-purge-stale.patchaddtarget/linux/generic/pending-6.18/711-04-net-dsa-qca8k-skip-host-FDB-entries-on-CPU-ports-purge-stale.patch
- package/kernel/linux/modules/netdevices.mk57072d9ebb29a40ddf8f6fb2333bdd425cf523321790501992000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comkernel: netdevices: enable MACsec support for mlx5-core
Enable MACsec (Media Access Control Security) support in the Mellanox
mlx5 driver by setting CONFIG_MLX5_MACSEC=y.
Enabling this configuration allows users to utilize hardware MACsec
offload capabilities on supported Mellanox ConnectX network adapters.
This provides point-to-point Layer 2 encryption at line rate while
significantly reducing CPU overhead.
The kmod-macsec dependency is intentionally omitted to make this an
opt-in feature. The offload support only builds if kmod-macsec is
also selected, preventing driver bloat for standard users.
Signed-off-by: Til Kaiser <mail@tk154.de>
Link: https://github.com/openwrt/openwrt/pull/25400
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-09-27 11:39:52 +020057072d9ebb29a40ddf8f6fb2333bdd425cf52332kernel: netdevices: enable MACsec support for mlx5-coreeditpackage/kernel/linux/modules/netdevices.mk
- target/linux/realtek/files-6.18/drivers/phy/realtek/phy-rtk-pcie.cab58ca8fc0e36c526d3590b97f9ef6f90828cd7f1790513936000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.derealtek: phy: add delay to fix pcie link up failures
The current pcie phy driver results in inconsistent failures on PCIe linkup,
different from one boot to another. Doing some testing, it has became clear
that mdio operations are at fault. The mdio seem to require an additional
delay after it has completed an operation and reported status of done. The
mdio ready bit however, is unchanged and so doesn't have any connection to
this "after completion" delay.
Fix the issue by adding an additional delay after regmap polling and remove
MDIO_READY from cond variable as it is unrelated. Change the function name
to rtk_phy_poll_done_and_delay() to go along with the changes. Mostly as a
guess but 10 us is enough delay to fix the inconsistent failures. Tested by
booting an image on rtl9607c machine 4 times and no failed link ups happen.
Add the fsleep() after regmap_read() in rtk_phy_read() as it also triggers
something in phy mdio controller that require the same delay.
Fixes: bb00e9f0974f ("realtek: phy: add support for rtl9607c pcie phy")
Signed-off-by: Rustam Adilov <adilov@tutamail.com>
Link: https://github.com/openwrt/openwrt/pull/25412
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 14:58:56 +0200ab58ca8fc0e36c526d3590b97f9ef6f90828cd7frealtek: phy: add delay to fix pcie link up failuresedittarget/linux/realtek/files-6.18/drivers/phy/realtek/phy-rtk-pcie.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.cf9ee620893c3214d661c80fefe943eb09224e2c11790535996000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: l3: drop a warning built on a value nobody set
The netevent handler ends by testing an err it never assigns and prints
a netdev warning with whatever the stack left there. Nothing it does can
fail at that point: the work it has just queued is what could, and that
happens somewhere else entirely.
No build says so, because the kernel turns -Wmaybe-uninitialized off for
GCC outside W=2 (scripts/Makefile.extrawarn).
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25311
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 21:06:36 +0200f9ee620893c3214d661c80fefe943eb09224e2c1realtek: l3: drop a warning built on a value nobody setedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.c5b0782cd0e5ad33ec3ad97a4f3f594927e0518f71790537930000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: l3: leave the RCU section before writing a table
Programming the routes that were waiting on a neighbour runs the whole
of otto_l3_nexthop_update() inside rcu_read_lock(), and everything it
does there ends in otto_table_acquire(), which takes a mutex.
Where this kernel is built there is no preemptible RCU, so that section
is a preempt_disable(): taking a mutex in it is fine only while the
mutex is free, and the moment it is not, the wait for it is a schedule()
with preemption off. Nothing says so at build time either, since
DEBUG_ATOMIC_SLEEP is off in the generic config and the might_sleep()
that would have complained is compiled out.
The other side of that mutex is not hypothetical. The router MAC, the
four host route tables, the four prefix route tables and the next hop
table are reached through one access register and so share one lock,
and this function writes three of them. The debugfs route dump holds
that same lock across a sweep of 8192 addresses and calls
cond_resched() every 64 rows, which is to say it sleeps with it held,
by design and legitimately. A neighbour resolving while someone reads
that file is all it takes.
Keep the section the rhashtable asks for around the lookup, which is
what needs it, and end it there. The routes the lookup would have walked
are the ones on the driver's own list with that gateway, and the list is
what the rest of this file already walks: the work queue behind every
route added, removed or programmed is single threaded, which is the
invariant the teardown path states and relies on.
Holding ctrl->lock instead was the smaller diff and would have been
wrong: it serialises this driver's insertions, not the rhashtable's own
shrink worker, which is what the RCU section is there for.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25447
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 21:38:50 +02005b0782cd0e5ad33ec3ad97a4f3f594927e0518f7realtek: l3: leave the RCU section before writing a tableedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.ce96716c4ef65c8f7590face49292b6066f26caf21790537930000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: l3: do not look for a route that was never placed
A prefix route is given its row when its gateway resolves, and until
then it carries the -1 its allocator wrote there. A route with no
gateway to resolve keeps that value for its whole life, and a connected
route is exactly that: nothing routes inside its own subnet, so nothing
ever places it.
Removing one still takes the hardware side of the removal path, because
the test there asks whether the ops can look a route up, not whether
this route was ever written. So the CAM is searched for an entry that
was never in it, and the answer is reported as a fault: on a plain
dual-stack box, "prefix route 192.168.1.0/24 was not in hardware" at
every restart of the network.
The noise is not the whole of it. That search keys on the masked
destination, so a shorter prefix covering the same address answers it,
and the row that comes back is then reported as holding another route -
which it does, and rightly, because it is not this route's row and never
was.
Ask the row the driver recorded instead. Both messages stay for the case
they were written for, a route that was placed and is no longer where
the driver put it, which is the state a half-finished row move leaves
behind.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25447
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 21:38:50 +0200e96716c4ef65c8f7590face49292b6066f26caf2realtek: l3: do not look for a route that was never placededittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l3.c
- target/linux/tegra/config-6.18target/linux/tegra/patches-6.12/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patchtarget/linux/tegra/patches-6.18/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patchtarget/linux/tegra/config-6.12dbea6b4972f3d7c9c1983fc6c634cf2aa66e753b1790538668000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dekernel/tegra: create files for v6.18 (from v6.12)
This is an automatically generated commit.
When doing `git bisect`, consider `git bisect --skip`.
Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
Link: https://patchwork.ozlabs.org/project/openwrt/patch/20260507135738.5684-2-tmn505@terefe.re/
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 21:51:08 +0200dbea6b4972f3d7c9c1983fc6c634cf2aa66e753bkernel/tegra: create files for v6.18 (from v6.12)addtarget/linux/tegra/patches-6.18/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patchdeletetarget/linux/tegra/config-6.12deletetarget/linux/tegra/patches-6.12/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patchaddtarget/linux/tegra/config-6.18
- target/linux/tegra/patches-6.12/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patchtarget/linux/tegra/config-6.121d019b3978db229aef2144e07430017c838a5bee1790538669000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.dekernel/tegra: restore files for v6.12
This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.
For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html
Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
Link: https://patchwork.ozlabs.org/project/openwrt/patch/20260507135738.5684-3-tmn505@terefe.re/
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 21:51:09 +02001d019b3978db229aef2144e07430017c838a5beekernel/tegra: restore files for v6.12addtarget/linux/tegra/config-6.12addtarget/linux/tegra/patches-6.12/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patch
- target/linux/tegra/config-6.18target/linux/tegra/patches-6.18/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patch7de485e59897aacc421b2df1a5de02cac1eaa9d61790538669000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.detegra: 6.18: refresh config and patches
No functional changes.
Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
Link: https://patchwork.ozlabs.org/project/openwrt/patch/20260507135738.5684-4-tmn505@terefe.re/
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 21:51:09 +02007de485e59897aacc421b2df1a5de02cac1eaa9d6tegra: 6.18: refresh config and patchesedittarget/linux/tegra/config-6.18edittarget/linux/tegra/patches-6.18/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patch
- target/linux/tegra/Makefile58c36f0bce0a5a7f5be09b7cfd5a763f80a9d4d71790538669000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.detegra: add 6.18 as testing kernel
Allow to select 6.18 as testing kernel.
Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
Link: https://patchwork.ozlabs.org/project/openwrt/patch/20260507135738.5684-5-tmn505@terefe.re/
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 21:51:09 +020058c36f0bce0a5a7f5be09b7cfd5a763f80a9d4d7tegra: add 6.18 as testing kerneledittarget/linux/tegra/Makefile
- package/boot/uboot-tegra/Makefilepackage/boot/uboot-tegra/patches/001-scripts-dtc-drop-yaml-in-DT-validation.patch4186150dbbb879f033b230a416f2f9ba6adde2e81790538669000https://taiha.net/jenkins/user/jonasjonasjonas@jonasjelonek.deuboot-tegra: bump version to 2026.04
Maintenence bump, no new features.
Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
Link: https://patchwork.ozlabs.org/project/openwrt/patch/20260507135738.5684-6-tmn505@terefe.re/
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
2026-09-27 21:51:09 +02004186150dbbb879f033b230a416f2f9ba6adde2e8uboot-tegra: bump version to 2026.04editpackage/boot/uboot-tegra/Makefileaddpackage/boot/uboot-tegra/patches/001-scripts-dtc-drop-yaml-in-DT-validation.patch
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.c48b6665b178c67125913d5cf55c3c0a94d6f03f01790539273000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: report only unicast rows in the FDB dump
rtldsa_port_fdb_dump() reuses one uninitialised entry for every row it
reads, but the fill functions do not write every field for every row
type. RTL838x and RTL839x never write is_trunk, so the test that skips
trunk entries reads a stack value for the whole walk and can drop every
hardware entry from bridge fdb show. An L2 multicast row leaves port
and is_static untouched on all families, and vid too on RTL930x and
RTL931x, so it is reported on the port of whatever row came before it.
Zero the entry for every row and report only L2_UNICAST rows, as
mv88e6xxx and b53 do. On RTL838x and RTL839x this skips IP multicast
rows as well. On RTL930x and RTL931x unicast rows are reported as
before, and the driver writes no multicast rows of its own: a static
FDB entry with a multicast MAC, which rtldsa_port_fdb_add() stores as a
unicast row there, reads back as multicast and is no longer reported.
Tested on an RTL9303 (Hasivo S1100W-8XGT-SE), with the L2 table dump of
PR #25394 as the reference and two follow-ups that change only the loop
bounds, which are the same on RTL930x. With 150 static and 16 learned
entries, bridge fdb show listed exactly the 166 unicast rows the
hardware held on user ports. A static FDB entry with a multicast MAC,
present in the table as an L2 multicast row, was not reported on any
user port. Not tested on RTL838x, RTL839x or RTL931x hardware.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25398
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 22:01:13 +020048b6665b178c67125913d5cf55c3c0a94d6f03f0realtek: dsa: report only unicast rows in the FDB dumpedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/dsa.c
- target/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/rtl839x.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.cfb9c8bf5ef88025425e6c1cd8dcb4bc84de53c0c1790539644000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: add the L2 table ids to the family config
The L2 debugfs dump walks fib_entries rows of the hash table and a
fixed 64 rows of the CAM. That covers both tables on RTL838x, RTL839x
and RTL930x, but not on RTL931x: otto_table.c maps the RTL9310 L2 table
with 32768 rows and its CAM with 128, while fib_entries stays at 16384
there (its TODO says the code cannot handle 32K). fib_entries also
sizes l2_uc_map and bounds the fdb_dump walk, so raising it is a change
of its own.
Record which otto_table ids hold the L2 hash table and the CAM of each
family, so a dump can take the row counts from otto_table_rows()
instead. Nothing reads the new fields yet, so this is a no-op on all
four families.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25394
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 22:07:24 +0200fb9c8bf5ef88025425e6c1cd8dcb4bc84de53c0crealtek: dsa: add the L2 table ids to the family configedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl931x.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.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/rtl839x.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l2.ctarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l2.ha980e72e6d34f27789fd10f4acdf6496e7896ef91790539644000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: add an L2 table dump to realtek_otto_l2
The only debugfs dump of the L2 table is rtl838x/l2_table in
debugfs.c. It walks fib_entries rows of the hash table and 64 rows of
the CAM, which leaves half of both unread on RTL931x. On RTL838x and
RTL839x its entry is not initialised and the fill functions of those
families never set is_trunk or trunk, so a stack value can be printed
as trunk data and used as an index into the LAG arrays.
Add the dump to l2.c as realtek_otto_l2/fdb, next to realtek_otto_l3.
It takes the row counts of the hash table and the CAM from
otto_table_rows(), so on RTL931x it reads all 32768 hash rows and 128
CAM rows. The upper hash rows are ones the driver already writes: on
RTL931x the second hash block starts at row 16384. The entry is zeroed
for every row, and the walk yields the CPU every 64 rows whether or not
they are valid, where the old loop only reached cond_resched() on a
valid row. The output format is unchanged.
debugfs.c keeps its copy until the next commit.
Tested on an RTL9303 (Hasivo S1100W-8XGT-SE) at this commit, where both
files exist: with 150 static FDB entries added, rtl838x/l2_table and
realtek_otto_l2/fdb listed the same 182 entries on three back-to-back
reads, identical apart from the age of learned entries. Reading the new
file in 64-byte chunks matched a single read, ages aside, and
CONFIG_DEBUG_ATOMIC_SLEEP reported nothing. Not tested on RTL838x,
RTL839x or RTL931x hardware.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25394
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 22:07:24 +0200a980e72e6d34f27789fd10f4acdf6496e7896ef9realtek: dsa: add an L2 table dump to realtek_otto_l2edittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/common.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l2.hedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/l2.c
- target/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/debugfs.c101929399c12644ac8c3fe9b11b83c93fe9ee7551790539644000https://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenmarkus.stockhausen@gmx.derealtek: dsa: drop the L2 table dump from debugfs.c
The L2 table dump now lives in l2.c as realtek_otto_l2/fdb and reads
the whole table on every family. Remove the old rtl838x/l2_table copy,
which stopped at half the table on RTL931x and could print stack
contents as trunk data on RTL838x and RTL839x.
The other files in the rtl838x debugfs directory are unchanged.
Tested on an RTL9303 (Hasivo S1100W-8XGT-SE): rtl838x/l2_table is gone
and realtek_otto_l2/fdb lists 150 static FDB entries next to the
learned ones.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25394
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
2026-09-27 22:07:24 +0200101929399c12644ac8c3fe9b11b83c93fe9ee755realtek: dsa: drop the L2 table dump from debugfs.cedittarget/linux/realtek/files-6.18/drivers/net/dsa/rtl83xx/debugfs.c
- target/linux/generic/backport-6.12/630-v6.13-net-usb-qmi_wwan-add-Quectel-RG255C.patchtarget/linux/generic/kernel-6.12target/linux/generic/pending-6.12/666-Add-support-for-MAP-E-FMRs-mesh-mode.patchtarget/linux/generic/backport-6.12/942-07-v7.2-net-dsa-realtek-rtl8365mb-add-FDB-support.patch5150a2ede192f609bf8894b75aa2794e346aef991790550358000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: bump 6.12 to 6.12.109
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.109
All patches are automatically refreshed.
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/25179
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-28 01:05:58 +02005150a2ede192f609bf8894b75aa2794e346aef99kernel: bump 6.12 to 6.12.109edittarget/linux/generic/pending-6.12/666-Add-support-for-MAP-E-FMRs-mesh-mode.patchedittarget/linux/generic/backport-6.12/630-v6.13-net-usb-qmi_wwan-add-Quectel-RG255C.patchedittarget/linux/generic/kernel-6.12edittarget/linux/generic/backport-6.12/942-07-v7.2-net-dsa-realtek-rtl8365mb-add-FDB-support.patch
- target/linux/generic/pending-6.12/342-powerpc-Enable-kernel-XZ-compression-option-on-PPC_8.patchtarget/linux/generic/backport-6.12/202-v6.13-clk-Provide-devm_clk_bulk_get_all_enabled-helper.patchtarget/linux/generic/pending-6.12/400-mtd-mtdsplit-support.patchtarget/linux/generic/pending-6.12/812-PCI-sysfs-enforce-single-creation-of-sysfs-entry-for.patchtarget/linux/generic/hack-6.12/610-net-page_pool-try-to-free-deferred-skbs-while-waitin.patchtarget/linux/generic/hack-6.12/200-tools_portability.patchtarget/linux/generic/backport-6.12/501-v6.19-ksmbd-server-avoid-busy-polling-in-accept-loop.patchtarget/linux/generic/config-6.12target/linux/generic/backport-6.12/502-v7.3-smb-server-fix-signing-multi-iov-response.patchtarget/linux/generic/pending-6.12/739-05-net-pcs-add-driver-for-MediaTek-USXGMII-PCS.patchtarget/linux/generic/pending-6.12/510-block-add-uImage.FIT-subimage-block-driver.patchtarget/linux/generic/backport-6.12/720-04-v6.13-net-phy-mediatek-Re-organize-MediaTek-ethernet-phy-d.patchtarget/linux/generic/hack-6.12/660-fq_codel_defaults.patchtarget/linux/generic/backport-6.12/500-02-v6.13-block-introduce-add_disk_fwnode.patchtarget/linux/generic/pending-6.12/790-bus-mhi-core-add-SBL-state-callback.patchtarget/linux/generic/backport-6.12/626-16b-v6.17-regulator-Add-support-for-power-budget.patchtarget/linux/generic/backport-6.12/504-v7.3-ksmbd-fix-listener-task-lifetime-on-netdev-events.patchtarget/linux/generic/kernel-6.12target/linux/generic/pending-6.12/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patchtarget/linux/generic/backport-6.12/720-05-v6.13-net-phy-mediatek-Move-LED-helper-functions-into-mtk-.patchtarget/linux/generic/backport-6.12/201-v6.13-of-property-add-of_graph_get_next_port.patchtarget/linux/generic/backport-6.12/503-02-v7.3-ksmbd-keep-tcp-timers-alive-for-kernel-sockets.patchtarget/linux/generic/backport-6.12/700-01-v7.0-net-sched-Export-mq-functions-for-reuse.patch0d3a5dfdf4a11ba2ee4ed122a1dfbedf2a172c451790550358000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: bump 6.12 to 6.12.110
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.110
Upstream merged patches:
- generic/backport-6.12/201-v6.13-of-property-add-of_graph_get_next_port.patch[1]
Manually rebased patches:
- generic/hack-6.12/200-tools_portability.patch[2]
kconfig symbol changes:
- Rename GENERIC_PTDUMP -> ARCH_HAS_PTDUMP[3]
All other patches are automatically refreshed.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=59d1a468e5e53bc8ca274966ee1935c39e403593
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11bdce7911eba18d96283a212a9b8435cc4b94d2
[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=654a60dcc384ae2cb65bbb59d11a3e7c3911b446
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/25179
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-28 01:05:58 +02000d3a5dfdf4a11ba2ee4ed122a1dfbedf2a172c45kernel: bump 6.12 to 6.12.110edittarget/linux/generic/backport-6.12/500-02-v6.13-block-introduce-add_disk_fwnode.patchedittarget/linux/generic/pending-6.12/400-mtd-mtdsplit-support.patchedittarget/linux/generic/backport-6.12/626-16b-v6.17-regulator-Add-support-for-power-budget.patchedittarget/linux/generic/hack-6.12/610-net-page_pool-try-to-free-deferred-skbs-while-waitin.patchedittarget/linux/generic/config-6.12edittarget/linux/generic/hack-6.12/200-tools_portability.patchedittarget/linux/generic/backport-6.12/202-v6.13-clk-Provide-devm_clk_bulk_get_all_enabled-helper.patchedittarget/linux/generic/pending-6.12/342-powerpc-Enable-kernel-XZ-compression-option-on-PPC_8.patchedittarget/linux/generic/pending-6.12/812-PCI-sysfs-enforce-single-creation-of-sysfs-entry-for.patchedittarget/linux/generic/backport-6.12/503-02-v7.3-ksmbd-keep-tcp-timers-alive-for-kernel-sockets.patchedittarget/linux/generic/backport-6.12/720-05-v6.13-net-phy-mediatek-Move-LED-helper-functions-into-mtk-.patchedittarget/linux/generic/kernel-6.12edittarget/linux/generic/pending-6.12/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patchedittarget/linux/generic/pending-6.12/739-05-net-pcs-add-driver-for-MediaTek-USXGMII-PCS.patchedittarget/linux/generic/backport-6.12/501-v6.19-ksmbd-server-avoid-busy-polling-in-accept-loop.patchedittarget/linux/generic/pending-6.12/790-bus-mhi-core-add-SBL-state-callback.patchedittarget/linux/generic/backport-6.12/504-v7.3-ksmbd-fix-listener-task-lifetime-on-netdev-events.patchedittarget/linux/generic/backport-6.12/502-v7.3-smb-server-fix-signing-multi-iov-response.patchedittarget/linux/generic/backport-6.12/720-04-v6.13-net-phy-mediatek-Re-organize-MediaTek-ethernet-phy-d.patchedittarget/linux/generic/pending-6.12/510-block-add-uImage.FIT-subimage-block-driver.patchdeletetarget/linux/generic/backport-6.12/201-v6.13-of-property-add-of_graph_get_next_port.patchedittarget/linux/generic/backport-6.12/700-01-v7.0-net-sched-Export-mq-functions-for-reuse.patchedittarget/linux/generic/hack-6.12/660-fq_codel_defaults.patch
- target/linux/generic/config-6.18target/linux/generic/config-6.12252773a268140cd85263ec304d4833e698da07971790550358000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: generic: remove kconfig symbol ARCH_HAS_PTDUMP
This is a CPU architecture specific feature. It will be automatically
selected if CPU support it, and we should not enable it globally.
It is worth noting that in the 6.18 kernel, GENERIC_PTDUMP has already
been renamed[1], but we did not add the new symbol ARCH_HAS_PTDUMP, so
we simply drop GENERIC_PTDUMP.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9aad622006bd64c28fdf73c03a1c5139fcbf049
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/25179
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-28 01:05:58 +0200252773a268140cd85263ec304d4833e698da0797kernel: generic: remove kconfig symbol ARCH_HAS_PTDUMPedittarget/linux/generic/config-6.12edittarget/linux/generic/config-6.18
- target/linux/generic/hack-6.12/711-net-dsa-mv88e6xxx-disable-ATU-violation.patchtarget/linux/generic/hack-6.12/755-net-phy-motorcomm-yt8821-bus-collision-workaround.patchtarget/linux/generic/pending-6.12/681-net-remove-NETIF_F_GSO_FRAGLIST-from-NETIF_F_GSO_SOF.patchtarget/linux/generic/pending-6.12/655-increase_skb_pad.patchtarget/linux/generic/pending-6.12/812-PCI-sysfs-enforce-single-creation-of-sysfs-entry-for.patchtarget/linux/generic/backport-6.12/720-10-v6.15-net-phy-mediatek-Change-to-more-meaningful-macros.patchtarget/linux/generic/backport-6.12/720-07-v6.13-net-phy-mediatek-Integrate-read-write-page-helper-fu.patchtarget/linux/generic/backport-6.12/720-09-v6.14-net-phy-Constify-struct-mdio_device_id.patchtarget/linux/generic/backport-6.12/502-v7.3-smb-server-fix-signing-multi-iov-response.patchtarget/linux/generic/pending-6.12/630-packet_socket_type.patchtarget/linux/generic/backport-6.12/720-04-v6.13-net-phy-mediatek-Re-organize-MediaTek-ethernet-phy-d.patchtarget/linux/generic/hack-6.12/766-net-phy-mediatek-ge-add-LED-configuration-interface.patchtarget/linux/generic/pending-6.12/710-bridge-add-knob-for-filtering-rx-tx-BPDU-pack.patchtarget/linux/generic/pending-6.12/750-net-sfp-add-quirk-for-QINIYEK-BJ-SFP-10G-T-copper-SF.patchtarget/linux/generic/pending-6.12/670-ipv6-allow-rejecting-with-source-address-failed-policy.patchtarget/linux/generic/pending-6.12/834-ledtrig-libata.patchtarget/linux/generic/hack-6.12/204-module_strip.patchtarget/linux/generic/hack-6.12/930-Revert-Revert-Revert-driver-core-Set-fw_devlink-on-b.patchtarget/linux/generic/backport-6.12/720-03-v6.13-net-phy-mediatek-ge-soc-Propagate-error-code-correct.patchtarget/linux/generic/hack-6.12/902-debloat_proc.patchtarget/linux/generic/backport-6.12/720-01-v6.13-net-phy-mediatek-ge-soc-Fix-coding-style.patchtarget/linux/generic/backport-6.12/740-v6.13-net-dsa-mv88e6xxx-Support-LED-control.patchtarget/linux/generic/backport-6.12/751-v7.2-net-dsa-qca8k-add-support-for-force-mode-for-fixed-l.patchtarget/linux/generic/backport-6.12/626-16b-v6.17-regulator-Add-support-for-power-budget.patchtarget/linux/generic/backport-6.12/720-08-v6.13-net-phy-mediatek-add-MT7530-MT7531-s-PHY-ID-macros.patchtarget/linux/generic/kernel-6.12target/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchtarget/linux/generic/backport-6.12/720-02-v6.13-net-phy-mediatek-ge-soc-Shrink-line-wrapping-to-80-c.patchtarget/linux/generic/backport-6.12/730-03-v6.13-net-phy-support-active-high-property-for-PHY-LEDs.patchtarget/linux/generic/backport-6.12/800-v6.13-hwmon-Add-static-visibility-member-to-struct-hwmon_o.patchtarget/linux/generic/backport-6.12/941-v7.2-net-dsa-realtek-rtl8365mb-add-support-for-rtl8367sb.patchtarget/linux/generic/backport-6.12/626-09-v6.13-net-pse-pd-Clean-ethtool-header-of-PSE-structures.patchtarget/linux/generic/backport-6.12/741-v6.13-net-dsa-mv88e6xxx-fix-unreleased-fwnode_handle-in-se.patch939a6efb1bfc646454d50433f5fb36ea9f4c5eb01790550358000https://taiha.net/jenkins/user/haukehaukehauke@hauke-m.dekernel: bump 6.12 to 6.12.111
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.111
Upstream merged patches:
- generic/backport-6.12/720-04-v6.13-net-phy-mediatek-Re-organize-MediaTek-ethernet-phy-d.patch[1]
- generic/backport-6.12/751-v7.2-net-dsa-qca8k-add-support-for-force-mode-for-fixed-l.patch[2]
- generic/backport-6.12/941-v7.2-net-dsa-realtek-rtl8365mb-add-support-for-rtl8367sb.patch[3]
All other patches are automatically refreshed.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eceb15fbc345b2e9cc1c1aa94baec2af828f6bfc
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d256b5b49066afdfbf854d866e91d0fdbf7285b
[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9baa7b30dff52e7c0bfa441adf69213410eb932c
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/25179
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-09-28 01:05:58 +0200939a6efb1bfc646454d50433f5fb36ea9f4c5eb0kernel: bump 6.12 to 6.12.111edittarget/linux/generic/backport-6.12/720-10-v6.15-net-phy-mediatek-Change-to-more-meaningful-macros.patchedittarget/linux/generic/backport-6.12/720-03-v6.13-net-phy-mediatek-ge-soc-Propagate-error-code-correct.patchedittarget/linux/generic/hack-6.12/711-net-dsa-mv88e6xxx-disable-ATU-violation.patchdeletetarget/linux/generic/backport-6.12/720-04-v6.13-net-phy-mediatek-Re-organize-MediaTek-ethernet-phy-d.patchedittarget/linux/generic/backport-6.12/720-08-v6.13-net-phy-mediatek-add-MT7530-MT7531-s-PHY-ID-macros.patchedittarget/linux/generic/hack-6.12/766-net-phy-mediatek-ge-add-LED-configuration-interface.patchedittarget/linux/generic/backport-6.12/800-v6.13-hwmon-Add-static-visibility-member-to-struct-hwmon_o.patchedittarget/linux/generic/backport-6.12/720-07-v6.13-net-phy-mediatek-Integrate-read-write-page-helper-fu.patchdeletetarget/linux/generic/backport-6.12/751-v7.2-net-dsa-qca8k-add-support-for-force-mode-for-fixed-l.patchedittarget/linux/generic/hack-6.12/902-debloat_proc.patchedittarget/linux/generic/hack-6.12/930-Revert-Revert-Revert-driver-core-Set-fw_devlink-on-b.patchedittarget/linux/generic/pending-6.12/681-net-remove-NETIF_F_GSO_FRAGLIST-from-NETIF_F_GSO_SOF.patchedittarget/linux/generic/backport-6.12/720-01-v6.13-net-phy-mediatek-ge-soc-Fix-coding-style.patchedittarget/linux/generic/backport-6.12/720-09-v6.14-net-phy-Constify-struct-mdio_device_id.patchedittarget/linux/generic/hack-6.12/755-net-phy-motorcomm-yt8821-bus-collision-workaround.patchedittarget/linux/generic/backport-6.12/730-03-v6.13-net-phy-support-active-high-property-for-PHY-LEDs.patchedittarget/linux/generic/pending-6.12/630-packet_socket_type.patchedittarget/linux/generic/backport-6.12/626-09-v6.13-net-pse-pd-Clean-ethtool-header-of-PSE-structures.patchedittarget/linux/generic/backport-6.12/741-v6.13-net-dsa-mv88e6xxx-fix-unreleased-fwnode_handle-in-se.patchedittarget/linux/generic/kernel-6.12edittarget/linux/generic/pending-6.12/670-ipv6-allow-rejecting-with-source-address-failed-policy.patchedittarget/linux/generic/backport-6.12/626-16b-v6.17-regulator-Add-support-for-power-budget.patchedittarget/linux/generic/backport-6.12/502-v7.3-smb-server-fix-signing-multi-iov-response.patchedittarget/linux/generic/backport-6.12/740-v6.13-net-dsa-mv88e6xxx-Support-LED-control.patchedittarget/linux/generic/pending-6.12/710-bridge-add-knob-for-filtering-rx-tx-BPDU-pack.patchedittarget/linux/generic/hack-6.12/204-module_strip.patchedittarget/linux/generic/pending-6.12/834-ledtrig-libata.patchedittarget/linux/generic/pending-6.12/750-net-sfp-add-quirk-for-QINIYEK-BJ-SFP-10G-T-copper-SF.patchedittarget/linux/generic/pending-6.12/655-increase_skb_pad.patchedittarget/linux/generic/hack-6.12/721-net-add-packet-mangeling.patchedittarget/linux/generic/pending-6.12/812-PCI-sysfs-enforce-single-creation-of-sysfs-entry-for.patchdeletetarget/linux/generic/backport-6.12/941-v7.2-net-dsa-realtek-rtl8365mb-add-support-for-rtl8367sb.patchedittarget/linux/generic/backport-6.12/720-02-v6.13-net-phy-mediatek-ge-soc-Shrink-line-wrapping-to-80-c.patch
githttps://taiha.net/jenkins/user/robimarkorobimarkohttps://taiha.net/jenkins/user/markus.stockhausenmarkus.stockhausenhttps://taiha.net/jenkins/user/haukehaukehttps://taiha.net/jenkins/user/danieldanielhttps://taiha.net/jenkins/user/jonasjonashttps://taiha.net/jenkins/user/mailmail