From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add Armada 385 General Purpose Development Board support
Date: Wed, 31 Dec 2014 10:57:20 +0100 [thread overview]
Message-ID: <20141231105720.24e6983f@free-electrons.com> (raw)
In-Reply-To: <1419678035-10658-1-git-send-email-gregory.clement@free-electrons.com>
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
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-31 9:57 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 ` Thomas Petazzoni [this message]
2015-01-05 14:36 ` [PATCH 0/3] " Gregory CLEMENT
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=20141231105720.24e6983f@free-electrons.com \
--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 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).