This is a backport of netdev/net [1]/[2], expected to be in kernel 6.11 (if not backported to a stable branch). Since 4fdc7bb8f13f (2024-06-14, switching ath79 from kernel 6.1 to 6.6), the rtl8366s driver was made to write to bogus PHY MII registers on ath79/netgear,wndr3800 and family, and likely on other systems using this switch in a similar manner. The writes were directed to PHY 4 MII registers 0x0d (13) and 0x0e (14). The rtl8366s data sheet claims these registers are reserved. These register writes were causing the device to not maintain link, track link status, or pass traffic on eth1 (labeled WAN), as eth1 is connected to PHY 4. 0x0d is MII_MMD_CTRL, and 0x0e is MII_MMD_DATA. rtl8366s doesn't appear to support MMD in any way, and certainly not via the IEEE 802.3 annex 22D "clause 45 over clause 22" protocol implemented by mmd_phy_indirect. This patch intercepts those attempted register accesses and returns -EOPNOTSUPP without touching the switch chip. This is implemented by defining phy_driver::{read,write}_mmd as genphy_{read,write}_mmd_unsupported for this PHY. A new PHY driver for this PHY is introduced to achieve that, because this PHY was previously using genphy_driver, and there is otherwise no clean way to declare lack of support for these operations. This was caused by kernel 9b01c885be36 (2023-02-13, in 6.3). The new genphy_c45_read_eee_abilities call in genphy_read_abilities (called during phy_probe) was causing an attempted MMD read of (MMIO_MMD_PCS, MDIO_PCS_EEE_ABLE), which was transformed into an annex 22D mmd_phy_indirect operation that performed MII register writes to MII_MMD_CTRL, MII_MMD_DATA, and MII_MMD_CTRL again, followed by another read from MII_MMD_DATA. This was enough to "scramble" the state of those two MII registers, which are in fact not used for annex 22D MMD register access on this device but are reserved and have some other function, rendering the PHY unusable while so configured. The result of the bungled MMD read attempt caused the genphy driver to incorrectly believe that the PHY supported standard EEE, which led to several more attempted MMD writes and reads, in turn being transformed into writes to these two MII registers. rtl8366s does support some pre-IEEE 802.3az EEE standard form of "Green Ethernet" which the switch driver (local to OpenWrt) already has some support for. No attempt is made to map the standard operations for this device. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=225990c487c1 [2] https://lore.kernel.org/netdev/20240725204147.69730-1-mark@mentovai.com/ Fixes: https://github.com/openwrt/openwrt/issues/15981 Link: https://github.com/openwrt/openwrt/issues/15739 Reported-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Mark Mentovai <mark@mentovai.com> Link: https://github.com/openwrt/openwrt/pull/16012 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -a
to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -a
to install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfig
to select your preferred configuration for the toolchain, target system & firmware packages. -
Run
make
to build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg
. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrt
on oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-devel
on oftc.net.
License
OpenWrt is licensed under GPL-2.0