As shown above, the SPI master controller shares its pin with GPIO 8, 9, 10, 11, 12. In some upcoming devices (like the Plasma Cloud PSX28/ESX28), they will be used for SFP cage signaling. These pins must therefore be switched manually to the GPIO mode.
The SPI_CTRL0 register provides all necessary configuration to enforce the GPIO mode of the pins. And until more requirements (and a correct driver) for the SPI master controller arise, it is therefore possible to use pinctrl-single to configure it using the devicetree.
Previously the ethernet driver did configure the SPI master controller for 31.25 MHz. It is unknown for which kind of device this was originally made and what was actually connected there. But this manual write to the register conflicts potentially with the write of the pinctrl driver to the same register. Luckily, we don't need this SPI speed configuration in the ethernet driver. Still, to allow this device an easy migration, the `spi0-31mhz` configuration was already prepared.
Signed-off-by: Sven Eckelmann <se@simonwunderlich.de> Link: https://github.com/openwrt/openwrt/pull/20263 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 3adb820)
realtek: rtl93xx: replace pending I2C patches with upstreamed patches
Replace the pending I2C backport patches for RTL93XX added in 44655c97bb with the upstreamed variants. The patches have been accepted upstream in the meantime and are included in v6.17 or v6.18.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/20273 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 272a392)
The FIT loadaddr on RK3308/RK3566/RK3568/RK358x is 0x02000000 instead of 0x02080000, while on RK3576 it's 0x42000000, which is quite different from the former SoCs and incompatible with current kernel loadaddr value.
kernel: modules: fix mlxreg dependency to avoid deferred probe
The mlxreg-hotplug platform driver was failing to probe due to a missing I²C multiplexer dependency. Previously, only kmod-i2c-mux-mlxcpld was declared, but mlxreg also requires kmod-i2c-mux-reg to initialize its I²C mux functionality.
Without this dependency, the driver probe was deferred:
With kmod-i2c-mux-reg added, the probe succeeds and the expected multiplexed I²C buses are registered:
[ 15.793884] i2c i2c-1: Added multiplexed i2c bus 2 [ 15.799391] i2c i2c-1: Added multiplexed i2c bus 3 [ 15.804830] i2c i2c-1: Added multiplexed i2c bus 4 ...
Signed-off-by: Til Kaiser <mail@tk154.de> Link: https://github.com/openwrt/openwrt/pull/20274 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 71e057b)
Right now the sha256sums are only created for the targets/ folder (i.e. firmware images) and only the buildbot generates those sha256sums. Instead, let the build system create the sha256sums directly.
Signed-off-by: Paul Spooren <mail@aparcar.org> (commit: 06be7f5)
realtek: dsa: Keep HW specific mirror code in SoC helper
Instead of using a lot of if-else blocks in the port mirror code, provide SoC specific function which calculates the SoC specific portions. The generic part of the port mirroring code can then simply operate on the calculated register addresses and values.
Suggested-by: Markus Stockhausen <markus.stockhausen@gmx.de> Signed-off-by: Sven Eckelmann <se@simonwunderlich.de> Link: https://github.com/openwrt/openwrt/pull/20264 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 8e22848)
realtek: rtl93xx: dsa: Add support for port based mirroring
The RTL930X and RTL931X SoCs support port-based, flow-based, and RSPAN-based mirroring. Like for other SoCs from the realtek target, only the port based port mirroring can be exposed using Linux's tc subsystem.
The port_mirror_add() implementation was updated with the following considerations for RTL93xx SoCs:
* mirrored packets must pass through the TX pipeline of the mirroring port, so they are subject to configuration such as VLAN tagging, remarking, and EVC * when a packet hits both source ports (SPM) and destination port (DPM) of a mirror group, the egress port traffic will be mirrored
The port_mirror_del() function doesn't require any modifications.
Signed-off-by: Sharadanand Karanjkar <sk@simonwunderlich.de> Co-developed-by: Sven Eckelmann <se@simonwunderlich.de> Signed-off-by: Sven Eckelmann <se@simonwunderlich.de> Link: https://github.com/openwrt/openwrt/pull/20264 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: be84bb3)
If transmissions are done outside of the DSA switch (directly from the CPU port), the STP state must not block the transmission. Otherwise, STP frames are not correctly submitted and the STP frames cannot correctly detect loops before switching a port in the forwarding state.
The same applies for the LLDP frames. These must be submitted independent of the STP state to identify neighbors or configure POE limits.
It is not necessary to filter specific destination mac addresses because the transmission was done outside the bridge/switch in the first place. The transmission is therefore forced.
Signed-off-by: Issam Hamdi <ih@simonwunderlich.de> Co-developed-by: Sven Eckelmann <sven@narfation.org> Signed-off-by: Sven Eckelmann <sven@narfation.org> Link: https://github.com/openwrt/openwrt/pull/20184 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 0d6b7fb)
d3be5474f6e6 udebug-cli: ignore zero-length messages in logstream c79f02d899df ucode: fix skipping lines where the timestamp cannot be parsed 5327524e7153 cmake: bump minimum required version to 3.13
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> (commit: f3d8bea)
tools/ccache: same behaviour for local and CI builds
If the environment variable `CI` is set, ccache will enable the CMake option CCACHE_DEV_MODE by default. This leads to differing behaviour between local and CI builds which takes quite some time to debug. 🤯
Achieve consistent behaviour between local builds and CI builds by setting CCACHE_DEV_MODE. Set it to OFF, because CCACHE_DEV_MODE amongst other settings like linker choice, enables -Werror, which will lead to potential compilation failures when the host compiler is updated. Using -Werror for host utils is not desirable, because the compiler version used is not controlled by the OpenWrt build system and host utils should compile successfully on an as wide range of host OSes as possible.
Reported-by: Roman Azarenko <roman.azarenko@iopsys.eu> Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu> Link: https://github.com/openwrt/openwrt/pull/20290 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> (commit: 6f32c65)
after change include/package-pack.mk in 16416782f194d1850a9d9accf02f04832a7fcea4, must use ALTERNATIVES to create soft link, otherwise the packing will be messed up.
Signed-off-by: Andy Chiang <AndyChiang_git@outlook.com> Link: https://github.com/openwrt/openwrt/pull/20283 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 2f2b9c2)
4b7638925d3e iptime-crc32: add support for ipTIME AX3000M 12c0b42231be nosimg-enc: add new tool for XikeStor SKS8300 series 2051fe5bc2a1 mktplinkfw2: Add 16MLmtk layout 5d1446bf57d6 tplink-safeloader: Add more special_id's for MR70X 075cdc0c4dd4 iptime-crc32: add support for ipTIME AX3000Q 48ababab6b08 iptime-crc32: add support for ipTIME AX3000SM f29de74ecd7d iptime-crc32: Add device support for ipTIME AX6000M 3346d7711c9a build: add mkqdimg 950f83405a93 iptime-crc32: add support for ipTIME AX7800M-6E 0725c3d4aa1b build: require CMake >= 3.5 due to dropped legacy support 996dc482a7e8 ptgen: fix misprint and simplify calculation a bit febfef7a09b1 ptgen: use long long instead of long for sizes 6ea8b6dd44d0 ptgen: fix protective MBR partition size f1f98b0b8456 ptgen: do not create stub partition to fill a gap if gap caused by alignment 3f2d14829150 ptgen: allow non-default placement of gpt entry table 78d8084c7376 ptgen: allow image generation for a specified disk size 9fa340db640e ptgen: create separate images for gpt data structure d3f8b6ed940a zynsig: add new tool for creating images for the ZyXEL GS1920 series 7e6f69b444c3 npk_pack_kernel: add tool for creating MikroTik NPK kernel packages 0782d243d23e Revert "ptgen: do not create stub partition to fill a gap if gap caused by alignment"
OpenWrt buildroot will compile all dtbs defined in target to $(KDIR)/image-$(DEVICE_DTS).dtb, so make use of it to allow us debug and use external dtbs easier without patching kernel Makefile.
This also fixes commit 5c724939c396 which forgot to update DTS_DIR in KERNEL variable.
realtek: rtl931x: Enable parsing of u-boot nvmem layouts
To be able to read out the ethaddr from the u-boot environment for MAC address configuration, it is required to also enable the NVMEM layout parsing code for the U-Boot env layout.
realtek: rtl931x: Add support for Plasma Cloud PSX28 Switch
The Plasma Cloud PSX28 Switch is a 24 + 4 port multi-GBit switch with 24x 10/100/1000/2500BaseT Ethernet ports and 4x SFP+ module slot.
Hardware:
- RTL9312C SoC - Macronix MX25L25645G (32MB flash) - 512MB DDR3 SDRAM - RTL8231 GPIO extender to control the port LEDs - 6x RTL8224 4x 10m/100m/1/2.5 Gigabit PHY - SFP+ 4x 10GBit slot - RTL8239 POE++ PSE controller with frontend MCU
The switch is powered directly via AC.
The external RS232 serial connector (RJ45, Cisco pinout) can be used to access the terminal. Serial connection is via 115200 baud, 8N1.
A reset button is accessible through a hole in the front panel.
Installation ------------
* The device can be flashed by using sysupgrade command. Either from the original vendor firmware or using an initramfs (see "Debug") * Connect serial on front panel. Connection parameters: 115200 8N1 * The image must be copied using scp to /tmp of the device
scp openwrt-realtek-rtl931x-plasmacloud_psx28-squashfs-sysupgrade.bin root@[IP address of the device]:/tmp/
* start sysupgrade without saving the original vendor configuration
* Connect serial on front panel. Connection parameters: 115200 8N1. * A tftp server is required, tftpd-hpa works well. * Power the device, at U-Boot start rapidly hit Esc key to stop autoboot * Enter passwords: "1234" or "plasmapsx" * Enable network:
realtek: rtl931x: Add support for Plasma Cloud ESX28 Switch
The Plasma Cloud ESX28 Switch is a 24 + 4 port multi-GBit switch with 24x 10/100/1000/2500BaseT Ethernet ports and 4x SFP+ module slot.
Hardware:
- RTL9312C SoC - Macronix MX25L25645G (32MB flash) - 512MB DDR3 SDRAM - RTL8231 GPIO extender to control the port LEDs - 6x RTL8224 4x 10m/100m/1/2.5 Gigabit PHY - SFP+ 4x 10GBit slot
The switch is powered directly via AC.
The external RS232 serial connector (RJ45, Cisco pinout) can be used to access the terminal. Serial connection is via 115200 baud, 8N1.
A reset button is accessible through a hole in the front panel.
Installation ------------
* The device can be flashed by using sysupgrade command. Either from the original vendor firmware or using an initramfs (see "Debug") * Connect serial on front panel. Connection parameters: 115200 8N1 * The image must be copied using scp to /tmp of the device
scp openwrt-realtek-rtl931x-plasmacloud_esx28-squashfs-sysupgrade.bin root@[IP address of the device]:/tmp/
* start sysupgrade without saving the original vendor configuration
* Connect serial on front panel. Connection parameters: 115200 8N1. * A tftp server is required, tftpd-hpa works well. * Power the device, at U-Boot start rapidly hit Esc key to stop autoboot * Enter passwords: "1234" or "plasmapsx" * Enable network:
Fix Timing side-channel in SM2 algorithm on 64 bit ARM. (CVE-2025-9231)
Fix Out-of-bounds read in HTTP client no_proxy handling. (CVE-2025-9232)
Reverted the synthesised OPENSSL_VERSION_NUMBER change for the release builds, as it broke some exiting applications that relied on the previous 3.x semantics, as documented in OpenSSL_version(3).
ramips: Fix Hongdian H7920 v40 pinctrl default state
According to the MT7628 hardware datasheet: - GPIO/4 was originally used for I2C, but is now used as the Modem Power. - GPIO/5 was originally used for I2C, but is now used as the SIM card select. (n/a for this device) - GPIO/6 was originally used for SPI CS1, but is now used as the Serial mode switch. - GPIO/36 was originally used for PERST, but is now used as the GPS OE. (n/a for this device) - GPIO/38 was originally used for WDT, but is now used as the Modem2 Power. (n/a for this device) - GPIO/44 was used for WLED_AN, but is now controlled by `gpio-leds`.
Corrected pinctrl to ensure it works properly in the future.
mt76: Fix DTS power-limits on little endian systems
The power-limits for ru and mcs and stored in the devicetree as bytewise array (often with sizes which are not a multiple of 4). These arrays have a prefix which defines for how many modes a line is applied. This prefix is also only a byte - but the code still tried to fix the endianness of this byte with a be32 operation. As result, loading was mostly failing or was sending completely unexpected values to the firmware.
Since the other rates are also stored in the devicetree as bytewise arrays, just drop the u32 access + be32_to_cpu conversion and directly access them as bytes arrays.
mt76 as support for generic rates power limits in the devicetree. But the mt7915 supports beamforming and has another table for configuring the backoff limits. These can be configured in the DT with the paths-* properties. The path-*-bf are the ones relevant for beamforming and the ones without -bf suffix for "traditional" path backoff.
Various methods can be used to install the actual image on the flash. Two easy ones are:
ap51-flash ----------
The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up.
initramfs from TFTP -------------------
The serial console (115200 8N1) must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21):
base-files: commit and sync before removing defaults script.
Improve the resilence against power failures during boot-up by trying to sync the file system before removing the script. The order of the operations are important.
The upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/smb?h=linux-6.6.y&id=fa1c47af4ff641cf9197ecdb1f8240cbb30389c1 and the extended for ipv6 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/smb?h=linux-6.6.y&id=d9e157fcfebc126cd19b2333a6417a840c24e529 cause a regression if you try to get a connection on nautilus by a double click on share name. When you do a double click on share name Nautilus try to connect two times, and ksmbd refusing it. An issue is opened here https://github.com/namjaejeon/ksmbd/issues/512, at the moment, until we don't have a fix upstream I suggest to revert these two commits.
realtek: Enhance MTD/ECC kernel configuration for NAND targets
The Realtek NAND kernel configuration has some shortcomings. Fix this as follows:
- MTD_NAND_ECC_REALTEK selects MTD_NAND_ECC and this selects MTD_NAND_CORE. For consistency add both config options.
- The partition layout of the Linksys switches requires some tricky concatenation to keep dual boot active. Add CONFIG_MTD_VIRT_CONCAT
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/20255 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: af7a74b)
- 64 MB vendor UBI (not touched) - 10 MB OpenWrt kernel - 22 MB Openwrt mtd-concat UBI - 23 MB vendor kernel 2 (space reduced, vendor data unchanged) - 09 MB OpenWrt mtd-concat UBI
Dual-boot with stock firmware using writable u-boot-env -------------------------------------------------------
From stock to OpenWrt / primary image 1 (CLI as admin): - > boot system image1 - > reboot
From OpenWrt to stock / boot image 2: (shell as root) - # fw_setsys bootpartition 1 - # reboot
Debrick using serial interface ------------------------------
1. Press "a" "c" "p" during message "Enter correct key to stop autoboot" 2. Load vendor image with "upgrade runtime <TFTP IP>:LGS328xxxxx.imag" 3. switch to primary partition "setsys bootpartition 0" 4. safe config "savesys"
Further documentation --------------------- See https://openwrt.org/toh/linksys/lgs352c
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/20255 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 853d73f)
- 64 MB vendor UBI (not touched) - 10 MB OpenWrt kernel - 22 MB Openwrt mtd-concat UBI - 23 MB vendor kernel 2 (space reduced, vendor data unchanged) - 09 MB OpenWrt mtd-concat UBI
Dual-boot with stock firmware using writable u-boot-env -------------------------------------------------------
From stock to OpenWrt / primary image 1 (CLI as admin): - > boot system image1 - > reboot
From OpenWrt to stock / boot image 2: (shell as root) - # fw_setsys bootpartition 1 - # reboot
Debrick using serial interface ------------------------------
1. Press "a" "c" "p" during message "Enter correct key to stop autoboot" 2. Load vendor image with "upgrade runtime <TFTP IP>:LGS352xxxxx.imag" 3. switch to primary partition "setsys bootpartition 0" 4. safe config "savesys"
Further documentation --------------------- See https://openwrt.org/toh/linksys/lgs352c
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/20255 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: f88135b)
Now the NAND targets have real devices that need to be built. Remove the source-only flag to make the images available.
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/20255 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 8916b26)
The first RTL931x devices make their way into OpenWrt. Their copper ports are driven by different interfaces modes like 10G_QXGMII or Realtek proprietary XSGMII. The DSA driver has no proper handling for theses modes implemented yet. So a lot is auto-mapped to USXGMII internally. As soon as the SerDes setup activates this (wrong) mode the PHY connectivity breaks.
Disable this mode for now and rely on the proper U-Boot setup.
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/20292 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: c18476d)
b14cf98 router: log “Sending a RA on lan” at LOG_DEBUG c2810fe odhcpd: update cmake file 8c2c065 odhcpd: convert README to markdown 3b96480 odhcpd: allow the use of an alternative cfg file 7328bfe odhcpd: remove confusing #defines cdb9e5b odhcpd: improve RFC9096 § 3.5 SLAAC compliance
RFC9096 § 3.5 SLAAC compliance introduces a new config option (odhcpd piofolder), which may wear out the flash under certain conditions (for example: ISPs with dynamic IPv6 prefixes which disconnect the clients every X hours). Therefore, setting "dhcp.odhcpd.piofolder" to persistent storage in the router flash is not advisable and should be set to other kinds of persistent storage such as USBs, SDs, NVMEs... In order to prevent wearing out the router flash it's set to ephemeral storage by default (tmp): uci set dhcp.odhcpd.piofolder="/tmp/odhcpd-piofolder"
