Started by timer with parameters: {BUILD_CFG_TARGET_DEV=WR8750N/WR9500N/WG600HP (AR9344)}BUILD_CFG_DISTCLEANtrueBUILD_CFG_DIFFCONFIGtrueBUILD_CFG_TARGET_DEVWR8750N/WR9500N/WG600HP (AR9344)4569e43544bc6ecea0e472ee6cc1bdf1e44ff199cdf9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdfrefs/remotes/origin/main9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdf9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdfrefs/remotes/origin/main9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdf9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdfrefs/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)#45620775842107699OpenWrt (master) for NEC Aterm (NetBSD based) #456456falsefalse45621SUCCESS1784158800218https://taiha.net/jenkins/view/all/job/OpenWrt-master-NEC-BSD-Aterm/456/home-slave02_taihasv- target/linux/qualcommax/dts/ipq5018-mx6200.dts5f467dc7dddec92c55e33171f78c77f9e6ee29851783931176000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq50xx: enable in-band-status for MXL GPY115C PHY on Linksys MX6200
The MXL GPY115C PHY requires in-band-status to be set properly detect
link status and communicate phy capabilities. So enable in-band-status
in the Linksys MX6200 device tree.
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24206
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 10:26:16 +02005f467dc7dddec92c55e33171f78c77f9e6ee2985qualcommax: ipq50xx: enable in-band-status for MXL GPY115C PHY on Linksys MX6200edittarget/linux/qualcommax/dts/ipq5018-mx6200.dts
- target/linux/qualcommax/dts/ipq8072-mx5300.dtse8c74e8f1e6deb94fb93a5de53f9198cb79925861783935911000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq8072: assign NVMEM MAC addresses for Linksys MX5300
While the base NVMEM cell (hw_mac_addr) is already defined in the device tree, it was not being utilized by the actual interfaces.
This patch completes the kernel-level MAC assignment by:
1. Correcting the label-mac-device alias to point to the WAN port (&swport5), ensuring the system reports the sticker MAC address correctly.
2. Assigning the base MAC address (offset 0) to the WAN port (&swport5).
3. Assigning the base MAC address (offset 1) to the LAN ports (&swport1 - &swport4).
4. Configuring the proper NVMEM cell references for the PCIe-attached QCA9984 radio (offset 2) and the built-in ATH11K radio (offset 3).
This eliminates the need for post-boot MAC address manipulation and ensures robust, predictable interface initialization.
Signed-off-by: Jackie264 <jackie.han@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24193
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 11:45:11 +0200e8c74e8f1e6deb94fb93a5de53f9198cb7992586qualcommax: ipq8072: assign NVMEM MAC addresses for Linksys MX5300edittarget/linux/qualcommax/dts/ipq8072-mx5300.dts
- target/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.cbf70dd5fb5b3e7b14aaecdfa351f062e335a1e571783938873000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: qca-edma: make RX descriptor endianness explicit
RX descriptor fields use little-endian byte order. Decode the DMA
address and status with the matching helpers before consuming them.
This makes the byte order explicit and keeps the code portable. The
conversions remain no-ops on little-endian IPQ60xx.
Link: https://github.com/openwrt/openwrt/pull/24203
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 12:34:33 +0200bf70dd5fb5b3e7b14aaecdfa351f062e335a1e57qualcommax: qca-edma: make RX descriptor endianness explicitedittarget/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.c
- target/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.cd2d1107057f68f035cc6b723feeedde13d7134291783938873000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: qca-edma: rate-limit malformed RX warnings
A malformed RX preheader can occur repeatedly after the descriptor ring
overruns. Rate-limit the warning to prevent excessive console output
from making the receive stall worse.
Decode the little-endian preheader metadata before printing it and use
consistent hexadecimal formatting.
Link: https://github.com/openwrt/openwrt/pull/24203
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 12:34:33 +0200d2d1107057f68f035cc6b723feeedde13d713429qualcommax: qca-edma: rate-limit malformed RX warningsedittarget/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.c
- target/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.c98108710b65b07e2b2bb4c0e0727b9830709493b1783938873000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: qca-edma: enable threaded NAPI by default
Run the EDMA RX and TX NAPI poll loops in dedicated kernel threads by
default. This allows the threads and their interrupts to be placed on
separate CPUs and avoids overloading a single softirq context.
If thread creation fails, dev_set_threaded() leaves NAPI in softirq mode
and the driver reports the failure.
Link: https://github.com/openwrt/openwrt/pull/24203
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 12:34:33 +020098108710b65b07e2b2bb4c0e0727b9830709493bqualcommax: qca-edma: enable threaded NAPI by defaultedittarget/linux/qualcommax/files/drivers/net/ethernet/qualcomm/qca_edma.c
- target/linux/qualcommax/ipq807x/base-files/etc/init.d/smp_affinitytarget/linux/qualcommax/ipq60xx/base-files/etc/init.d/smp_affinitytarget/linux/qualcommax/ipq60xx/base-files/etc/uci-defaults/15_smp_affinity305c7599e5fa400cf6221fd0a596dbd0145292351783938873000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: pin EDMA processing to dedicated CPUs
IPQ60xx and IPQ807x use threaded NAPI for EDMA. The NAPI threads
inherit CPU0 affinity, and running both there can eventually starve the
RX fill ring under sustained traffic.
Add an IPQ60xx smp_affinity service and extend the existing IPQ807x
service to discover the EDMA IRQs and NAPI IDs at runtime. Place RX on
CPU1 and TX on CPU2. Retry EDMA setup asynchronously because its NAPI
threads may appear after the init service runs.
Provide the same UCI enable and logging controls on both subtargets.
IPQ50xx uses a different Ethernet driver and is left unchanged.
Link: https://github.com/openwrt/openwrt/pull/24203
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-13 12:34:33 +0200305c7599e5fa400cf6221fd0a596dbd014529235qualcommax: pin EDMA processing to dedicated CPUsedittarget/linux/qualcommax/ipq807x/base-files/etc/init.d/smp_affinityaddtarget/linux/qualcommax/ipq60xx/base-files/etc/init.d/smp_affinityaddtarget/linux/qualcommax/ipq60xx/base-files/etc/uci-defaults/15_smp_affinity
- package/boot/uboot-mediatek/patches/220-cmd-env-readmem.patchpackage/boot/uboot-mediatek/patches/470-add-bpi-r4-lite.patchpackage/boot/uboot-mediatek/patches/100-11-env-add-support-for-NMBM-upper-MTD-layer.patchpackage/boot/uboot-mediatek/patches/008-scripts-Makefile.lib-drop-Wno-graph_child_address.patchpackage/boot/uboot-mediatek/patches/457-initialized-the-watchdog-subsystem-later.patchpackage/boot/uboot-mediatek/patches/100-25-env-ubi-add-support-to-create-environment-volume-if-.patchpackage/boot/uboot-mediatek/patches/005-scripts-dtc-drop-yaml-in-DT-validation.patchpackage/boot/uboot-mediatek/patches/100-17-board-mt7981-add-reference-board-using-new-spi-nand-.patchpackage/boot/uboot-mediatek/patches/100-10-cmd-add-a-new-command-for-NAND-flash-debugging.patchpackage/boot/uboot-mediatek/patches/103-01-mt7622-enable-pstore.patchpackage/boot/uboot-mediatek/patches/191-mediatek-mt7622-add-RNG-node.patchpackage/boot/uboot-mediatek/patches/107-configs-add-useful-options-to-mt7981-rfb.patchpackage/boot/uboot-mediatek/patches/500-adapt-mt7987-rfb.patchpackage/boot/uboot-mediatek/patches/408-arm-mediatek-add-back-mt7622-LK-image-header.patchpackage/boot/uboot-mediatek/patches/200-cmd-add-imsz-and-imszb.patchpackage/boot/uboot-mediatek/patches/467-add-routerich-be7200.patchpackage/boot/uboot-mediatek/patches/110-pinctrl-mediatek-MT7981-some-register-map-fixes.patchpackage/boot/uboot-mediatek/patches/007-ARM-dts-build-DT-for-MT7987-RFB.patchpackage/boot/uboot-mediatek/Makefilepackage/boot/uboot-mediatek/patches/401-update-u7623-defconfig.patchpackage/boot/uboot-mediatek/patches/100-18-mtd-spi-nor-add-more-flash-ids.patchpackage/boot/uboot-mediatek/patches/100-07-cmd-add-nmbm-command.patchpackage/boot/uboot-mediatek/patches/100-06-common-board_r-add-support-to-initialize-NMBM-after-.patchpackage/boot/uboot-mediatek/patches/312-mt7622-select-rootdisk.patchpackage/boot/uboot-mediatek/patches/105-configs-add-usefull-stuff-to-mt7988-rfb.patchpackage/boot/uboot-mediatek/patches/002-pinctrl-mediatek-set-MT798x-rev-as-MTK_PINCTRL_V1.patchpackage/boot/uboot-mediatek/patches/100-12-mtd-spi-nor-add-support-to-read-flash-unique-ID.patchpackage/boot/uboot-mediatek/patches/100-22-mmc-mtk-sd-add-support-to-display-verbose-error-log.patchpackage/boot/uboot-mediatek/patches/452-add-xiaomi-redmi-ax6s.patchpackage/boot/uboot-mediatek/patches/121-arm-dts-mediatek-exclude-some-unnecessary-dtbs-from-.patchpackage/boot/uboot-mediatek/patches/211-cmd-bootmenu-custom-title.patchpackage/boot/uboot-mediatek/patches/129-board-mediatek-wire-up-NMBM-support.patchpackage/boot/uboot-mediatek/patches/006-mips-mtmips-align-MT7621-image-blobs-to-8-byte-bound.patchpackage/boot/uboot-mediatek/patches/120-use-xz-instead-of-lzma.patchpackage/boot/uboot-mediatek/patches/100-16-board-mt7622-use-new-spi-nand-driver.patchpackage/boot/uboot-mediatek/patches/410-add-linksys-e8450.patchpackage/boot/uboot-mediatek/patches/412-add-ubnt-unifi-6-lr.patchpackage/boot/uboot-mediatek/patches/301-mt7622-generic-reset-button-ignore-env.patchpackage/boot/uboot-mediatek/patches/400-update-bpir2-defconfig.patchb496e07d0f529804a4c4607284e263c6966a5b4b1783965078000https://taiha.net/jenkins/user/danieldanieldaniel@makrotopia.orguboot-mediatek: update to v2026.07
Remove upstreamed patches:
- 002-pinctrl-mediatek-set-MT798x-rev-as-MTK_PINCTRL_V1.patch[1]
- 005-scripts-dtc-drop-yaml-in-DT-validation.patch[2]
- 006-mips-mtmips-align-MT7621-image-blobs-to-8-byte-bound.patch[3]
- 110-pinctrl-mediatek-MT7981-some-register-map-fixes.patch[4]
[1] https://github.com/u-boot/u-boot/commit/b681f2be8cc81de83fdd4c56cdb35755ca0409eb
[2] https://github.com/u-boot/u-boot/commit/8ef8dee4f3a2b2021decfefd853dbd2a1632b77f
[3] https://github.com/u-boot/u-boot/commit/de79075f0f6b8795d1f9e30ff36435583b1a119a
[4] https://github.com/u-boot/u-boot/commit/5576522219d40ffeb7918dd04263f5d925df9d1d
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
2026-07-13 18:51:18 +0100b496e07d0f529804a4c4607284e263c6966a5b4buboot-mediatek: update to v2026.07editpackage/boot/uboot-mediatek/patches/100-11-env-add-support-for-NMBM-upper-MTD-layer.patcheditpackage/boot/uboot-mediatek/patches/457-initialized-the-watchdog-subsystem-later.patcheditpackage/boot/uboot-mediatek/patches/100-12-mtd-spi-nor-add-support-to-read-flash-unique-ID.patcheditpackage/boot/uboot-mediatek/patches/401-update-u7623-defconfig.patcheditpackage/boot/uboot-mediatek/patches/312-mt7622-select-rootdisk.patcheditpackage/boot/uboot-mediatek/patches/100-25-env-ubi-add-support-to-create-environment-volume-if-.patcheditpackage/boot/uboot-mediatek/patches/007-ARM-dts-build-DT-for-MT7987-RFB.patcheditpackage/boot/uboot-mediatek/patches/220-cmd-env-readmem.patcheditpackage/boot/uboot-mediatek/patches/191-mediatek-mt7622-add-RNG-node.patcheditpackage/boot/uboot-mediatek/patches/410-add-linksys-e8450.patcheditpackage/boot/uboot-mediatek/patches/103-01-mt7622-enable-pstore.patcheditpackage/boot/uboot-mediatek/patches/120-use-xz-instead-of-lzma.patcheditpackage/boot/uboot-mediatek/patches/100-16-board-mt7622-use-new-spi-nand-driver.patcheditpackage/boot/uboot-mediatek/patches/100-07-cmd-add-nmbm-command.patcheditpackage/boot/uboot-mediatek/patches/100-18-mtd-spi-nor-add-more-flash-ids.patcheditpackage/boot/uboot-mediatek/patches/129-board-mediatek-wire-up-NMBM-support.patcheditpackage/boot/uboot-mediatek/patches/412-add-ubnt-unifi-6-lr.patcheditpackage/boot/uboot-mediatek/patches/100-22-mmc-mtk-sd-add-support-to-display-verbose-error-log.patcheditpackage/boot/uboot-mediatek/patches/105-configs-add-usefull-stuff-to-mt7988-rfb.patcheditpackage/boot/uboot-mediatek/patches/211-cmd-bootmenu-custom-title.patchdeletepackage/boot/uboot-mediatek/patches/005-scripts-dtc-drop-yaml-in-DT-validation.patcheditpackage/boot/uboot-mediatek/patches/467-add-routerich-be7200.patcheditpackage/boot/uboot-mediatek/patches/301-mt7622-generic-reset-button-ignore-env.patchaddpackage/boot/uboot-mediatek/patches/008-scripts-Makefile.lib-drop-Wno-graph_child_address.patcheditpackage/boot/uboot-mediatek/patches/100-17-board-mt7981-add-reference-board-using-new-spi-nand-.patchdeletepackage/boot/uboot-mediatek/patches/002-pinctrl-mediatek-set-MT798x-rev-as-MTK_PINCTRL_V1.patchaddpackage/boot/uboot-mediatek/patches/121-arm-dts-mediatek-exclude-some-unnecessary-dtbs-from-.patchdeletepackage/boot/uboot-mediatek/patches/006-mips-mtmips-align-MT7621-image-blobs-to-8-byte-bound.patcheditpackage/boot/uboot-mediatek/patches/100-06-common-board_r-add-support-to-initialize-NMBM-after-.patcheditpackage/boot/uboot-mediatek/Makefileeditpackage/boot/uboot-mediatek/patches/107-configs-add-useful-options-to-mt7981-rfb.patcheditpackage/boot/uboot-mediatek/patches/500-adapt-mt7987-rfb.patcheditpackage/boot/uboot-mediatek/patches/452-add-xiaomi-redmi-ax6s.patcheditpackage/boot/uboot-mediatek/patches/200-cmd-add-imsz-and-imszb.patcheditpackage/boot/uboot-mediatek/patches/100-10-cmd-add-a-new-command-for-NAND-flash-debugging.patcheditpackage/boot/uboot-mediatek/patches/400-update-bpir2-defconfig.patcheditpackage/boot/uboot-mediatek/patches/408-arm-mediatek-add-back-mt7622-LK-image-header.patcheditpackage/boot/uboot-mediatek/patches/470-add-bpi-r4-lite.patchdeletepackage/boot/uboot-mediatek/patches/110-pinctrl-mediatek-MT7981-some-register-map-fixes.patch
- target/linux/airoha/patches-6.18/609-02-clk-en7523-add-support-for-dedicated-PCIe-PERSTOUT-r.patchtarget/linux/airoha/dts/an7581-nokia-valyrian.dtstarget/linux/airoha/patches-6.18/913-pcie-mediatek-gen3-fix-x2-mode-PERST-deassert.patchtarget/linux/airoha/patches-6.18/609-01-dt-bindings-clock-airoha-Add-additional-reset-for-PC.patchtarget/linux/airoha/patches-6.18/912-pcie-mediatek-gen3-Add-x2-link-support-for-Airoha-EN7581.patchtarget/linux/airoha/dts/an7581-w1700k-ubi.dtstarget/linux/airoha/patches-6.18/609-04-PCI-mediatek-gen3-Add-2-lanes-mode-support-for-Airoh.patchtarget/linux/airoha/patches-6.18/911-clk-en7581-Separate-PERST-from-refclk-in-PCIe-clock.patchtarget/linux/airoha/dts/an7581.dtsitarget/linux/airoha/patches-6.18/913-clk-en7523-reset-PCIE-HB-on-init.patch7d56183d903f3cbe549fa89a4f857b4fee1d97b61784032066000https://taiha.net/jenkins/user/ansuelsmthansuelsmthansuelsmth@gmail.comairoha: replace PCIe x2-mode patch with new pending version
The current x2-mode patch is mostly an hack ported from Airoha SDK. Replace
with in favor of a new version posted upstream that better implement
handling of reset and configuring x2-mode. This now use the standard
num-lanes property and dedicated PERSTOUT resets exported by the clk
driver.
All the DTS that used x2-mode are updated.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
2026-07-14 14:27:46 +02007d56183d903f3cbe549fa89a4f857b4fee1d97b6airoha: replace PCIe x2-mode patch with new pending versionedittarget/linux/airoha/dts/an7581.dtsiaddtarget/linux/airoha/patches-6.18/609-02-clk-en7523-add-support-for-dedicated-PCIe-PERSTOUT-r.patchdeletetarget/linux/airoha/patches-6.18/912-pcie-mediatek-gen3-Add-x2-link-support-for-Airoha-EN7581.patchedittarget/linux/airoha/dts/an7581-w1700k-ubi.dtsdeletetarget/linux/airoha/patches-6.18/911-clk-en7581-Separate-PERST-from-refclk-in-PCIe-clock.patchaddtarget/linux/airoha/patches-6.18/913-clk-en7523-reset-PCIE-HB-on-init.patchdeletetarget/linux/airoha/patches-6.18/913-pcie-mediatek-gen3-fix-x2-mode-PERST-deassert.patchedittarget/linux/airoha/dts/an7581-nokia-valyrian.dtsaddtarget/linux/airoha/patches-6.18/609-01-dt-bindings-clock-airoha-Add-additional-reset-for-PC.patchaddtarget/linux/airoha/patches-6.18/609-04-PCI-mediatek-gen3-Add-2-lanes-mode-support-for-Airoh.patch
- target/linux/airoha/dts/an7581-w1700k-ubi.dtstarget/linux/airoha/dts/an7581-nokia-valyrian.dts665cfa98de1aa02b31436621a063969aba322a181784032909000https://taiha.net/jenkins/user/ansuelsmthansuelsmthansuelsmth@gmail.comairoha: add missing SCU phandle for PCIe 2-lanes mode
The SCU phandle is mandatory to configure PCIe MUX when PCIe 2-lanes mode
is enabled.
Add the missing property where needed.
Fixes: 7d56183d903f ("airoha: replace PCIe x2-mode patch with new pending version")
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
2026-07-14 14:41:49 +0200665cfa98de1aa02b31436621a063969aba322a18airoha: add missing SCU phandle for PCIe 2-lanes modeedittarget/linux/airoha/dts/an7581-w1700k-ubi.dtsedittarget/linux/airoha/dts/an7581-nokia-valyrian.dts
- target/linux/airoha/dts/an7581-evb-emmc-eagle.dts4fa33a07247e519b258d45bae80e5d05f7999f3b1784033053000https://taiha.net/jenkins/user/ansuelsmthansuelsmthansuelsmth@gmail.comairoha: configure PCIe 2-lanes mode for eMMC EAGLE RFB board
The EAGLE PCIe WiFi card require PCIe0 to be in 2-lanes mode to correctly
work. Add the missing property to enable this mode and restore correctly
functionality of the WiFi card.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
2026-07-14 14:44:13 +02004fa33a07247e519b258d45bae80e5d05f7999f3bairoha: configure PCIe 2-lanes mode for eMMC EAGLE RFB boardedittarget/linux/airoha/dts/an7581-evb-emmc-eagle.dts
- package/libs/mbedtls/patches/102-fix-arm32-build-error-against-GCC-15.3.patch0745de60f4172a04f32c42021ad509aea591b7dd1784062247000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commbedtls: fix arm32 build errors with GCC 15.3
It seems that GCC 15.3 has added additional OOB checks for ARCH arm32.
Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/23774
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 22:50:47 +02000745de60f4172a04f32c42021ad509aea591b7ddmbedtls: fix arm32 build errors with GCC 15.3addpackage/libs/mbedtls/patches/102-fix-arm32-build-error-against-GCC-15.3.patch
- target/linux/lantiq/files/arch/mips/pci/ifxmips_pcie.htarget/linux/lantiq/patches-6.18/001-MIPS-lantiq-add-pcie-driver.patchtarget/linux/lantiq/files/arch/mips/pci/fixup-lantiq-pcie.ctarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_msi.ctarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_ar10.htarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_vr9.htarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_pm.htarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie.ctarget/linux/lantiq/files/arch/mips/pci/pcie-lantiq.htarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_pm.ctarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_reg.htarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_phy.ctarget/linux/lantiq/patches-6.18/151-lantiq-ifxmips_pcie-use-of.patchtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pci_common.htarget/linux/lantiq/patches-6.12/151-lantiq-ifxmips_pcie-use-of.patchtarget/linux/lantiq/patches-6.12/001-MIPS-lantiq-add-pcie-driver.patchc8839a94d730f2118279ea3f424e6f706ae8bbfd1784064212000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comlantiq: move pcie driver from patch to files
This driver is quite huge and local only. Never seems to have been
submitted upstream.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24190
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:23:32 +0200c8839a94d730f2118279ea3f424e6f706ae8bbfdlantiq: move pcie driver from patch to filesdeletetarget/linux/lantiq/patches-6.18/151-lantiq-ifxmips_pcie-use-of.patchaddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pci_common.haddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_vr9.hedittarget/linux/lantiq/patches-6.12/001-MIPS-lantiq-add-pcie-driver.patchaddtarget/linux/lantiq/files/arch/mips/pci/fixup-lantiq-pcie.caddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie.haddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_msi.caddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_phy.caddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_reg.haddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie.caddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_ar10.haddtarget/linux/lantiq/files/arch/mips/pci/pcie-lantiq.hdeletetarget/linux/lantiq/patches-6.12/151-lantiq-ifxmips_pcie-use-of.patchaddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_pm.caddtarget/linux/lantiq/files/arch/mips/pci/ifxmips_pcie_pm.hedittarget/linux/lantiq/patches-6.18/001-MIPS-lantiq-add-pcie-driver.patch
- package/network/services/dropbear/patches/100-pubkey_path.patchpackage/network/services/dropbear/patches/003-Fix-too-low-pubkey-key-query-count.patchpackage/network/services/dropbear/patches/140-disable_assert.patchpackage/network/services/dropbear/patches/001-sntrup-Fix-64-bit-literals.patchpackage/network/services/dropbear/Makefilepackage/network/services/dropbear/patches/001-avoid-out-of-bounds-read-matching-ecdsa-curve-identi.patchpackage/network/services/dropbear/patches/002-Increase-MAX_HOSTKEYS-to-6.patch49096a9c4867d3f37fd4d98b283331a30d264aaf1784065062000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comdropbear: bump to 2026.92
- update dropbear to latest stable 2026.92;
for the changes see https://matt.ucc.asn.au/dropbear/CHANGES
- remove previously cherry-picked patches
- cherry-pick upstream patches:
- avoid out-of-bounds read matching ecdsa curve identifier
- automatically refresh patches
Signed-off-by: Konstantin Demin <rockdrilla@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24113
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:37:42 +020049096a9c4867d3f37fd4d98b283331a30d264aafdropbear: bump to 2026.92editpackage/network/services/dropbear/Makefileeditpackage/network/services/dropbear/patches/100-pubkey_path.patchdeletepackage/network/services/dropbear/patches/001-sntrup-Fix-64-bit-literals.patcheditpackage/network/services/dropbear/patches/140-disable_assert.patchdeletepackage/network/services/dropbear/patches/002-Increase-MAX_HOSTKEYS-to-6.patchdeletepackage/network/services/dropbear/patches/003-Fix-too-low-pubkey-key-query-count.patchaddpackage/network/services/dropbear/patches/001-avoid-out-of-bounds-read-matching-ecdsa-curve-identi.patch
- target/linux/airoha/patches-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchtarget/linux/generic/pending-6.18/896-01-net-pse-pd-add-notifier-chain-for-controller-lifecyc.patchtarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patchtarget/linux/generic/pending-6.18/896-02-net-pse-pd-fire-lifecycle-events-on-controller-regis.patchtarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchtarget/linux/generic/backport-6.18/627-v7.2-net-pse-pd-scope-pse_control-regulator-handle-to-kre.patch96ecf8dd248cbdd4bcabcc198f9170abda1ab0ea1784065529000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comgeneric: pse-pd: add patches for module-based PSE drivers
Add a backport patch and pending patches needed by upcoming PSE drivers
which are built as modules and probed after the MAC/PHY.
The net effect for module-built PSE controllers: attachment to PHYs
happens via the lifecycle notifier rather than via probe-time
-EPROBE_DEFER coupling, so the MDIO/DSA probe no longer sees any
PSE-originated -EPROBE_DEFER and the probe-retry storm is gone.
Link: https://github.com/openwrt/openwrt/pull/23222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:45:29 +020096ecf8dd248cbdd4bcabcc198f9170abda1ab0eageneric: pse-pd: add patches for module-based PSE driversedittarget/linux/airoha/patches-6.18/801-01-net-phy-add-PHY_DETACH_NO_HW_RESET-PHY-flag.patchaddtarget/linux/generic/pending-6.18/896-02-net-pse-pd-fire-lifecycle-events-on-controller-regis.patchaddtarget/linux/generic/backport-6.18/627-v7.2-net-pse-pd-scope-pse_control-regulator-handle-to-kre.patchaddtarget/linux/generic/pending-6.18/896-01-net-pse-pd-add-notifier-chain-for-controller-lifecyc.patchedittarget/linux/ramips/patches-6.18/720-NET-no-auto-carrier-off-support.patchaddtarget/linux/generic/pending-6.18/896-03-net-phy-own-phydev-psec-via-PSE-notifier-and-remove-.patch
- target/linux/realtek/rtl930x/config-6.18target/linux/realtek/rtl930x_nand/config-6.18target/linux/realtek/rtl931x/config-6.18target/linux/realtek/rtl838x/config-6.18target/linux/realtek/patches-6.18/816-02-net-pse-pd-realtek-pse-mcu-add-I2C-transport.patchtarget/linux/realtek/rtl839x/config-6.18target/linux/realtek/patches-6.18/816-03-net-pse-pd-realtek-pse-mcu-add-UART-transport.patchtarget/linux/realtek/rtl931x_nand/config-6.18target/linux/realtek/patches-6.18/816-01-net-pse-pd-add-Realtek-Broadcom-PSE-MCU-core.patchpackage/kernel/linux/modules/pse-pd.mk301d98f81fa7baedcb172f7d47c05b12770302a51784065529000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: add Realtek PSE MCU driver
Add pending patches which add a PSE driver for the PSE setup found on
most of Realtek-based switches. An MCU with a Realtek-defined firmware
and protocol fronts one or more PSE chips (from Realtek or Broadcom) as
a management controller.
The driver provides both I2C/SMBus and UART communication, which varies
among our supported switches. There is no need for complicated userspace
handling anymore, the PSE setup is defined in the device tree and
interfaced in userspace via ethtool, netlink and netifd support.
Those patches have progressed far enough upstream, the bindings are
reviewed. Thus, we can keep this intermediate version downstream to open
it up earlier for usage. Only little changes are expected til the final
version lands.
Link: https://github.com/openwrt/openwrt/pull/23222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:45:29 +0200301d98f81fa7baedcb172f7d47c05b12770302a5realtek: add Realtek PSE MCU driveredittarget/linux/realtek/rtl930x/config-6.18edittarget/linux/realtek/rtl838x/config-6.18edittarget/linux/realtek/rtl839x/config-6.18edittarget/linux/realtek/rtl931x_nand/config-6.18addtarget/linux/realtek/patches-6.18/816-02-net-pse-pd-realtek-pse-mcu-add-I2C-transport.patchaddtarget/linux/realtek/patches-6.18/816-03-net-pse-pd-realtek-pse-mcu-add-UART-transport.patchedittarget/linux/realtek/rtl930x_nand/config-6.18editpackage/kernel/linux/modules/pse-pd.mkaddtarget/linux/realtek/patches-6.18/816-01-net-pse-pd-add-Realtek-Broadcom-PSE-MCU-core.patchedittarget/linux/realtek/rtl931x/config-6.18
- target/linux/realtek/patches-6.18/817-net-pse-pd-realtek-pse-mcu-add-per-por-legacy-detec.patch184f70a44d9eec8633dd4e2fe0aa307e6368f0931784065529000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pse: add patch for sysfs detection control
Add a patch which modifies the Realtek PSE MCU driver backport to add a
sysfs control to control detection mode per port. Some older,
bad-designed devices aren't detected properly in standard mode on some
switches, though vendor firmware powers them properly. Testing shows
that enabling the detection of legacy PDs by allowing wider resistance,
more input capacitance and using a wider detection window, solves this
issue.
The legacy detection can be activated by writing 1 to
portN/detection_legacy in the device's sysfs, e.g.
echo 1 > /sys/bus/i2c/devices/3-0020/port0/detection_legacy
This patch is kept downstream for now, upstreaming will be attempted
though it is likely that upstream prefers a generic pse-pd approach.
Link: https://github.com/openwrt/openwrt/pull/23222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:45:29 +0200184f70a44d9eec8633dd4e2fe0aa307e6368f093realtek: pse: add patch for sysfs detection controladdtarget/linux/realtek/patches-6.18/817-net-pse-pd-realtek-pse-mcu-add-per-por-legacy-detec.patch
- target/linux/realtek/image/rtl930x.mktarget/linux/realtek/dts/rtl9302_zyxel_xmg1915-10ep.dtsf57de02350ab6b4b3eb7ca2e6cf8ca036220840e1784065530000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: use realtek-pse-mcu kernel driver for PoE on XMG1915-10EP
Instead of relying on the userspace implementation, make this device the
first user of the new realtek-pse kernel driver (kmod-pse-realtek-mcu-uart)
based on the PSE-PD framework to interface PoE functionality of that
switch. Control of PoE functionality happens via ethtool / netifd now.
Drop selecting realtek-poe for this device.
This doesn't include any support for PoE-related LEDs.
Link: https://github.com/openwrt/openwrt/pull/23222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:45:30 +0200f57de02350ab6b4b3eb7ca2e6cf8ca036220840erealtek: use realtek-pse-mcu kernel driver for PoE on XMG1915-10EPedittarget/linux/realtek/dts/rtl9302_zyxel_xmg1915-10ep.dtsedittarget/linux/realtek/image/rtl930x.mk
- target/linux/realtek/image/rtl931x.mktarget/linux/realtek/dts/rtl9313_zyxel_xs1930-12hp.dtse9aa5bea9f249eadfc5368874efee996643c0efc1784065530000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: add PoE support for XS1930-12HP
Add support for PoE functionality using the realtek-pse-mcu driver
(kmod-pse-realtek-mcu-i2c) interfacing the on-board PoE MCU and RTL8239
PSE chips.
This doesn't include any support for PoE-related LEDs.
Link: https://github.com/openwrt/openwrt/pull/23222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-14 23:45:30 +0200e9aa5bea9f249eadfc5368874efee996643c0efcrealtek: add PoE support for XS1930-12HPedittarget/linux/realtek/image/rtl931x.mkedittarget/linux/realtek/dts/rtl9313_zyxel_xs1930-12hp.dts
- target/linux/qualcommax/patches-6.12/0907-soc-qcom-fix-smp2p-ack-on-ipq6018.patchtarget/linux/qualcommax/patches-6.12/0906-arm64-dts-qcom-ipq6018-add-wifi-node.patchtarget/linux/qualcommax/patches-6.12/0909-arm64-dts-qcom-ipq6018-assign-QDSS_AT-clock-to-wifi-.patchtarget/linux/qualcommax/patches-6.12/0077-v7.2-pwm-Driver-for-qualcomm-ipq6018-pwm-block.patchtarget/linux/qualcommax/patches-6.12/0304-dt-bindings-pwm-add-IPQ5018-compatible.patchtarget/linux/qualcommax/patches-6.12/0138-arm64-dts-qcom-ipq6018-add-pwm-node.patchtarget/linux/qualcommax/patches-6.12/0306-arm64-dts-qcom-ipq5018-Add-PWM-node.patchtarget/linux/qualcommax/patches-6.12/0140-dt-bindings-pwm-add-IPQ6018-binding.patchtarget/linux/qualcommax/patches-6.12/0141-pwm-driver-for-qualcomm-ipq6018-pwm-block.patchtarget/linux/qualcommax/patches-6.12/0076-v7.2-dt-bindings-pwm-add-IPQ6018-binding.patchtarget/linux/qualcommax/patches-6.12/0078-v7.3-arm64-dts-qcom-ipq6018-add-pwm-node.patchtarget/linux/qualcommax/patches-6.12/0189-arm64-dts-qcom-ipq5018-add-nodes-to-bringup-q6.patchtarget/linux/qualcommax/patches-6.12/0079-v7.3-arm64-dts-qcom-ipq5018-add-pwm-node.patch0368dc896a2f66f2a409fbc14b68528467449c231784114784000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: backport upstreamed patches for IPQ PWM support
Backport upstreamed patches for IPQ PWM support and refresh following
patches.
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24238
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-15 13:26:24 +02000368dc896a2f66f2a409fbc14b68528467449c23qualcommax: backport upstreamed patches for IPQ PWM supportaddtarget/linux/qualcommax/patches-6.12/0077-v7.2-pwm-Driver-for-qualcomm-ipq6018-pwm-block.patchaddtarget/linux/qualcommax/patches-6.12/0078-v7.3-arm64-dts-qcom-ipq6018-add-pwm-node.patchedittarget/linux/qualcommax/patches-6.12/0909-arm64-dts-qcom-ipq6018-assign-QDSS_AT-clock-to-wifi-.patchdeletetarget/linux/qualcommax/patches-6.12/0304-dt-bindings-pwm-add-IPQ5018-compatible.patchdeletetarget/linux/qualcommax/patches-6.12/0141-pwm-driver-for-qualcomm-ipq6018-pwm-block.patchdeletetarget/linux/qualcommax/patches-6.12/0306-arm64-dts-qcom-ipq5018-Add-PWM-node.patchaddtarget/linux/qualcommax/patches-6.12/0076-v7.2-dt-bindings-pwm-add-IPQ6018-binding.patchedittarget/linux/qualcommax/patches-6.12/0906-arm64-dts-qcom-ipq6018-add-wifi-node.patchedittarget/linux/qualcommax/patches-6.12/0907-soc-qcom-fix-smp2p-ack-on-ipq6018.patchdeletetarget/linux/qualcommax/patches-6.12/0138-arm64-dts-qcom-ipq6018-add-pwm-node.patchaddtarget/linux/qualcommax/patches-6.12/0079-v7.3-arm64-dts-qcom-ipq5018-add-pwm-node.patchedittarget/linux/qualcommax/patches-6.12/0189-arm64-dts-qcom-ipq5018-add-nodes-to-bringup-q6.patchdeletetarget/linux/qualcommax/patches-6.12/0140-dt-bindings-pwm-add-IPQ6018-binding.patch
- target/linux/qualcommax/patches-6.12/0067-v6.17-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ5018-SoC.patchtarget/linux/qualcommax/patches-6.12/0081-v7.1-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ8074.patchtarget/linux/qualcommax/patches-6.12/0082-v7.1-clk-qcom-ipq-cmn-pll-Add-IPQ6018-SoC-support.patchtarget/linux/qualcommax/patches-6.12/0914-clk-qcom-ipq-cmn-pll-Add-IPQ6018-SoC-support.patchtarget/linux/qualcommax/patches-6.12/0083-v7.1-clk-qcom-ipq-cmn-pll-Add-IPQ8074-SoC-support.patchtarget/linux/qualcommax/patches-6.12/0818-arm64-dts-qcom-ipq5018-fix-assigned-cmn-pll-clock-rate.patchtarget/linux/qualcommax/patches-6.12/0915-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ8074.patchtarget/linux/qualcommax/patches-6.12/0916-clk-qcom-ipq-cmn-pll-Add-IPQ8074-SoC-support.patchtarget/linux/qualcommax/patches-6.12/0080-v7.1-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ6018.patchtarget/linux/qualcommax/patches-6.12/0085-v7.3-arm64-dts-qcom-ipq5018-Correct-CMN-PLL-reference-clock-rate.patchtarget/linux/qualcommax/patches-6.12/0190-clk-qcom-cmnpll-Account-for-reference-clock-divider.patchtarget/linux/qualcommax/patches-6.12/0084-v7.2-clk-qcom-cmnpll-Account-for-reference-clock-divider.patchtarget/linux/qualcommax/patches-6.12/0913-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ6018.patch5ddbbe76703a68d7af048e105a4cf53f8916e4da1784114784000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: backport upstreamed patches for IPQ CMN PLL support
Backport upstreamed patched for IPQ CMN PLL support.
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24238
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-15 13:26:24 +02005ddbbe76703a68d7af048e105a4cf53f8916e4daqualcommax: backport upstreamed patches for IPQ CMN PLL supportaddtarget/linux/qualcommax/patches-6.12/0083-v7.1-clk-qcom-ipq-cmn-pll-Add-IPQ8074-SoC-support.patchdeletetarget/linux/qualcommax/patches-6.12/0818-arm64-dts-qcom-ipq5018-fix-assigned-cmn-pll-clock-rate.patchdeletetarget/linux/qualcommax/patches-6.12/0914-clk-qcom-ipq-cmn-pll-Add-IPQ6018-SoC-support.patchdeletetarget/linux/qualcommax/patches-6.12/0915-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ8074.patchdeletetarget/linux/qualcommax/patches-6.12/0916-clk-qcom-ipq-cmn-pll-Add-IPQ8074-SoC-support.patchdeletetarget/linux/qualcommax/patches-6.12/0190-clk-qcom-cmnpll-Account-for-reference-clock-divider.patchedittarget/linux/qualcommax/patches-6.12/0067-v6.17-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ5018-SoC.patchaddtarget/linux/qualcommax/patches-6.12/0081-v7.1-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ8074.patchaddtarget/linux/qualcommax/patches-6.12/0084-v7.2-clk-qcom-cmnpll-Account-for-reference-clock-divider.patchaddtarget/linux/qualcommax/patches-6.12/0082-v7.1-clk-qcom-ipq-cmn-pll-Add-IPQ6018-SoC-support.patchaddtarget/linux/qualcommax/patches-6.12/0085-v7.3-arm64-dts-qcom-ipq5018-Correct-CMN-PLL-reference-clock-rate.patchaddtarget/linux/qualcommax/patches-6.12/0080-v7.1-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ6018.patchdeletetarget/linux/qualcommax/patches-6.12/0913-dt-bindings-clock-qcom-Add-CMN-PLL-support-for-IPQ6018.patch
- target/linux/qualcommax/patches-6.12/0740-03-arm64-qcom-ipq5018-add-gephy-rx-and-tx-clocks.patchtarget/linux/qualcommax/patches-6.12/0089-v7.2-net-phy-at803x-add-RX-and-TX-clock-management-for-IPQ5018-PHY.patchtarget/linux/qualcommax/patches-6.12/0740-04-net-phy-at803x-add-rx-and-tx-clock-management-for-ipq5018-phy.patchtarget/linux/qualcommax/patches-6.12/0087-v7.2-dt-bindings-net-ethernet-phy-increase-max-clock-count-to-two.patchtarget/linux/qualcommax/patches-6.12/0086-v6.17-dt-bindings-net-qca-ar803x-Add-IPQ5018-Internal-GE-PHY-support.patchtarget/linux/qualcommax/patches-6.12/0189-arm64-dts-qcom-ipq5018-add-nodes-to-bringup-q6.patchtarget/linux/qualcommax/patches-6.12/0740-01-dt-bindings-net-ethernet-phy-increase-max-clock-count-to-two.patchtarget/linux/qualcommax/patches-6.12/0088-v7.2-dt-bindings-net-qca-ar803x-Add-clocks-for-IPQ5018-PHY.patchtarget/linux/qualcommax/patches-6.12/0090-v7.3-arm64-qcom-ipq5018-Add-GEPHY-RX-and-TX-clocks.patchad1de384bf93d44503a13cb3983f35001dd511ef1784114785000https://taiha.net/jenkins/user/robimarkorobimarkorobimarko@gmail.comqualcommax: ipq50xx: backport upstreamed patches for IPQ5018 PHY clocks
Backport upstreamed patches for IPQ5018 PHY RX and TX clocks support.
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
Link: https://github.com/openwrt/openwrt/pull/24238
Signed-off-by: Robert Marko <robimarko@gmail.com>
2026-07-15 13:26:25 +0200ad1de384bf93d44503a13cb3983f35001dd511efqualcommax: ipq50xx: backport upstreamed patches for IPQ5018 PHY clocksedittarget/linux/qualcommax/patches-6.12/0189-arm64-dts-qcom-ipq5018-add-nodes-to-bringup-q6.patchaddtarget/linux/qualcommax/patches-6.12/0088-v7.2-dt-bindings-net-qca-ar803x-Add-clocks-for-IPQ5018-PHY.patchdeletetarget/linux/qualcommax/patches-6.12/0740-01-dt-bindings-net-ethernet-phy-increase-max-clock-count-to-two.patchaddtarget/linux/qualcommax/patches-6.12/0086-v6.17-dt-bindings-net-qca-ar803x-Add-IPQ5018-Internal-GE-PHY-support.patchaddtarget/linux/qualcommax/patches-6.12/0089-v7.2-net-phy-at803x-add-RX-and-TX-clock-management-for-IPQ5018-PHY.patchdeletetarget/linux/qualcommax/patches-6.12/0740-03-arm64-qcom-ipq5018-add-gephy-rx-and-tx-clocks.patchaddtarget/linux/qualcommax/patches-6.12/0087-v7.2-dt-bindings-net-ethernet-phy-increase-max-clock-count-to-two.patchdeletetarget/linux/qualcommax/patches-6.12/0740-04-net-phy-at803x-add-rx-and-tx-clock-management-for-ipq5018-phy.patchaddtarget/linux/qualcommax/patches-6.12/0090-v7.3-arm64-qcom-ipq5018-Add-GEPHY-RX-and-TX-clocks.patch
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c146d0fb6e02b4b37519075531841806d2e8ff87f1784137018000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl93xx: make cmu_page getter generic
Rename rtpcs_931x_sds_cmu_page_get() to rtpcs_93xx_sds_get_cmu_page()
and move it next to the other 93xx-shared helpers, so RTL930X can
reuse it instead of duplicating the same hw_mode-to-CMU-page switch.
Also fix the wrong -ENOTSUPP return to -EOPNOTSUPP.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:36:58 +0200146d0fb6e02b4b37519075531841806d2e8ff87frealtek: pcs: rtl93xx: make cmu_page getter genericedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c8eaa84d2e9b0c9880bb124163eae5fa5a1c8db311784137019000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: use cmu_page getter for tx_config
Derive the CMU page from rtpcs_93xx_sds_get_cmu_page() instead of
hardcoding it per hw_mode case. Also change the function to return
int and propagate errors instead of silently doing nothing.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:36:59 +02008eaa84d2e9b0c9880bb124163eae5fa5a1c8db31realtek: pcs: rtl930x: use cmu_page getter for tx_configedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cbf2c9a5d8b061a60a6fc0ba9361785941a56dace1784137019000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: only apply TX config for 10G SerDes
So far, there was only a misleading and confusing gate to avoid applying
the TX config to SerDes which do not need it or where it even breaks
some modes. This is achieved by not applying any configuration for
QSGMII mode. While this fits the real-world cases we know so far where
QSGMII is only used on SerDes 0/1 but never on others, it implicates
that this is true too for QSGMII on 10G SerDes. Looking at the SDK, this
assumption doesn't hold.
To fix this, drop out of config_media in case a non-10G SerDes is
delivered. The SDK does the same in various ways, ending up with the
config just being applied for SerDes 2 - 9.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:36:59 +0200bf2c9a5d8b061a60a6fc0ba9361785941a56dacerealtek: pcs: rtl930x: only apply TX config for 10G SerDesedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c4212598948459f7e96aed13b491a7a6ab111e9d21784137019000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: classify SGMII as PHY-attached media
SGMII always terminates in a PHY, whether on-board or embedded in an
SFP copper module, so it belongs with QSGMII/XSGMII/USXGMII rather
than the direct fiber/DAC modes. The PHY equalizes on its own far-end
receiver in either case, so no media-dependent TX tuning is needed.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:36:59 +02004212598948459f7e96aed13b491a7a6ab111e9d2realtek: pcs: rtl930x: classify SGMII as PHY-attached mediaedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c5f6896209dc506d38fc98d6b5b3eebc57bdbec7d1784137020000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl93xx: rename MEDIA_PCB to MEDIA_PHY
Every SerDes lane runs over some PCB trace before reaching the port,
even fiber/DAC ones, so PCB doesn't describe what actually
distinguishes this case: the SerDes terminates directly into a PHY
chip rather than a fiber module or DAC cable.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:00 +02005f6896209dc506d38fc98d6b5b3eebc57bdbec7drealtek: pcs: rtl93xx: rename MEDIA_PCB to MEDIA_PHYedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c8d2bd202c4899c6dfbf8037b8ae2c80dabe49cb31784137020000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl93xx: rename media to attachment
"media" doesn't fit well once PHY sits alongside FIBER/DAC_SHORT/
DAC_LONG as a value: a PHY isn't a transmission medium, whereas what
actually matters here is what electrically terminates the SerDes lane
on the other end. Rename the enum, struct field, ops vtable member,
and both variants' config functions accordingly. Calling it 'attachment'
better fits what it actually is, doesn't confuse with the variants and
also fits to the PMA (Physical Medium Attachment) sublayer that lives
below PCS.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:00 +02008d2bd202c4899c6dfbf8037b8ae2c80dabe49cb3realtek: pcs: rtl93xx: rename media to attachmentedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.cf8afbb637befb49009e39f1cd5e7e6693aca6caf1784137020000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl93xx: commit attachment only after successful config
sds->attachment was written right after selection, before
config_attachment() ran, so a failed config call would leave it
reflecting a value that was never actually applied to hardware. Move
the assignment after the call succeeds, matching how sds->hw_mode is
only committed after set_hw_mode() succeeds.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:00 +0200f8afbb637befb49009e39f1cd5e7e6693aca6cafrealtek: pcs: rtl93xx: commit attachment only after successful configedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c629c5c8b11d5a2cb88a8b7b185ecd9851bdbdbbd1784137021000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: refactor TX config
Replace the on-stack, hardcoded pre/main/post-amp locals with static
const rtpcs_sds_tx_config data, one struct per speed class (1g, 2g5,
10g), instead of duplicating the same literals inline on every call.
Move the decision logic about which values are applied to the
config_media function. The tx_config should only be about what is set,
decision logic is handled one layer above. This also prepares further
refactoring.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:01 +0200629c5c8b11d5a2cb88a8b7b185ecd9851bdbdbbdrealtek: pcs: rtl930x: refactor TX configedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c7f063b1f95d2d1163897a808fa74753df39e17071784137021000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: gate TX tuning on attachment and baud rate
TX amp/pre-emphasis tuning depends on the SerDes' real baud rate class
rather than hw_mode, so key config_attachment's dispatch on that instead.
At 1G/2.5G, attachment doesn't change meaningful: even a non-adaptive
fiber receiver needs little compensation on a short trace, so
PHY-attached and fiber links already use the same config there. At 10G,
real channel loss is high enough that it matters: PHY-attached links
equalize on the PHY's own far-end receiver and need less amp drive,
while genuine fiber/DAC links, which have no adaptive receiver
downstream, need the full config. Real DAC-vs-fiber detection doesn't
exist yet, so both of those still share one config for now.
Make use of the PLL speed enum for now, though it is a bit blurry and
may not represent the real baud rate in some cases, e.g. QSGMII (1.25G
PLL with multiplier -> 5G).
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:01 +02007f063b1f95d2d1163897a808fa74753df39e1707realtek: pcs: rtl930x: gate TX tuning on attachment and baud rateedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c0f1019db1d45f578221611d1900653863c60aa481784137021000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comrealtek: pcs: rtl930x: gate WDIG 10G-mode bit on real baud rate
This bit was set unconditionally for any 10G-capable SerDes regardless
of hw_mode, including SGMII/1000BASEX/2500BASEX running on 10G-capable
silicon. The vendor SDK's dal_longan_construct_mac_default_10gmedia_fiber
gates it on the port's declared protocol class instead, applying it to
PHY-attached XSGMII/USXGMII as well as genuine fiber - the "medium to
fiber" naming doesn't match its actual condition.
Gate on speed == RTPCS_SDS_PLL_SPD_10000 instead, matching the real
10G-class protocol family, and actively clear it for 1G/2.5G modes so a
prior 10G-class configuration doesn't leave it stuck across a runtime
downshift. 0 also matches this register's confirmed hardware reset
default on an unconfigured SerDes.
Link: https://github.com/openwrt/openwrt/pull/24232
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 19:37:01 +02000f1019db1d45f578221611d1900653863c60aa48realtek: pcs: rtl930x: gate WDIG 10G-mode bit on real baud rateedittarget/linux/realtek/files-6.18/drivers/net/pcs/pcs-rtl-otto.c
- target/linux/ath79/dts/ar9344_enterasys_ws-ap3705i.dts2644302c14dfbae1c7c33e90836b426689a46fd61784139191000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comath79: fix u-boot-env nvmem-layout on enterasys,ws-ap3705i
The u-boot-env0 partition on this board stores a redundant U-Boot
environment (4-byte CRC32 + 1-byte flag + data), with the flag byte
differing between the u-boot-env0/u-boot-env1 copies (0x00 vs 0x01).
The actual environment size used by U-Boot for the CRC calculation is
0x1000 bytes, not the full 0x10000 byte partition.
The DTS declared this as the plain, non-redundant "u-boot,env" layout
with no env-size, so the kernel's u-boot-env nvmem-layout driver
miscomputes the CRC and fails to probe:
u-boot-env-layout ...nvmem-layout: Invalid calculated CRC32: 0xbc490a68 (expected: 0xfae56b95)
u-boot-env-layout ...nvmem-layout: probe with driver u-boot-env-layout failed with error -22
Because the probe fails, the macaddr_uboot_ethaddr nvmem cell is never
created, so eth0's nvmem-cells reference never resolves and the
ag71xx-legacy platform device is stuck in "deferred probe pending"
forever - the device boots with no functioning Ethernet interface at
all.
Switch to "u-boot,env-redundant-count" (matching the redundant-env
layout already used on other boards from this vendor lineage, e.g.
qca9557_extreme-networks_ws-ap3805i.dts) and set env-size to the
verified 0x1000, which fixes CRC validation and lets eth0 probe
successfully.
Verified on real hardware: before the fix, eth0 never comes up
(confirmed against the official 25.12.5 release, matching CRC values
exactly); after the fix, eth0 links up normally and dmesg is free of
any CRC/nvmem-layout errors.
Signed-off-by: Zoltan Szalay <dealer@ddsweb.hu>
Signed-off-by: Zoltan Szalay <szazo@halycomp.hu>
Link: https://github.com/openwrt/openwrt/pull/24134
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 20:13:11 +02002644302c14dfbae1c7c33e90836b426689a46fd6ath79: fix u-boot-env nvmem-layout on enterasys,ws-ap3705iedittarget/linux/ath79/dts/ar9344_enterasys_ws-ap3705i.dts
- target/linux/siflower/sf21/config-6.12target/linux/generic/config-6.18target/linux/generic/config-6.12867c857b93ae4376041975ebb6323ce0135a32bb1784139489000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.comkernel: disable pcrypt
The obsolete pcrypt module is being removed upstream.
Signed-off-by: Qingfang Deng <dqfext@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/24222
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 20:18:09 +0200867c857b93ae4376041975ebb6323ce0135a32bbkernel: disable pcryptedittarget/linux/siflower/sf21/config-6.12edittarget/linux/generic/config-6.12edittarget/linux/generic/config-6.18
- target/linux/mpc85xx/p1010/config-defaulttarget/linux/mpc85xx/patches-6.12/220-usb-fsl-mph-dr-of-add-regulator-support.patchtarget/linux/mpc85xx/patches-6.18/220-usb-fsl-mph-dr-of-add-regulator-support.patchtarget/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts9e43544bc6ecea0e472ee6cc1bdf1e44ff199cdf1784139952000https://taiha.net/jenkins/user/jelonek.jonasjelonek.jonasjelonek.jonas@gmail.commpc85xx: use regulator for USB power
Use upstream solution for managing GPIO power for USB devices.
A small patch is needed to make the whole thing work as this is an older
USB driver that does not use the PHY framework.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/16842
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
2026-07-15 20:25:52 +02009e43544bc6ecea0e472ee6cc1bdf1e44ff199cdfmpc85xx: use regulator for USB poweredittarget/linux/mpc85xx/p1010/config-defaultedittarget/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dtsaddtarget/linux/mpc85xx/patches-6.12/220-usb-fsl-mph-dr-of-add-regulator-support.patchaddtarget/linux/mpc85xx/patches-6.18/220-usb-fsl-mph-dr-of-add-regulator-support.patch
githttps://taiha.net/jenkins/user/danieldanielhttps://taiha.net/jenkins/user/robimarkorobimarkohttps://taiha.net/jenkins/user/ansuelsmthansuelsmthhttps://taiha.net/jenkins/user/jelonek.jonasjelonek.jonas