public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: add support for BCM2708/BCM2835 and Raspberry Pi
Date: Sat, 08 Sep 2012 19:27:47 +0000	[thread overview]
Message-ID: <9292467.5Y4vCKkKhh@wuerfel> (raw)
In-Reply-To: <504B8359.80403@wwwdotorg.org>

On Saturday 08 September 2012 11:41:45 Stephen Warren wrote:
> On 09/08/2012 06:37 AM, Simon Arlott wrote:
> > On 08/09/12 06:48, Stephen Warren wrote:
> 
> > I don't know what you're trying to achieve. This does not add support
> > for the BCM2708.
> 
> I'm trying to get upstreaming started, a little bit at a time. Right
> now, all work has been done outside the regular Linux ARM community. I
> feel it'd be much better to start feeding the work upstream. This will
> provide much better exposure for the work, and put it into a place
> that's more obvious for users, and useful for distros.
> 
> Obviously, the next step after this patch is to upstream the interrupt
> controller and timer, to resolve the problem mentioned above. There's
> certainly still much more to do after that.

I think it would be good to get those reviewed and submitted in time for
the merge window, to have something that actually boots.

I agree that for review purposes starting out with just the minimal patch
was a good idea, but when the other stuff looks reasonable, we should also
try to get it in at the same time.

	Arnd

      reply	other threads:[~2012-09-08 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  5:48 [PATCH V2] ARM: add support for BCM2708/BCM2835 and Raspberry Pi Stephen Warren
2012-09-08 12:37 ` Simon Arlott
2012-09-08 16:25   ` Seth Jennings
2012-09-08 17:41   ` Stephen Warren
2012-09-08 19:27     ` Arnd Bergmann [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=9292467.5Y4vCKkKhh@wuerfel \
    --to=arnd@arndb.de \
    --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