Jonas Jelonek
12120ba3a0
RTL930x and RTL931x program the same physical SerDes IP mode field (page 0x1f reg 0x09, bits 11:7 hold the 5-bit mode value, bit 6 is the "force mode" enable), but did so via two unrelated code paths: RTL930x kept the force bit separate from the value in a __set helper, while RTL931x had it baked into each switch-case constant. Add a shared rtpcs_93xx_sds_set_ip_mode() that takes the rtpcs_sds_mode enum, looks up the 5-bit value from the existing sds_hw_mode_vals table, and writes value | force-bit in one place. Convert both variants: - RTL930x: drop __rtpcs_930x_sds_set_ip_mode and the manual table lookup; __rtpcs_930x_sds_get_ip_mode is replaced by the shared rtpcs_93xx_sds_get_ip_mode, which reverse-looks the raw register value up in sds_hw_mode_vals[] and returns the matching enum rtpcs_sds_mode (or -ENOENT for an unmapped raw value). The wrapper that orchestrates power, CMU, state machine and rx-reset around the mode write is renamed to rtpcs_930x_sds_apply_ip_mode for clarity. - RTL931x: drop the per-mode switch and the leftover pr_info debug print; rename the symerr-clear + MAC-OFF + IP-mode-write wrapper to rtpcs_931x_sds_apply_ip_mode. rtpcs_930x_sds_reconfigure_to_pll() now goes through the new shared get/set helpers: it saves the current IP mode as an enum on entry and restores it via the enum-taking setter after the PLL reconfigure. This changes behavior by mapping the raw mode setting through the hardware mode table, effectively blocking unknown modes which might be set by bootloader or somewhere else. This is intended and might uncover unknown behavior instead of hiding it. As a side-effect, QSGMII is now properly set too for RTL931x. Most code paths anyway already had support for this mode, but it was missing from the mode setting. Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: https://github.com/openwrt/openwrt/pull/23213 Signed-off-by: Robert Marko <robimarko@gmail.com>
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