From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: LPC43xx
Date: Mon, 17 Nov 2014 15:20:52 +0300 [thread overview]
Message-ID: <1416226852.621003559@f175.i.mail.ru> (raw)
In-Reply-To: <5469E37E.7080803@vanguardiasur.com.ar>
Mon, 17 Nov 2014 09:01:02 -0300 от Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>:
>
>
> On 11/17/2014 04:39 AM, Alexander Shiyan wrote:
> > Sun, 16 Nov 2014 18:35:23 -0300 от Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>:
> >> Hi Alexander,
> >>
> >> On 10/21/2014 01:34 PM, Alexander Shiyan wrote:
> >>> Hello all.
> >>>
> >>> We started developing device which uses NXP LPC43xx CPU. I would like to add
> >>> support for this CPU series into barebox.
> >>> The problem is that there is no support for this architecture in the Linux kernel,
> >>> and it would upset the current concept (the barebox tree is very similar to Linux
> >>> tree and we not have any orphan arch-s).
> >>
> >> I'm working on the upstream Linux port for LPC43xx SoCs. The obvious
> >> choice would be mach-lpc43xx. The problem is that LPC18xx are similar
> >> SoCs, and I think it would make sense to have them in the same mach-xxx.
> >> Haven't made up my mind on this issue, and I suspect we won't find out
> >> until we push some patches upstream.
> >>
> >> Anyway, if you make any progress with the barebox port, I'd be happy to
> >> take a look and help you test it.
> >
> > The kernel has existing mach-lpc32xx architecture. I think it would be appropriate
> > to rename it to mach-lpc and move the CPU-specific options in the local KConfig as first step.
> >
>
> LPC3xxx is ARMv5 based while LPC4xxx and LPC1xxx are ARMv7-M based.
This should not be a problem. Look at the i.MX architecture, this contain v4, v5, v7 CPUs.
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-11-17 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 16:34 LPC43xx Alexander Shiyan
2014-10-22 6:41 ` LPC43xx Uwe Kleine-König
2014-10-22 7:50 ` LPC43xx Sascha Hauer
2014-11-16 21:35 ` LPC43xx Ezequiel Garcia
2014-11-17 7:39 ` LPC43xx Alexander Shiyan
2014-11-17 12:01 ` LPC43xx Ezequiel Garcia
2014-11-17 12:20 ` Alexander Shiyan [this message]
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=1416226852.621003559@f175.i.mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
/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