summaryrefslogtreecommitdiff
path: root/arch/arm/configs/shark_defconfig
AgeCommit message (Collapse)AuthorFilesLines
2010-06-10ARM: reduce defconfigsUwe Kleine-König1-1167/+0
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
2009-12-18ARM: Kill CONFIG_CPU_32Russell King1-1/+0
26-bit ARM support was removed a long time ago, and this symbol has been defined to be 'y' ever since. As it's never disabled anymore, we can kill it without any side effects. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2009-02-19[ARM] 5363/1: Shark cleanup and new defconfigAlexander Schulz1-335/+593
This includes a new defconfig for the Shark and some changes to the mach-shark directory to avoid namespace pollution and to switch the rtc to the newer driver. Signed-off-by: Alexander Schulz <alex@shark-linux.de> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-11-30[ARM] Remove DEBUG_WAITQRussell King1-1/+0
DEBUG_WAITQ appears to have been removed by others, but no one removed the configuration option from ARM. Remote it from both Kconfig.debug and all default configurations. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-01-09[ARM] Remove CONFIG_ARCH_CAMELOT from defconfigsRussell King1-1/+0
EPXA10DB has gone, no need to keep the symbol in the defconfigs. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2005-07-16[PATCH] ARM: 2815/1: Shark: new defconfig, fixes with __io and serial portsAlexander Schulz1-33/+52
Patch from Alexander Schulz This patch brings a new default config file for the shark and fixes a compilation issue with io addressing and a runtime problem with the serial ports, where I corrected a wrong regshift value. These are all shark specific files so I hope it is ok to put them in one patch. Signed-off-by: Alexander Schulz <alex@shark-linux.de> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2005-04-17Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds1-0/+974
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!