All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC
Date: Tue, 12 Jun 2012 10:04:18 +0200	[thread overview]
Message-ID: <20120612080418.GC3221@lunn.ch> (raw)
In-Reply-To: <4FD6F15E.4080000@free-electrons.com>

On Tue, Jun 12, 2012 at 09:35:58AM +0200, Gregory CLEMENT wrote:
> On 06/11/2012 10:44 PM, David Marlin wrote:
> > 
> > I noticed that you are using mach-mvebu in these patches.  I have seen 
> > these machines referred to as 'armada', 'axp', 'armadaxp', etc.  Will 
> > 'mvebu' be the official machine name to use for these systems?  I'm 
> > looking for a 'name' to identify the common kernel for these systems. 
> > For reference, the names of the ARM kernels we are currently building in 
> > Fedora include: 'highbank', 'imx', 'kirkwood', 'omap', and 'tegra'.
> > 
> > 
> > Thank you,
> > 
> > d.marlin
> > ===========
> > 
> 
> Hello David,
> 
> Mvebu is aimed to be the official name for the all the SOC with device tree
> support coming out of Marvell's EBU division. As stated Nicolas Pitre: "One
> thing that is common to Orion/Kirkwood/Dove/(insert some Armada flavours
> here)/etc though is that they came out of Marvell's EBU division."
> 
> For the beginning only Armada XP and Armada 370 are in this directory but as
> son as the other Marvell architectures will be converted to device tree they
> will be moved to mach-mvebu.

So it still seems like we have a naming issue. We have given a usable
name to the directory. But what do we call the kernel? This is what
David wants to know. When we have moved the DT enabled architectures
into mach-mvebu, they are still likely to build a ARMv5 kernel for
Kirkwood and Orion5x, and a ARMv7 kernel for Dove plus these two new
SoCs. But what do we call this new kernel?

      Andrew

  reply	other threads:[~2012-06-12  8:04 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 [this message]
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
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=20120612080418.GC3221@lunn.ch \
    --to=andrew@lunn.ch \
    --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.