All of lore.kernel.org
 help / color / mirror / Atom feed
From: bryan.wu@canonical.com (Bryan Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: devicetree in arm
Date: Thu, 08 Apr 2010 14:41:30 +0800	[thread overview]
Message-ID: <4BBD7A9A.9090501@canonical.com> (raw)
In-Reply-To: <k2tfa686aa41004072331p7541292ajc35521cf24fd24c6@mail.gmail.com>

Grant Likely wrote:
> On Thu, Mar 18, 2010 at 2:24 PM, Bill Gatliff <bgat@billgatliff.com> wrote:
>   
>> 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.
>>     
>
> Hi Bill.  I've just pushed out my tree with a bit of the device tree
> probing working on the versatile platform.  It works with the QEMU
> branch that Jeremy Kerr is maintaining.  Here are the git trees, and
> the web page that describes how to build it:
>
> git://git.secretlab.ca/git/linux-2.6 test-devicetree
> git://git://kernel.ubuntu.com/jk/dt/qemu.git
> https://wiki.ubuntu.com/KernelTeam/ARMDeviceTrees
>
> I've got stuff working on real hardware too, but it's not fully baked
> yet.  Right now qemu is the least trouble.
>
> g.
>
>   

Grant and Jeremy,

I'm very happy to try that on my real Freescale i.MX51 board. Any hints 
about that?

Cheers,
-Bryan

  reply	other threads:[~2010-04-08  6:41 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
2010-04-08  6:31       ` Grant Likely
2010-04-08  6:41         ` Bryan Wu [this message]
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=4BBD7A9A.9090501@canonical.com \
    --to=bryan.wu@canonical.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 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.