From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Marvell Orion5x boards with PCIe, and DT conversion
Date: Sun, 13 Apr 2014 18:55:20 +0200 [thread overview]
Message-ID: <20140413185520.5f9e7165@skate> (raw)
In-Reply-To: <53480402.5030101@free.fr>
Dear Albert ARIBAUD,
On Fri, 11 Apr 2014 17:02:26 +0200, Albert ARIBAUD wrote:
> I'll gladly test these patches on my faithful Orion ED Mini V2. Not sure
> if it uses PCIe, but I suspect it does not.
Thanks for the proposal. Unfortunately, it turns out that the Orion ED
Mini V2 is one of the two boards I already have, so I can test on this
one. However, it would definitely be useful to have your testing and
feedback.
I've posted the patch series on LAKML just a few hours ago, you can
also grab the code from:
https://github.com/MISL-EBU-System-SW/mainline-public/tree/3.15/orion
In this branch, Orion ED Mini v2 is fully converted to the Device Tree.
> How does this play out with U-Boot? I mean, I know that you can produce
> a kernel which embeds the device tree and will load without U-Boot
> knowing anything about them, but OTOH, U-Boot has some support for DTs,
> and could possibly use the DT files too.
For now, I'm using the U-Boot included with the boards, so it does not
have FDT support, which means I'm using appended DTBs.
Do you know if UART booting works for Orion boards? If not, what is the
recovery mechanism if you screw up while reflashing U-Boot?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-13 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 13:57 Marvell Orion5x boards with PCIe, and DT conversion Thomas Petazzoni
2014-04-11 15:02 ` Albert ARIBAUD
2014-04-12 2:48 ` Chris Moore
2014-04-13 16:58 ` Thomas Petazzoni
2014-04-13 16:55 ` Thomas Petazzoni [this message]
2014-04-13 17:36 ` Alexander Clouter
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=20140413185520.5f9e7165@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox