linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: devicetree in arm
Date: Thu, 8 Apr 2010 00:58:09 -0600	[thread overview]
Message-ID: <n2sfa686aa41004072358g8da88d77jcbee418e5173fae3@mail.gmail.com> (raw)
In-Reply-To: <4BBD7A9A.9090501@canonical.com>

On Thu, Apr 8, 2010 at 12:41 AM, Bryan Wu <bryan.wu@canonical.com> wrote:
> 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.
>
> Grant and Jeremy,
>
> I'm very happy to try that on my real Freescale i.MX51 board. Any hints
> about that?

Look at Jeremy's tree.  He's got a bunch of i.MX51 patches based on
top of my tree.  Here's the git url:

git://kernel.ubuntu.com/jk/dt/linux-2.6.git

g.

  reply	other threads:[~2010-04-08  6:58 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
2010-04-08  6:58           ` Grant Likely [this message]
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=n2sfa686aa41004072358g8da88d77jcbee418e5173fae3@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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).