a4cbb44c1b
The RTL931x has 14 frontend and at least 26 backend serdes. Currently the programming functions always need to determine the right backend serdes from the given frontend serdes on their own. We plan to provide a consistent serdes mapping to all callers as follows Frontend SerDes | 0 1 2 3 4 5 6 7 8 9 10 11 12 13 -----------------+------------------------------------------ Backend SerDes 1 | 0 1 2 3 6 7 10 11 14 15 18 19 22 23 Backend SerDes 2 | 0 1 2 4 6 8 10 12 14 16 18 20 22 24 Backend SerDes 3 | 0 1 2 5 6 9 10 13 14 17 18 21 22 25 frontend page "even" frontend SerDes "odd" frontend SerDes page 0x000-0x03f (analog): page 0x000-0x03f back SDS page 0x000-0x03f back SDS page 0x100-0x13f (XSGMII1): page 0x000-0x03f back SDS page 0x000-0x03f back SDS+1 page 0x200-0x23f (XSGMII2): page 0x000-0x03f back SDS page 0x000-0x03f back SDS+2 As a first micro step provide some helpers that simply operate on frontend serdes and will determine the backend serdes on their own. So rtmdio_931x_read_sds_phy() and rtmdio_931x_write_sds_phy() operate on backend serdes. While rtmdio_931x_read_sds_phy_**new**() and rtmdio_931x_write_sds_phy_**new**() operate on frontend serdes. This is only an intermediate naming convention and will be cleanup afterwards. In a first step make use of these new functions whenever we want to access the analog page. As the pages stay unchanged in the new functions conversion is as simple as this: Old: asds = rtl931x_get_analog_sds(...) rtmdio_931x_read_sds_phy(asds, ...) New: rtmdio_931x_read_sds_phy_new(sds, ...) Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: https://github.com/openwrt/openwrt/pull/19818 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