From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 0/6] mvebu multi SoC support
Date: Fri, 19 Sep 2014 10:25:08 +0200 [thread overview]
Message-ID: <541BE864.4030609@gmail.com> (raw)
In-Reply-To: <20140919075542.GF4992@pengutronix.de>
On 09/19/2014 09:55 AM, Sascha Hauer wrote:
> On Fri, Sep 19, 2014 at 08:44:09AM +0200, Sebastian Hesselbarth wrote:
>> On 09/19/2014 07:47 AM, Sascha Hauer wrote:
>>> On Wed, Sep 17, 2014 at 10:22:38PM +0200, Sebastian Hesselbarth wrote:
>>>> This is v2 of the Multi-SoC series for MVEBU. It has been tested
>>>> on Kirkwood (Guruplug), Dove (CuBox), and Armada 370 (Mirabox)
>>>> with the very same non-EABI binary. It should also work on Armada
>>>> XP but I cannot test right now.
>>>
>>> Do you want to give it a test on Armada XP before I apply this series or
>>> are you fine with this without testing it on Armada XP?
>>
>> I just tested it on Lenovo ix4-300d with Armada XP MV78230-A0, so feel
>> free to pick it up.
>
> Cool, just did that. Are you fine with removing the board specific
> configs now that we have a mvebu_defconfig?
Yes, please. As you already pointed out, the board specific configs are
horribly out-dated and should be nuked.
>> If I find some time, I'll polish ix4-300d patches and send them, too.
>
> Nice.
It may also include deferred probing support as the ix4-300d has a gpio
attached gpio-expander (aka 74HC138) with LEDs. And as you may guess,
requesting GPIOs from that expander which needs GPIOs itself does not
quite work yet.
I have it running, the deferred probing is simple, but I'll have to
review the whole set first (and sync with Linux dts of ix4).
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-09-19 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 20:22 [PATCH v2 0/6] mvebu multi SoC support Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 1/6] ARM: mvebu: Add common reset_cpu function Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 2/6] ARM: mvebu: Add machine compatible to mbus ranges Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 3/6] ARM: mvebu: Simplify memory init order Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 4/6] ARM: mvebu: Check for correct SoC in of_fixup callback Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 5/6] ARM: mvebu: Allow multiple SoCs Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 6/6] ARM: Add mvebu_defconfig Sebastian Hesselbarth
2014-09-20 17:24 ` Sebastian Hesselbarth
2014-09-23 5:58 ` Sascha Hauer
2014-09-19 5:47 ` [PATCH v2 0/6] mvebu multi SoC support Sascha Hauer
2014-09-19 6:44 ` Sebastian Hesselbarth
2014-09-19 7:55 ` Sascha Hauer
2014-09-19 8:25 ` Sebastian Hesselbarth [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=541BE864.4030609@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.