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, 18 Mar 2010 07:14:05 -0600	[thread overview]
Message-ID: <fa686aa41003180614g574b9d91o5926f94a59ad5ec9@mail.gmail.com> (raw)
In-Reply-To: <dac45061003180504k49a9f303y4329530a5b475108@mail.gmail.com>

On Thu, Mar 18, 2010 at 6:04 AM, Mark Ryden <markryde@gmail.com> wrote:
> Hello,
> According to :
> http://lwn.net/Articles/375296/
> Some patches that add basic ARM device tree support
> were sent,
>
> In the link above, there is a link to a git tree here:
> git://git.secretlab.ca/git/linux-2.6 test-devicetree
>
> I git-cloned this tree, and I don't have arch/arm/kernel/devtree.c
>
> Am I missing something ?

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.

g.

  reply	other threads:[~2010-03-18 13:14 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 [this message]
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
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=fa686aa41003180614g574b9d91o5926f94a59ad5ec9@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).