All of lore.kernel.org
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add support for generic BCM SoC chipsets
Date: Fri, 9 Nov 2012 08:49:14 +0100	[thread overview]
Message-ID: <20121109074913.GA25257@glitch> (raw)
In-Reply-To: <509C7771.9020400@wwwdotorg.org>

Hi Christian,

On Thu, Nov 08, 2012 at 08:24:33PM -0700, Stephen Warren wrote:
> On 11/08/2012 09:13 AM, Christian Daudt wrote:
> > In order to start upstreaming Broadcom SoC support, create
> > a starting hierarchy, arch and dts files.
> >

Glad to know that Broadcom is interested in mainline :)

> > The first support SoC family that is planned is the
> >  BCM281XX (BCM28145/28150/28155) family of dual A9 mobile SoC cores
> > This code is just the skeleton code for get the machine upstreamed. It
> > has been made MULTIPLATFORM compatible.
> 
> Is the intent for this to support other BCM SoCs in the future, such as
> the bcm2835 in the Raspberry Pi, and the mach-bcm476x which Domenico
> Andreoli recently sent patches for? It'd be awesome if Broadcom could
> provide MMC and USB drivers for the bcm2835 for example.

I'd love to see published some more documentation as well.

Regards,
Domenico

  reply	other threads:[~2012-11-09  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 16:13 [PATCH] Add support for generic BCM SoC chipsets Christian Daudt
2012-11-09  3:24 ` Stephen Warren
2012-11-09  7:49   ` Domenico Andreoli [this message]
2012-11-11 13:34   ` Christian Daudt
2012-11-11 21:38     ` Stephen Warren
2012-12-05  3:35     ` Stephen Warren
2012-12-05  8:36       ` Christian Daudt

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=20121109074913.GA25257@glitch \
    --to=cavokz@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.