summaryrefslogtreecommitdiffstats
path: root/target/linux/brcm63xx/config-2.6.25
diff options
context:
space:
mode:
authornbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2008-05-18 17:30:04 +0000
committernbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2008-05-18 17:30:04 +0000
commit8a5477f5860e5c78c8ddc5a7d5efd95bec96a8d1 (patch)
tree1fdcb14f68659caf865d2ba09b9c17dae45d2e50 /target/linux/brcm63xx/config-2.6.25
parent72ac579241312915d2dcec02491d7d4cc3c79886 (diff)
bcm963xx: image generation using image tagger
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
Diffstat (limited to 'target/linux/brcm63xx/config-2.6.25')
0 files changed, 0 insertions, 0 deletions