summaryrefslogtreecommitdiff
path: root/target/linux/brcm63xx/Makefile
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2008-05-18 17:30:04 +0000
committerFelix Fietkau <nbd@openwrt.org>2008-05-18 17:30:04 +0000
commit2dfabe39918965db358452bea94d2a317c58309a (patch)
tree578e1f4f602d81421a19367c1bf4b90c204ecc24 /target/linux/brcm63xx/Makefile
parent301ee97229491fbdd694e22aefaaf5058b93da48 (diff)
downloadmtk-20170518-2dfabe39918965db358452bea94d2a317c58309a.zip
mtk-20170518-2dfabe39918965db358452bea94d2a317c58309a.tar.gz
mtk-20170518-2dfabe39918965db358452bea94d2a317c58309a.tar.bz2
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> SVN-Revision: 11171
Diffstat (limited to 'target/linux/brcm63xx/Makefile')
0 files changed, 0 insertions, 0 deletions