From: bgat@billgatliff•com (Bill Gatliff)
To: linux-arm-kernel@lists•infradead.org
Subject: devicetree in arm
Date: Thu, 18 Mar 2010 15:24:23 -0500 [thread overview]
Message-ID: <4BA28BF7.2080403@billgatliff.com> (raw)
In-Reply-To: <20100318132358.GE19544@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Thu, Mar 18, 2010 at 07:14:05AM -0600, Grant Likely wrote:
>
>> ARM device tree support is very much in flux, and that particular
>> branch gets rebased a lot as device tree code from Sparc, Microblaze
>> and Powerpc is merged into drivers/of. I may have ended up pushing
>> out to test-devicetree without the ARM patches applied. I'll look at
>> it today, make sure the ARM stuff is all there, and then push it out
>> again.
>>
>> Note however that this is only very basic support. It doesn't yet
>> have the code needed to register devices and drivers from device tree
>> data. That will be coming real-soon-now.
>>
>
> Is someone going to do a device tree example port to a 'real' platform
> rather than simple the ARM evaluation boards?
>
> As I've said previously, I'm not going to accept device tree stuff until
> I see a working implementation on a set of real platforms.
>
I can give it a spin on a couple of the boards I have here. I'm already
using device trees on my PPC platforms.
b.g.
--
Bill Gatliff
bgat at billgatliff.com
next prev parent reply other threads:[~2010-03-18 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 12:04 devicetree in arm Mark Ryden
2010-03-18 13:14 ` Grant Likely
2010-03-18 13:23 ` Russell King - ARM Linux
2010-03-18 13:45 ` Armando VISCONTI
2010-03-18 13:54 ` Grant Likely
2010-03-18 14:10 ` Jason McMullan
2010-03-18 20:24 ` Bill Gatliff [this message]
2010-04-08 6:31 ` Grant Likely
2010-04-08 6:41 ` Bryan Wu
2010-04-08 6:58 ` Grant Likely
2010-04-08 7:23 ` Jeremy Kerr
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=4BA28BF7.2080403@billgatliff.com \
--to=bgat@billgatliff$(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