Felix Fietkau 2dfabe3991 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		2008-05-18 17:30:04 +00:00
..
files	Upgrade brcm63xx to 2.6.24	2008-02-13 17:31:17 +00:00
image	bcm963xx: image generation using image tagger	2008-05-18 17:30:04 +00:00
patches	Upgrade brcm63xx to 2.6.24	2008-02-13 17:31:17 +00:00
profiles	strip the kernel version suffix from target directories, except for brcm-2.4 (the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles.	2007-09-06 16:27:37 +00:00
config-2.6.24	enable proper PCI & USB support detection at config-time by disabling CONFIG_PCI & CONFIG_USB entries in generic/config and enabling them on targets where appropriate	2008-05-09 17:08:51 +00:00
Makefile	upgrade to 2.6.24.5	2008-04-28 10:23:36 +00:00