From: "Jan Lübbe" <jlu@pengutronix.de>
To: Uladzimir Bely <u.bely@sam-solutions.net>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: OMAP5 processors support
Date: Fri, 26 Apr 2013 12:54:42 +0200 [thread overview]
Message-ID: <1366973682.4158.142.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <517A57F8.8020805@sam-solutions.net>
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
next prev parent reply other threads:[~2013-04-26 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <014261>
2013-04-24 10:33 ` Uladzimir Bely
2013-04-24 10:51 ` Uladzimir Bely
2013-04-24 20:11 ` Sascha Hauer
2013-04-25 9:09 ` Uladzimir Bely
2013-04-25 11:05 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-25 11:58 ` Jan Lübbe
2013-04-25 12:42 ` Uladzimir Bely
2013-04-25 20:47 ` Sascha Hauer
2013-04-26 8:31 ` Jan Lübbe
[not found] ` <517A57F8.8020805@sam-solutions.net>
2013-04-26 10:54 ` Jan Lübbe [this message]
2013-04-26 10:59 ` Uladzimir Bely
2013-04-26 21:58 ` Sascha Hauer
2013-04-25 13:31 ` menon.nishanth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1366973682.4158.142.camel@coredoba.hi.pengutronix.de \
--to=jlu@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=u.bely@sam-solutions.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox