Vitaliy Sochnev
ab2dc6ab16
an7581.dtsi reserves five no-map regions for the NPU and hands all of them to the npu node. Four of them - pkt, tx-pkt, tx-bufid and ba, 110 MiB plus 26 KiB - are consumed only by airoha_npu_wlan_init_memory(), which the mt76 NPU layer calls when it attaches an Airoha-offloaded Wi-Fi chip. To run its firmware and to offload flows the NPU needs the binary region alone, and the driver looks that one up by index rather than by name. Boards that bind no Wi-Fi chip to the NPU therefore lose 110 MiB of DRAM for nothing, and they lose it whether or not the NPU probes at all: the memory is carved out by the reserved-memory node itself. On AN7581 that is both Nokia XG-040G-MD variants. an7583.dtsi already does this correctly and reserves npu_binary only. Move the four regions into a new an7581-npu-wlan.dtsi and include it from the two NPU overlays the Wi-Fi boards already pull in, so that the regions and the full memory-region list follow the Wi-Fi chip instead of the SoC. an7581-evb includes the new overlay directly instead. It declares two mediatek,mt76 nodes with airoha,npu and enables the NPU, but pins no particular chip because the card goes into a PCIe slot, so it is the one board using the offload that pulls in neither NPU overlay. Keep the ba region on all four Wi-Fi boards even though it is described as MT7996-only. It is already optional in the driver, but narrowing it down to MT7996 would change behaviour on Kite, so leave that for a separate change. Verified by building the device trees before and after: the DTBs of an7581-evb, an7581-evb-emmc-eagle, an7581-evb-emmc-kite, an7581-nokia-valyrian and an7581-w1700k-ubi are byte for byte identical, while an7581-nokia_xg-040g-md and an7581-nokia_xg-040g-md-ubi each shrink by 376 bytes and lose the four regions. Tested on a Nokia XG-040G-MD. Reserved memory drops from 197296K to 84400K and MemTotal rises from 325900 kB to 438736 kB, 110 MiB given back. The NPU still comes up on the binary region alone and reports "NPU fw version: 1456.62", so dropping the four regions costs the board neither the NPU nor its flow offloading. Not tested on Wi-Fi hardware, where the argument rests on the DTBs being unchanged. Signed-off-by: Vitaliy Sochnev <sochnev.v.74@gmail.com> Link: https://github.com/openwrt/openwrt/pull/24593 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.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