summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/Kconfig
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2015-05-04 19:45:54 +0200
committerTony Lindgren <tony@atomide.com>2015-05-06 18:27:53 +0200
commitd203c5747e88f053e4ee373a939c05914c82eb1c (patch)
tree6dc3e8dcc172277e627752b9e24a948d7a673bdc /arch/arm/mach-omap2/Kconfig
parentARM: OMAP2+: Remove legacy booting support for Overo (diff)
downloadlinux-d203c5747e88f053e4ee373a939c05914c82eb1c.tar.xz
linux-d203c5747e88f053e4ee373a939c05914c82eb1c.zip
ARM: OMAP2+: Remove legacy booting support for Beagleboards
We've been moving all omap2+ based systems to boot in device tree only mode for a few years now. Only omap3 has legacy booting support remaining. Most omap3 boards already have related arch/arm/boot/*.dts* files for booting with device tree. This board has support for device tree based booting, and we've been printing warnings about the legacy booting being deprecated for a few merge cycles now. Let's attempt to remove the legacy booting for it. The reason for removing the legacy booting support now rather than later is we can simply revert this patch if necessary if we run into some unexpected issues that are not trivial to fix for the device tree based booting. Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/Kconfig')
-rw-r--r--arch/arm/mach-omap2/Kconfig6
1 files changed, 0 insertions, 6 deletions
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 1b8a45a4642a..ecc04ff13e95 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -171,12 +171,6 @@ config MACH_OMAP2_TUSB6010
depends on ARCH_OMAP2 && SOC_OMAP2420
default y if MACH_NOKIA_N8X0
-config MACH_OMAP3_BEAGLE
- bool "OMAP3 BEAGLE board"
- depends on ARCH_OMAP3
- default y
- select OMAP_PACKAGE_CBB
-
config MACH_OMAP_LDP
bool "OMAP3 LDP board"
depends on ARCH_OMAP3