Commits d205878ede and 46cf10771a relabeled the supported Zyxel devices from v1/v2 to A1/B1, but board setup files were overlooked.
Fixes: d205878ede ("rtl838x: rename GS1900 series v1/v2 to A1/B1") Fixes: 46cf10771a ("rtl839x: rename GS1900 series v1/v2 to A1/B1") Signed-off-by: Stijn Segers <foss@volatilesystems.org> Link: https://github.com/openwrt/openwrt/pull/20590 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: c361c1e)
Commits d205878ede and 46cf10771a relabeled the supported Zyxel devices from v1/v2 to A1/B1, but board setup files were overlooked.
Fixes: d205878ede ("rtl838x: rename GS1900 series v1/v2 to A1/B1") Fixes: 46cf10771a ("rtl839x: rename GS1900 series v1/v2 to A1/B1") Signed-off-by: Stijn Segers <foss@volatilesystems.org> Link: https://github.com/openwrt/openwrt/pull/20590 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 8067fd5)
** This commit includes a fix for the GPIO pins for factory/reset and WPS. It was reversed and is now fixed.
* U-Boot Mod Openwrt Installation via UART:
Openwrt Stock Layout Commit: https://github.com/openwrt/openwrt/commit/6e04dccb7ad3191e9a48597a1b354bf548ead1d8 NOTE: Stock Openwrt is not necessary. You can go straight to ubootmod version of the firmware. However, it is recommended to follow stock layout instructions to backup NAND.
1. Configure TFTP server with IP 192.168.1.66. Copy `openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-initramfs-recovery.itb` to TFTP root and rename to `predator.bin` 2. Interrupt boot by pressing 0 on startup or select `U-Boot Console` in U-Boot Boot Menu. 3. Run setenv `serverip 192.168.1.66; setenv ipaddr 192.168.1.1; tftpboot 0x46000000 predator.bin; bootm` in uboot console. 4. Wait for boot complete on Openwrt initramfs env. 5. Transfer `openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-initramfs-recovery.itb`, `openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-squashfs-sysupgrade.itb`, `openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-bl31-uboot.fip`, `openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-preloader.bin` to router's /tmp/ directory. 6. run `ubidetach -p /dev/mtd5; ubiformat /dev/mtd5 -y; ubiattach -p /dev/mtd5` 7. run `ubimkvol /dev/ubi0 -n 0 -N ubootenv -s 128KiB` 8. run `ubimkvol /dev/ubi0 -n 1 -N ubootenv2 -s 128KiB` 9. run `ubimkvol /dev/ubi0 -n 2 -N recovery -s 10MiB` 10. run `ubiupdatevol /dev/ubi0_2 /tmp/openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-initramfs-recovery.itb` 11. install kmod-mtd-rw via opkg or apk. 12. run `insmod /lib/modules/$(uname -r)/mtd-rw.ko i_want_a_brick=1` 13. run `mtd write /tmp/openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-preloader.bin bl2` 14. run `mtd write /tmp/openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-bl31-uboot.fip fip` 15. run `sysupgrade -n /tmp/openwrt-mediatek-filogic-acer_predator-w6x-ubootmod-squashfs-sysupgrade.itb` 16. reboot to ubootmod layout
mediatek: mt7622: fix 2.5G WAN port on Netgear WAX206
Since 6b43a52171f5, the PHY is using interrupts instead of polling. It turned out that the interrupt number is wrong and the WAN port doesn't work. This commit fixes this bug.
Fixes: 6b43a52171f5 ("mediatek: mt7622: add the missing phy interrupt-parent for WAX206") Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl> (commit: 351deeb)
Fix Totolink X6000R image failing to upgrade via sysupgrade due to an incorrect upgrade case. The fallback upgrade path used the NAND upgrade routine, which caused the "layout volume not found" error on NOR flash devices. By adding a specific case for this board, sysupgrade now uses `default_do_upgrade`, which is compatible with the NOR flash layout.
wpa_supplicant: use a timer to defer starting interfaces
This allows wpa_supplicant to process pending netlink socket messages first. Without this change, there is a race condition where the newly created interface processes netlink events from the removal of the previous interface.
Signed-off-by: Felix Fietkau <nbd@nbd.name> (commit: e373a32)
ipq806x: remove trailing whitespaces in base-files
This removes the obsolete trailing whitespaces from all base-files cases to be in line with other targets.
Signed-off-by: Christoph Krapp <achterin@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20603 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 2a8b899)
Signed-off-by: Christoph Krapp <achterin@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20603 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 24e2c70)
Signed-off-by: Christoph Krapp <achterin@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20603 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 3156d72)
scripts/make-index-json: ensure that manifest output is in opkg format
Certain existing tooling, such as 'package-metadata.pl', are written to accept the output of 'opkg list' with package manifest delimited by '-'. The 'make-index-json.py --manifest' output was emulating the 'apk list --manifest' format without the delimiting dash, thus breaking these legacy tools.
We fix this by adding the dash to the manifest output, which allows all existing tooling to process the output irrespective of whether the build system uses opkg or apk.
Signed-off-by: Eric Fahlgren <ericfahlgren@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20094 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 3b21f97)
realtek: dsa,pcs: rtl930x: Disable SerDes patching for 10G-QXGMII
The code to add bootstrapping for 10G-QXGMII on RTL930X broke the only devices which are using 10G-QXGMII on RTL930X (Plasma Cloud PSX8+PSX10) in OpenWrt. It is currently unknown what other changes are pending to get this correctly working. But both the `rtpcs_930x_sds_usxgmii_config()` call and the write of the "magic" SerDes values in the patching process break the SerDes connected to the RTL8224 PHYs.
The Plasma Cloud PSX8+PSX10 devices get their RTL8224 and the 10G-QXGMII SerDes bootstrapped directly by u-boot.
Fixes: dca20f91ea12 ("realtek: add serdes patch for 10G_QXGMII") Signed-off-by: Sven Eckelmann <se@simonwunderlich.de> Link: https://github.com/openwrt/openwrt/pull/20588 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 87c7670)
Check for and handle an error which may be returned by rtpcs_create in various cases.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: c447ba0)
realtek: dsa: allow to drop phy-handle on switch ports
When Realtek SerDes is completely handled by PCS, it is not treated as a regular PHY anymore. Thus, we should be able to drop the currently used pseudo-PHYs and phy-handles for ports which just use the SerDes as PCS but have no PHY attached.
Allow to drop the phy-handle from switch port definitions if there is a pcs-handle defined by relaxing several checks in the DSA driver.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: ed240e3)
realtek: rtl93xx: remove pseudo-PHYs and phy-handle from SFP ports
RTL93XX reached the point where the SerDes' are no longer treated as regular PHYs. Instead, they are managed by the dedicated PCS driver. Thus, all device tree definitions should follow this change.
Remove the pseudo-PHYs for the SerDes (so far usually defined with macro INTERNAL_PHY) and corresponding 'phy-handle's from all SFP ports. This removes a long-lasting confusion from our Realtek driver(s).
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 623180a)
Drop the now unused SerDes code for RTL930X from rtl83xx-phy driver as the SerDes is completely managed by the PCS driver.
This marks a breaking point because RTL930X SerDes is no longer treated as a regular PHY device.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: f578ed0)
realtek: dsa: remove 'RTL93XX SerDes as PHY' leftovers
RTL93XX SerDes is entirely managed through the PCS driver and not treated as PHYs anymore. Thus, remove the leftovers from the DSA driver.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 447415b)
After having moved RTL93XX SerDes configuration from PHY to PCS driver, the DSA driver doesn't need to know about SerDes explicitly anymore.
Although RTL83XX SerDes is still partly managed within the DSA driver, it doesn't make use of the sds_num property/field. RTL93XX was the only user of this right now.
Thus, we can just remove the remaining 'sds_num' code which doesn't serve any purpose anymore.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20577 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 3570dee)
