From: hechtb@gmail.com (Bastian Hecht)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: shmobile: armadillo800eva: Reference DT implementation
Date: Wed, 9 Jan 2013 17:13:15 +0100 [thread overview]
Message-ID: <CABYn4sxsSMSosAVT8DZDupNP9m-vQN+88R2nyC58L-tcNW044Q@mail.gmail.com> (raw)
In-Reply-To: <20130109020712.GC6496@verge.net.au>
Hi Simon,
2013/1/9 Simon Horman <horms@verge.net.au>:
> On Tue, Dec 18, 2012 at 06:22:39PM +0100, Bastian Hecht wrote:
>> Provide alternate board code for the Armadillo 800 EVA to
>> demonstrate how DT may be used given the current state of
>> driver device tree support. This is intended to act as a
>> reference for mach-shmobile developers.
>>
>> This is based on Simon Horman's reference implementation for
>> the board kzm9g.
>>
>> Currently only the ethernet controller is brought up.
>
> Thanks, looks good. I will apply this.
Thanks!
> Could you let me know what the status of
> the DT bindings for sh-eth is?
I used the bindings that comply to the patch "[v2,1/2] net: sh_eth:
Add support of device tree probe" from 10/16/2012 from Iwamatsu-san. I
hasn't found its way into v3.8-rc2 yet and I don't know anything more
accurate about the merge process.
Cheers,
Bastian
prev parent reply other threads:[~2013-01-09 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 17:22 [PATCH 0/2] Armadillo DT Reference Implementation Bastian Hecht
2012-12-18 17:22 ` [PATCH 1/2] ARM: r8a7740: Add interim sh-eth device name to clocks list Bastian Hecht
2012-12-19 9:10 ` Guennadi Liakhovetski
2012-12-19 10:50 ` Magnus Damm
2013-01-09 2:06 ` Simon Horman
2013-04-11 3:09 ` Simon Horman
2012-12-18 17:22 ` [PATCH 2/2] ARM: shmobile: armadillo800eva: Reference DT implementation Bastian Hecht
2013-01-09 2:07 ` Simon Horman
2013-01-09 16:13 ` Bastian Hecht [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=CABYn4sxsSMSosAVT8DZDupNP9m-vQN+88R2nyC58L-tcNW044Q@mail.gmail.com \
--to=hechtb@gmail.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).