aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm63xx
Commit message (Collapse)AuthorAgeFilesLines
* bcm963xx: flashmap supportFelix Fietkau2008-05-181-0/+82
| | | | | | Signed-off-by: Axel Gembe <ago@bastart.eu.org> SVN-Revision: 11176
* bcm963xx: serial port supportFelix Fietkau2008-05-181-0/+23
| | | | | | Signed-off-by: Axel Gembe <ago@bastart.eu.org> SVN-Revision: 11175
* bcm963xx: board supportFelix Fietkau2008-05-181-0/+182
| | | | | | Signed-off-by: Axel Gembe <ago@bastart.eu.org> SVN-Revision: 11174
* bcm963xx: add 2.6.25 configuration fileFelix Fietkau2008-05-181-0/+317
| | | | | | Signed-off-by: Axel Gembe <ago@bastart.eu.org> SVN-Revision: 11173
* bcm963xx: use the 2.6.25.1 kernelFelix Fietkau2008-05-181-1/+1
| | | | | | Signed-off-by: Axel Gembe <ago@bastart.eu.org> SVN-Revision: 11172
* bcm963xx: image generation using image taggerFelix Fietkau2008-05-181-0/+27
| | | | | | | | | | | | | | | 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
* bcm963xx: fix load address / kernel entryFelix Fietkau2008-05-182-3/+3
| | | | | | | | | | 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> SVN-Revision: 11169
* enable proper PCI & USB support detection at config-time by disabling ↵Nicolas Thill2008-05-092-2/+2
| | | | | | CONFIG_PCI & CONFIG_USB entries in generic/config and enabling them on targets where appropriate SVN-Revision: 11097
* upgrade to 2.6.24.5Imre Kaloz2008-04-281-1/+1
| | | | SVN-Revision: 10959
* properly disable CONFIG_CRYPTO_HWNicolas Thill2008-04-271-1/+0
| | | | SVN-Revision: 10952
* Delete config-default file and resync kernel configuration for brcm63xxFlorian Fainelli2008-04-112-293/+3
| | | | SVN-Revision: 10790
* brcm63xx image generation cleanups (#3169)Florian Fainelli2008-04-011-0/+5
| | | | SVN-Revision: 10703
* Upgrade brcm63xx to 2.6.24Florian Fainelli2008-02-1314-459/+483
| | | | SVN-Revision: 10455
* resync kernel configGabor Juhos2008-02-111-34/+11
| | | | SVN-Revision: 10444
* upgrade & standardize kernel versionsImre Kaloz2008-02-111-1/+1
| | | | SVN-Revision: 10443
* fix initramfsFelix Fietkau2008-01-011-1/+0
| | | | SVN-Revision: 10080
* make the image filenames a bit shorterFelix Fietkau2007-11-101-1/+1
| | | | SVN-Revision: 9533
* move crypto support to a seperate crypto.mk file, split modules into ↵Nicolas Thill2007-09-231-23/+0
| | | | | | multiple packages and adjust dependencies, sync crypto options in kconfigs. SVN-Revision: 8980
* add missing 2.6 conntrack/nat helpers, add 2.6 conntrack/nat helper for RTSP ↵Nicolas Thill2007-09-221-15/+0
| | | | | | (closes: #2297, thanks to aorlinsk), sync 2.4 / 2.6 kconfigs. SVN-Revision: 8955
* clean up jffs2 config optionsFelix Fietkau2007-09-191-3/+0
| | | | SVN-Revision: 8848
* adapt profiles for subtarget changesFelix Fietkau2007-09-081-3/+0
| | | | SVN-Revision: 8695
* major target cleanup. it is now possible to have subtargets that can ↵Felix Fietkau2007-09-082-4/+3
| | | | | | override many target settings, including arch - merge adm5120, adm5120eb. target profiles still need to be adapted for subtargets SVN-Revision: 8694
* strip the kernel version suffix from target directories, except for brcm-2.4 ↵Felix Fietkau2007-09-0653-0/+8620
(the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles. SVN-Revision: 8653