From: Sascha Hauer <s.hauer@pengutronix.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Anybody working on Samsung S3C64xx support
Date: Wed, 28 Sep 2011 19:55:00 +0200 [thread overview]
Message-ID: <20110928175459.GB31404@pengutronix.de> (raw)
In-Reply-To: <201109281458.09005.jbe@pengutronix.de>
On Wed, Sep 28, 2011 at 02:58:08PM +0200, Juergen Beisert wrote:
> Myself wrote:
> > is anybody working on Barebox support for the ARM11 based S3C6410 CPU from
> > Samsung (just to be sure to not re-invent the wheel)?
>
> When adding the S3C6410 CPU support: Should I try to extend the existing
> S3C24xx family (its uses an ARMv4 core) with the ARMv6 core S3C64xx family,
> or better a separate mach-* directory? Both CPUs sharing some peripherals,
> but with many little differences (known from i.MX...)
I would recommend the same directory. The core v6 vs. v6 is irrelevant
for the port and the fact that they share peripherals suggests that it's
not that different from the older Samgsungs. What does the kernel do?
Sascha
--
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:[~2011-09-28 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:16 Juergen Beisert
2011-09-28 12:58 ` Juergen Beisert
2011-09-28 17:55 ` Sascha Hauer [this message]
2011-09-29 6:29 ` Juergen Beisert
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=20110928175459.GB31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jbe@pengutronix.de \
/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