a4965dbf48
PCS driver registers each SerDes as an fwnode_pcs provider in probe; the resolver returns the cached or freshly-allocated rtpcs_link for the requested (sds, link_idx) cell. DSA glue stops calling rtpcs_create directly, drops .mac_select_pcs, and instead populates phylink_config.num_available_pcs / fill_available_pcs from each port's pcs-handle in phylink_get_caps. The rtl838x_port.pcs pointer becomes a has_pcs bool populated at port probe via fwnode_property_ present, since nothing assigns the actual phylink_pcs anymore but the "does this port use a PCS?" checks elsewhere still need a presence flag. Without .mac_select_pcs, phylink_major_config only searches the pcs_list when state->interface is set in phylink_config.pcs_interfaces (drivers/net/phy/phylink.c:1378). Populate it per port whenever the port has a pcs-handle, listing the SerDes-routable interface modes for each SoC variant -- without this, pcs_config / pcs_link_up are never called and the SerDes is left unconfigured. pcs_get_state still needs the MAC port number to index per-port link status registers. Recover it at probe via rtpcs_map_links: walk the sibling switch's ethernet-ports subtree (same backwards topology lookup the sibling MDIO driver does for phy-handle), and for every port whose pcs-handle resolves to one of our SerDes, store the port's reg in sds->link_port[]. The resolver consults link_port[] when allocating rtpcs_link and fails with -ENODEV if a consumer requested a link the map step didn't record. Avoids a driver-side port_base table that would have to encode per-SoC SerDes-to-port wiring (and would silently break on non-contiguous variants); the DT is the single source of truth. Kconfig selects FWNODE_PCS. Assisted-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Link: https://github.com/openwrt/openwrt/pull/23539 Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> |
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| BSDmakefile | ||
| Config.in | ||
| COPYING | ||
| feeds.conf.default | ||
| Makefile | ||
| README.md | ||
| rules.mk | ||
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 -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo 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
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0