linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kmpark@infradead.org (Kyungmin Park)
To: linux-arm-kernel@lists.infradead.org
Subject: Discussion request for new Samsung SoCs maintaining
Date: Mon, 7 Sep 2009 22:24:48 +0900	[thread overview]
Message-ID: <9c9fda240909070624q33bda480g17aabcfa452578d0@mail.gmail.com> (raw)
In-Reply-To: <20090901133812.GP19719@n2100.arm.linux.org.uk>

hi,

On Tue, Sep 1, 2009 at 10:38 PM, Russell King - ARM
Linux<linux@arm.linux.org.uk> wrote:
> On Thu, Aug 27, 2009 at 07:44:32AM -0500, Bill Gatliff wrote:
>> I'm not sure I have any useful suggestion for this part. ?It would have
>> been nice to have a "mach-a8" and "mach-arm11" for these situations,
>
> A8 and ARM11 are CPU types and we already have a perfectly good
> abstraction for these. ?Should the Realview ARM11 end up in mach-arm11
> and the Realview Cortex A8 end up in mach-a8? ?Clearly, it's just
> wrong.

How about to finish the this issues.
Even though Ben don't give any opinion, we have to decide how to add
next new SoCs and drivers.

First, decide the proper platform directory.
1. use the plat-s3c,
2. rename plat-samsung or
3. create new plat-samsung.

Second, who maintains the new SoCs?
1. maintain the all samsung SoCs as before by Ben
2. maintain s3c24xx and s3c64xx by Ben. others (s5pc1xx series) by Samsung.

Please give your opinions.

Thank you,
Kyungmin Park

  reply	other threads:[~2009-09-07 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 11:06 Discussion request for new Samsung SoCs maintaining Jinsung Yang
2009-08-27 12:44 ` Bill Gatliff
2009-08-28  3:19   ` Harald Welte
2009-09-01 13:38   ` Russell King - ARM Linux
2009-09-07 13:24     ` Kyungmin Park [this message]
2009-09-07 17:53       ` Peter Korsgaard
2009-09-29  9:32   ` Ben Dooks
2009-08-27 13:14 ` Mark Brown
2009-08-28  3:27   ` Harald Welte
2009-08-28 12:45     ` Mark Brown
2009-08-27 13:57 ` David F. Carlson
2009-08-28  3:34   ` Harald Welte

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=9c9fda240909070624q33bda480g17aabcfa452578d0@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).