On Fri, 2013-04-26 at 13:33 +0300, Uladzimir Bely wrote: > >> diff --git a/arch/arm/mach-omap/Kconfig b/arch/arm/mach-omap/Kconfig > >> index 42e5f4a..0ad3864 100644 > >> --- a/arch/arm/mach-omap/Kconfig > >> +++ b/arch/arm/mach-omap/Kconfig > >> @@ -41,6 +41,14 @@ config ARCH_OMAP4 > >> help > >> Say Y here if you are using Texas Instrument's OMAP4 based platform > >> > >> > >> +config MACH_OMAP5_SEVM > >> + bool "Phytec phyCORE omap5_sevm" > >> + depends on ARCH_OMAP5 > >> + help > >> + Say Y here if you are using Phytecs phyCORE omap5_sevm board > >> + based on OMAP5 > >> + > >> config MACH_PCM051 > >> bool "Phytec phyCORE pcm051" > >> select OMAP_CLOCK_ALL > > > > Isn't the OMAP5 sEVM from TI? > > > > This question is more complicated. We use Phytec phyCORE OMAP4 board, but > with OMAP5 SOC installed. We used omap5_sevm with number 3777 which already > exists in arch/arm/tools. Kernel also was compiled for this mach-type.
So the board which you use for development is not generally available. Maybe you could call it something like "MACH_PCM049_OMAP5" or "MACH_PHYCORE_OMAP5_EVAL"...? > As I understand, new board (Phytec phyCORE OMAP5) must be added to this file > (http://www.arm.linux.org.uk/developer/machines/download.php) first, and > barebox > will use this updated file for this board too. Am I right? How can I add new > board here correctly? To request a new machine ID, use http://www.arm.linux.org.uk/developer/machines/?action=new Note that new legacy (non-Device-Tree) boards are no longer accepted into the kernel! For DT-only boards no machine ID is needed at all. Regards, Jan Lübbe -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
