From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC
Date: Wed, 13 Jun 2012 15:24:26 +0000 [thread overview]
Message-ID: <201206131524.26653.arnd@arndb.de> (raw)
In-Reply-To: <4FD8AC5E.1060804@redhat.com>
On Wednesday 13 June 2012, Jon Masters wrote:
> On 06/11/2012 12:52 PM, Gregory CLEMENT wrote:
>
> > You'll find in this patch set the new version of the initial support for a
> > new family of ARMv7-compatible Marvell SoCs initially submitted by my
> > colleague Thomas Petazzoni. Following the conclusion of the discussion when
> > we submitted our first version we have chosen to add this support for this
> > SoC family in the to support in the arch/arm/mach-mvebu/ directory.
>
> Pardon my silly question. I know that there's an effort to reconcile the
> two different SoCs so you're picking a neutral name, but what does
> "mvebu" mean, and will you be persistently keeping this name? Our guys
> want to know what this new platform will entail for Fedora support in
> terms of the platform name being used in various non-kernel places.
We've had an extended discussion about the name when the patches
were posted for the first time. It was just the best thing that anyone
suggested so far given the alternatives.
"EBU" is the business unit that makes all the SoCs in this family
(orion, kirkwood, armadaxp, dove, ...) and no other name that was
suggested covers all of these but not also at least some of the other
Marvell SoCs (pxa, mmp, armada1000, ...).
Just "ebu" would not be very clear, and other variations (mv-ebu,
mrvl-ebu) were considered to be too long.
Arnd
next prev parent reply other threads:[~2012-06-13 15:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 16:52 [PATCH v2] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Gregory CLEMENT
2012-06-11 16:52 ` [PATCH v2 1/8] arm: mach-mvebu: add header Gregory CLEMENT
2012-06-11 17:11 ` Andrew Lunn
2012-06-11 16:52 ` [PATCH v2 2/8] arm: mach-mvebu: add source files Gregory CLEMENT
2012-06-12 8:45 ` Arnd Bergmann
2012-06-12 12:56 ` Gregory CLEMENT
2012-06-12 13:35 ` Arnd Bergmann
2012-06-12 15:50 ` Nicolas Pitre
2012-06-11 16:53 ` [PATCH v2 3/8] arm: mach-mvebu: add compilation/configuration change Gregory CLEMENT
2012-06-12 8:39 ` Arnd Bergmann
2012-06-12 13:01 ` Gregory CLEMENT
2012-06-11 16:53 ` [PATCH v2 4/8] arm: mach-mvebu: add support for Armada 370 and Armada XP with DT Gregory CLEMENT
2012-06-12 13:09 ` Arnd Bergmann
2012-06-11 16:53 ` [PATCH v2 5/8] arm: mach-mvebu: add documentation for new device tree bindings Gregory CLEMENT
2012-06-11 16:53 ` [PATCH v2 6/8] arm: mach-mvebu: add defconfig Gregory CLEMENT
2012-06-11 16:53 ` [PATCH v2 7/8] arm: mach-mvebu: add entry to MAINTAINERS Gregory CLEMENT
2012-06-11 16:53 ` [PATCH v2 8/8] ARM: mvebu: MPIC: read number of interrupts from control register Gregory CLEMENT
2012-06-11 20:44 ` [PATCH v2] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC David Marlin
2012-06-12 7:35 ` Gregory CLEMENT
2012-06-12 8:04 ` Andrew Lunn
2012-06-12 8:09 ` Arnd Bergmann
2012-06-12 13:49 ` Arnd Bergmann
2012-06-12 13:56 ` Gregory CLEMENT
2012-06-12 14:06 ` Andrew Lunn
2012-06-12 14:24 ` Jason Cooper
2012-06-12 14:59 ` Arnd Bergmann
2012-06-12 15:40 ` Jason Cooper
2012-06-12 17:39 ` Arnd Bergmann
2012-06-13 16:14 ` Thomas Petazzoni
2012-06-13 19:19 ` Arnd Bergmann
2012-06-13 15:06 ` Jon Masters
2012-06-13 15:14 ` Gregory CLEMENT
2012-06-13 15:24 ` Arnd Bergmann [this message]
2012-06-13 15:48 ` Jason Cooper
2012-06-13 16:12 ` Arnaud Patard (Rtp)
2012-06-13 15:56 ` Nicolas Pitre
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=201206131524.26653.arnd@arndb.de \
--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 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.