From: florian@openwrt.org (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Add support for generic BCM SoC chipsets
Date: Sun, 11 Nov 2012 16:53:42 +0100 [thread overview]
Message-ID: <12188358.5I1Xcz160E@bender> (raw)
In-Reply-To: <1352645834-10173-1-git-send-email-csd@broadcom.com>
Hi Christian,
On Sunday 11 November 2012 06:57:14 Christian Daudt wrote:
> In order to start upstreaming Broadcom SoC support, create
> a starting hierarchy, arch and dts files.
> The first support SoC family that is planned is the
> BCM281XX (BCM28145/28150/28155/28160) 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.
> Next steps
> ----------
> Upstream a basic set of drivers - sufficient for a console boot to
> ramdisk. These will includer timer, gpio, i2c drivers.
> After this basic set, we will proceed with a more comprehensive set
> of drivers for the 281XX SoC family.
Would not it make more sense to use mach-bcm281xx as a directory name instead
of mach-bcm which sounds a tad too generic? This would also make it consistent
with Domenico's mach-bcm47xx and the existing bcm47xx and bcm63xx MIPS-based
SoC support.
--
Florian
next prev parent reply other threads:[~2012-11-11 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 14:57 [PATCH v2] Add support for generic BCM SoC chipsets Christian Daudt
2012-11-11 15:53 ` Florian Fainelli [this message]
2012-11-11 17:32 ` Christian Daudt
2012-11-11 18:43 ` Florian Fainelli
2012-11-11 21:40 ` Stephen Warren
2012-11-12 15:00 ` Arnd Bergmann
2012-11-12 16:04 ` Domenico Andreoli
2012-11-12 17:05 ` Arnd Bergmann
2012-11-12 17:15 ` Stephen Warren
2012-11-13 17:53 ` Christian Daudt
2012-11-13 21:31 ` Domenico Andreoli
2012-11-12 15:17 ` Russell King - ARM Linux
2012-11-13 17:58 ` Christian Daudt
2012-11-13 4:45 ` Stephen Warren
2012-11-13 19:02 ` 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=12188358.5I1Xcz160E@bender \
--to=florian@openwrt.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).