dumalogiya
/
openwrt
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
OpenWRT firmware for routers
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
48,450 Commits
2 Branches
0 Tags
653 MiB
Diff 68.3%
C 21%
Makefile 4.7%
Shell 2.3%
Roff 1.6%
Other 2%
 
 
 
 
 
 
v19.07.3_mercusys_ac12_duma
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '494f12c52d'
${ noResults }
Go to file
Adrian Schmutzler 494f12c52d mvebu: implement compatibility version for DSA migration 
This implements the newly introduced compat-version to prevent
upgrade between swconfig and DSA for mvebu.

Just define a compat version with minor increment and an appropriate
message for both image (in Makefile) and device (in base-files).

Having taken care of sysupgrade, we can put back the SUPPORTED_DEVICES
that have been removed in previous patches to prevent broken config.

Attention:

All users that already updated to the DSA versions in master will
receive the same incompatibility warning since their devices are still
"1.0" as far as fwtool can tell.
Those, and only those, can bypass the upgrade check by using force (-F)
without having to reset config again. In addition, the new version
string needs to be put into uci config manually, so the new fwtool
knows that it actually deals with a "1.1":

   uci set "system.@system[-1].compat_version=1.1"
   uci commit system

Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
 		4 years ago
.github build: Update README & github help 6 years ago
config build: add option to mark devices as BROKEN 4 years ago
include base-files: fwtool: make compat_version backward compatible 4 years ago
package base-files: fwtool: make compat_version backward compatible 4 years ago
scripts build: add option to mark devices as BROKEN 4 years ago
target mvebu: implement compatibility version for DSA migration 4 years ago
toolchain toolchain: add PKG_RELEASE if local files 4 years ago
tools tools/mkimage: create .itb file with read-access for group,other not just owner. 4 years ago
.gitattributes add .gitattributes to prevent the git autocrlf option from messing with CRLF/LF in files 12 years ago
.gitignore build: improve ccache support 4 years ago
BSDmakefile add missing copyright header 17 years ago
Config.in merge: base: update base-files and basic config 6 years ago
LICENSE finally move buildroot-ng to trunk 8 years ago
Makefile build: improve ccache support 4 years ago
README build: switch to Python 3 5 years ago
feeds.conf.default feeds: add freifunk feed 4 years ago
rules.mk build: improve ccache support 4 years ago

README 

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------

This is the buildsystem for the OpenWrt Linux distribution.

To build your own firmware you need a Linux, BSD or MacOSX system (case
sensitive filesystem required). Cygwin is unsupported because of the lack
of a case sensitive file system.

You need gcc, binutils, bzip2, flex, python3.5+, perl, make, find, grep, diff,
unzip, gawk, getopt, subversion, libz-dev and libc headers installed.

1. Run "./scripts/feeds update -a" to obtain all the latest package definitions
defined in feeds.conf / feeds.conf.default

2. Run "./scripts/feeds install -a" to install symlinks for all obtained
packages into package/feeds/

3. Run "make menuconfig" to select your preferred configuration for the
toolchain, target system & firmware packages.

4. Run "make" to build your firmware. This will download all sources, build
the cross-compile toolchain and then cross-compile the Linux kernel & all
chosen applications for your target system.

Sunshine!
	Your OpenWrt Community
	http://www.openwrt.org