summaryrefslogtreecommitdiff
path: root/arch/arm/configs/omap3_defconfig
AgeCommit message (Collapse)AuthorFilesLines
2010-05-20omap3: Add stalker board to omap3_defconfigTony Lindgren1-0/+1
Add stalker board to omap3_defconfig Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-20omap3: update omap3_defconfigAnand Gadiyar1-37/+79
- Update the omap3_defconfig to sync up with the generated .config - Increase CONFIG_LOG_BUF_SHIFT to 16 to allow the entire boot log to be captured (useful when using boot time tracer, for example) Signed-off-by: Anand Gadiyar <gadiyar@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-05omap2/3/4: Disable CONFIG_FB_OMAP in omap3_defconfigTony Lindgren1-9/+1
Looks like CONFIG_FB_OMAP prevents somehow mounting root on MMC at least on zoom3 for multi-omap. Disable CONFIG_FB until the omap FB code is fixed. This allows booting omap3_defconfig on various omaps. Tested on 2420-n8x0, 3430-n900, 3630-zoom3 and 4430-blaze. Note that n8x0 still has issues with starting user space because of TLS and VFP. Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-05omap2/3/4: Disable CONFIG_PM_VERBOSE in omap3_defconfigTony Lindgren1-1/+1
It's too noisy. Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-05omap2/3/4: Update PMIC options for TWL and Menelaus chipsTony Lindgren1-6/+7
These are needed for mounting root on MMC on many boards. Also disable CONFIG_WATCHDOG_NOWAYOUT, that can keep the system from running with external watchdogs. Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-05omap2/3/4: Make omap3_defconfig usable on Nokia boardsTony Lindgren1-2/+2
The bootloader on Nokia boards does not support updating the kernel cmdline. For the other boards, the bootloader provided cmdline will be used instead. To mount root on n8x0, compile in also the MMC_OMAP. It seems that the best way to mount root with the new kernels on Nokia boards is to mount root on mmcblk0p2. Note that n8x0 current has several issues booting with omap3_defconfig: The bootloader has a 2MB limit for loading kernels, so you may want to use kexec. Also ARMv6 does not currently work with ARMv7 for VFP and TLS. Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-05-05omap2/3/4: Add new boards to omap3_defconfigTony Lindgren1-2/+3
Enable 2430 omaps and the missing boards. Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-03-11omap: Enable PM_RUNTIME in defconfigs to avoid USB compile errorsTony Lindgren1-1/+1
While waiting for the related USB patch, fix compile by enabling it in the defconfigs. As discussed at: http://thread.gmane.org/gmane.linux.usb.general/27432/focus=4460 Otherwise we'll get errors like: drivers/usb/core/hcd.c:1892: error: 'pm_wq' undeclared (first use in this function) drivers/usb/core/hcd.c:1892: error: (Each undeclared identifier is reported only once drivers/usb/core/hcd.c:1892: error: for each function it appears in.) Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-02-15omap2/3/4: Add omap4 into omap3_defconfigTony Lindgren1-1/+5
Add omap4 into omap3_defconfig. Note that this does not yet boot on omap4, but boots on omap2 and omap3. Also note that CONFIG_SMP does not currently work on uniprocessor ARMs. Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-02-15omap2/3: Update omap3_defconfig to build in all the 2420 based boardsTony Lindgren1-36/+138
Note that booting 2420 depends on another patch posted earlier to not select CONFIG_CPU_32v6K if CONFIG_ARCH_OMAP2 is selected. Also note that we cannot add omap2430 in yet because of the different clock addresses compared to 2420. Also note that we cannot have CONFIG_CPU_32v6K=y in order to boot on 24xx. Signed-off-by: Tony Lindgren <tony@atomide.com>
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-12-03arm: omap: Add omap3_defconfigOlof Johansson1-0/+2119
Having one combined defconfig that is the superset of the individual defconfigs for OMAP3 platforms is useful for easily finding build errors. Not to mention convenient as a base if you want to boot several platforms with a single kernel image. Signed-off-by: Olof Johansson <olof@lixom.net> Signed-off-by: Tony Lindgren <tony@atomide.com>