summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/board-omap3beagle.c
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2015-05-04 19:49:36 +0200
committerTony Lindgren <tony@atomide.com>2015-05-04 19:58:29 +0200
commit71115b30a3f55ceb52e41d80c6101960248195d1 (patch)
tree5baff10c4ab254a750aa46ac812f1d819c84a940 /arch/arm/mach-omap2/board-omap3beagle.c
parentARM: OMAP2+: Remove legacy booting support for cm-t35 (diff)
downloadlinux-71115b30a3f55ceb52e41d80c6101960248195d1.tar.xz
linux-71115b30a3f55ceb52e41d80c6101960248195d1.zip
ARM: OMAP2+: Remove legacy booting support for Overo
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. Cc: Florian Vaussard <florian.vaussard@epfl.ch> Acked-by: Ash Charles <ashcharles@gmail.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/board-omap3beagle.c')
0 files changed, 0 insertions, 0 deletions