summaryrefslogtreecommitdiff
path: root/target/linux/brcm63xx/image
AgeCommit message (Collapse)Author
2008-12-10Fix typo, we are not building for the DG834G (ar7) but the DG834GT (brcm6348)florian
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13588 3c298f89-4303-0410-b956-a3cf2f4a3e73
2008-12-10Add support for Sagem F@ST2404 (#4332)florian
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13583 3c298f89-4303-0410-b956-a3cf2f4a3e73
2008-12-07Add support for bcm96348gw10 (Netgear DG834GT) (#4319)florian
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13540 3c298f89-4303-0410-b956-a3cf2f4a3e73
2008-11-20Generate valid images for the bcm96348gw boardflorian
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13298 3c298f89-4303-0410-b956-a3cf2f4a3e73
2008-11-15This patch is for broadcom 96348GW-11 boards, to get USB and Ethernet ↵florian
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
2008-10-20Add definitions for bcm96350vw, add back bcm63xx mtd driver, be careful when ↵florian
testing with 8MB devices git-svn-id: svn://svn.openwrt.org/openwrt/trunk@13015 3c298f89-4303-0410-b956-a3cf2f4a3e73
2008-05-18bcm963xx: image generation using image taggernbd
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
2008-05-18bcm963xx: fix load address / kernel entrynbd
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
2008-05-09enable proper PCI & USB support detection at config-time by disabling ↵nico
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
2008-04-01brcm63xx image generation cleanups (#3169)florian
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10703 3c298f89-4303-0410-b956-a3cf2f4a3e73
2007-11-10make the image filenames a bit shorternbd
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@9533 3c298f89-4303-0410-b956-a3cf2f4a3e73
2007-09-06strip the kernel version suffix from target directories, except for brcm-2.4 ↵nbd
(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