From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] arm: add documentation describing Marvell families of SoC
Date: Sat, 4 Aug 2012 22:59:38 +0200 [thread overview]
Message-ID: <20120804225938.6d44a9af@skate> (raw)
In-Reply-To: <CAMPhdO8jiTwfdk0DkhjdwMbH3Mt6=XXZKhwNH412UfNbodu7Ww@mail.gmail.com>
Hello Eric,
Thanks for all those details! Some comments below.
Le Wed, 18 Jul 2012 02:01:51 +0800,
Eric Miao <eric.y.miao@gmail.com> a ?crit :
> This is so useful to Marvell processor new comers, thanks everyone to
> compile this.
>
> The PXA side might need a bit modification though, so for historical
> reason there is PXA series as originated back from Intel. So there
> are really those legacy ones:
>
> PXA21x/PXA25x/PXA27x/PXA3xx/PXA93x
>
> The new ones developed after Marvell acquired Intel's XScale biz are:
>
> PXA95x/PXA168/PXA910/MMP2
>
> And among these, they are actually categorized into two flavors:
>
> AP with CP: PXA93x/PXA95X/PXA910
> AP only without CP: the rest of them
>
> And the ARM cores used are also a bit different:
>
> XScale (Intel's ARMv5te compatible):
> PXA21x/PXA25x/PXA27x/PXA3xx/PXA93x Marvell's PJ1 (Marvell's ARMv5te
> compatible): PXA168/PXA910 Marvell's PJ4 (Marvell's ARMv7
> compatible): PXA95x/MMP2
Great, I included all those informations in some form. Will be part of
v3.
> So these are really a bit complicated, by the end of the day, we
> would still go the way as Arnd suggested, that to collapse PXA and
> MMP series into one, so that will be simpler and easier to understand.
>
> Considering the complications here, I would suggest to simply have a
> single processor line as: PXA/MMP processor line, and list all the
> processor flavors under, whether it's an AP or a AP+CP could be
> individually indicated.
For now, I prefer to keep those as two separate families, so that it
reflects the *current* state of the Linux mach-* directories. The
current state may not be perfect, but it's the current state, so let's
reflect it for now.
Thanks again for your comments!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-08-04 20:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 14:26 [PATCH] [RFC] arm: add documentation describing Marvell families of SoC Thomas Petazzoni
2012-07-17 14:59 ` Andrew Lunn
2012-07-17 15:37 ` Thomas Petazzoni
2012-07-17 15:09 ` Arnd Bergmann
2012-07-17 15:40 ` Thomas Petazzoni
2012-07-17 16:52 ` Andrew Lunn
2012-07-17 15:45 ` Nicolas Pitre
2012-07-17 18:58 ` Nicolas Pitre
2012-08-04 21:01 ` Thomas Petazzoni
2012-07-17 15:35 ` [PATCH v2] " Thomas Petazzoni
2012-07-17 18:01 ` [PATCH] " Eric Miao
2012-07-17 18:05 ` Andrew Lunn
2012-07-17 18:08 ` Eric Miao
2012-07-17 18:35 ` Thomas Petazzoni
2012-07-17 18:50 ` Eric Miao
2012-08-04 20:59 ` Thomas Petazzoni [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=20120804225938.6d44a9af@skate \
--to=thomas.petazzoni@free-electrons.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.