fa3b9f5149
Add dual-partition upgrade support for Qihoo 360v6 using the generic bootconfig.sh library. This enables safe system upgrades with automatic failover capability. The device uses Qualcomm's bootconfig structure to control A/B partition switching. The bootloader dynamically maps physical NAND partitions to logical MTD devices based on the bootconfig, ensuring firmware always writes to the inactive partition. Implementation details: - Use bootconfig.sh library (copied from ipq50xx) for bootconfig operations - Operate on 'rootfs' partition by name instead of hardcoded offset - Add magic header validation for safety - Remove OEM UBI volumes (wifi_fw and ubi_rootfs) before sysupgrade - Toggle bootconfig before removing OEM volumes Hardware details: - SoC: Qualcomm IPQ6000 - Flash: NAND with dual rootfs partitions (mtd16/mtd17) - Bootconfig: controls slot selection via partition name lookup Installation: Standard sysupgrade process. After upgrade, the system will boot from the new partition while preserving the old system as backup. The OEM volume cleanup is necessary because these volumes are created by the stock firmware and are not automatically cleaned by the standard nand_upgrade_prepare_ubi() function, which only removes volumes named 'kernel', 'rootfs', and 'rootfs_data'. Without this cleanup, the remaining OEM volumes consume available space, causing the creation of rootfs_data to fail during sysupgrade. Tested on Qihoo 360v6 running stock firmware and OpenWrt. Signed-off-by: Zhenyu Qi <qzydustin@hotmail.com> Link: https://github.com/openwrt/openwrt/pull/21154 Signed-off-by: Robert Marko <robimarko@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