Port the vendor SDK's _phy_rtl9310_fiber_adapt() as rtpcs_931x_sds_rxcal_fiber_adapt(), dispatched from post_config for RTPCS_SDS_ATTACH_FIBER when hw_mode is 10GBase-R (1G/100M fiber isn't calibrated by the vendor SDK either). Add the rxeq_tap_*/rxeq_vth_* setters (set_value, set_adapt) needed to drive it: fiber calibration runs VTH/TAP0 auto-adapt for 200ms, then samples the auto-adapted VTH and locks it in, forces TAP0 to a fixed value (31, per the vendor SDK), and re-locks manual mode, before letting DFE TAP1-4 auto-adapt freely and verifying via a symbol-error recheck loop. Sampling VTH needs the SerDes' debug-readback routing. Add rtpcs_931x_sds_set_debug() and rxeq_vth_get() for it, mirroring _phy_rtl9310_dbg_set()/_phy_rtl9310_dfe_get(). The final symbol-error recheck deliberately deviates from the vendor SDK's shape (adapt once, recheck 3x at 150ms, require exactly 0): symErr's field is only 8 bits wide and reads as a saturated 0xff right after rx_reset(), which looks like "link hasn't relocked yet" rather than a genuine error count - 10G optical relock can plausibly take longer than 150ms. Instead, recheck more times with more patience per check and no reset in between (so a settling link isn't interrupted), and tolerate a small nonzero symbol-error count rather than requiring exactly 0. rtpcs_931x_sds_fiber_get_symerr() already existed but was unused; wire it up alongside the existing rtpcs_931x_sds_clear_symerr(). Link: https://github.com/openwrt/openwrt/pull/24542 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.8+ 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
