hsist
/
freifunkist-firmware
6
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16108 Commits
1 Branch
0 Tags
164 MiB
 
 
 
 
 
 
Tag: Branch: Tree: f9d20beed7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f9d20beed7'
${ noResults }
Felix Fietkau f9d20beed7
mac80211: merge pending cfg80211 patches to fix a race condition with setting the regdomain for multiple cards 		14 years ago
docs docs: fix a counting fail 15 years ago
include package-ipkg.mk: add support for "essential" package flag, fix typo 14 years ago
package mac80211: merge pending cfg80211 patches to fix a race condition with setting the regdomain for multiple cards 14 years ago
scripts deptest: Capitalize failure message. Makes it easier to spot in the logs. 14 years ago
target x86: refresh config, enable pci express support 14 years ago
toolchain
…
tools imagetag: Significantly updated brcm63xx imagetag writing tool. * Rewrote commandline parsing code using gengetopt - We now get long options - We have more options including use of the info section for board information (e.g. to add the same boardid but different GPIOs on different routers) * Added back the ability to write stock images (this is useful, for example, when copying the firmware from the in-memory flash, and then being able to create an image that will let you revert to/test stock firmware * Fixed copying of CRCs to use memcpy instead of strncpy (strncpy stops at 0) * Added ability to use all sections of the imagetag, including custom magic signatures (e.g. for the Telsey router I'm adding soon), info sections, and reserved sections * Added putting the router type (as defined in the image generating Makefile) into the info1 section and the filesystem type in the info2 section. This will be used by mtd (when I add the code) to return the name of image used to flash this router. (As requested by Jo, as well as being useful for same boardid different board scenario described above). 14 years ago
.gitignore
…
BSDmakefile
…
Config.in
…
LICENSE finally move buildroot-ng to trunk 9 years ago
Makefile
…
README remove bison requirement (see [10398] & [14900]) 15 years ago
feeds.conf.default switch to LuCI trunk, should be stable enough for common use now 14 years ago
rules.mk
…

README 

This is the buildsystem for the OpenWrt Linux distribution

Please use "make menuconfig" to configure your appreciated
configuration for the toolchain and firmware.

You need to have installed gcc, binutils, patch, bzip2, flex,
make, gettext, pkg-config, unzip, libz-dev and libc headers.

Simply running 'make' will build your firmware.
It will download all sources, build the cross-compile toolchain, 
the kernel and all choosen applications.

You can use scripts/flashing/flash.sh for remotely updating your embedded
system via tftp.

The OpenWrt system is documented in docs/. You will need a LaTeX distribution
and the tex4ht package to build the documentation. Type make -C docs/ to build it.

Building your own firmware you need to have access to a Linux, BSD or MacOSX system.
Cygwin will not be supported because of the lack of case sensitiveness.

Sunshine!
	Your OpenWrt Project
	http://openwrt.org