From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] Add Armada 385 General Purpose Development Board support
Date: Mon, 05 Jan 2015 15:36:09 +0100 [thread overview]
Message-ID: <54AAA159.4040901@free-electrons.com> (raw)
In-Reply-To: <20141231105720.24e6983f@free-electrons.com>
Hi Thomas,
On 31/12/2014 10:57, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> On Sat, 27 Dec 2014 12:00:32 +0100, Gregory CLEMENT wrote:
>
>> this patch set adds the support for the Armada 385 GP board, this board
>> is pretty close to the Armada 385 RD one. It comes with a new revision
>> of the Armada 385 SoC (B0).
>
> Unless I'm wrong, it actually comes with an A0 revision, not a B0. But
> it's indeed different from the Z1 revision we have been using until now.
>
> At least, my Armada XP GP says:
>
> Board: DB-88F6820-GP
> SoC: MV88F6828 Rev A0
You're right I wen too far in the revision, it was A0.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2015-01-05 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 11:00 [PATCH 0/3] Add Armada 385 General Purpose Development Board support Gregory CLEMENT
2014-12-27 11:00 ` [PATCH 1/3] ARM: mvebu: a38x: Fix node names Gregory CLEMENT
2014-12-27 11:00 ` [PATCH 2/3] ARM: mvebu: a38x: Add the pinctrl alias Gregory CLEMENT
2014-12-27 11:29 ` Andrew Lunn
2014-12-27 14:46 ` Sergei Shtylyov
2014-12-27 11:00 ` [PATCH 3/3] ARM: mvebu: Add Armada 385 General Purpose Development Board support Gregory CLEMENT
2014-12-27 11:34 ` Andrew Lunn
2015-01-05 14:03 ` Gregory CLEMENT
2015-01-05 14:24 ` Andrew Lunn
2014-12-27 11:50 ` Andrew Lunn
2015-01-05 14:34 ` Gregory CLEMENT
2014-12-31 10:32 ` Thomas Petazzoni
2015-01-05 17:06 ` Gregory CLEMENT
2014-12-31 9:57 ` [PATCH 0/3] " Thomas Petazzoni
2015-01-05 14:36 ` Gregory CLEMENT [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=54AAA159.4040901@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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