Age | Commit message (Collapse) | Author |
|
interface, thanks to Anselmo Luginbuhl and Daniel Dickinson (#4909, #4943)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@15253 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@15242 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
decimal (#4885)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@15133 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
closes (#4366)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@14896 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@14850 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@14305 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@14264 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13616 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13588 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13583 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13540 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13298 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
working. Also it patches mtd map driver for bcm96xx boards to be sure that CFE1CFE1 code is detected when booting from CFE. (#4201)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13213 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
testing with 8MB devices
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13015 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
This adds CFE tagged image generation in the BCM963xx target image Makefile.
It has to generate its own LZMA compressed kernel because CFE is a LZMA nazi.
It also seems that the Broadcom image tagger as well as CFE use AdvanceCOMP,
which is based on a slightly older LZMA SDK. Anyways, some of the code is
GPL, some of it is LGPL, so it might be that Broadcom owes some sources.
Also, LZMA has a bug which causes it to generate different output when you
are using stdin / stdout compared to plain files. I've just worked around
the issue by using plain files.
Signed-off-by: Axel Gembe <ago@bastart.eu.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11171 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
Current kernels have the same kernel entry as load address, so just set them
like this. Also, the BCM963xx uses 0x80010000 as its load address, so use this
too.
Signed-off-by: Axel Gembe <ago@bastart.eu.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11169 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
CONFIG_PCI & CONFIG_USB entries in generic/config and enabling them on targets where appropriate
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11097 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10703 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@9533 3c298f89-4303-0410-b956-a3cf2f4a3e73
|
|
(the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@8653 3c298f89-4303-0410-b956-a3cf2f4a3e73
|