devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Jon Masters <jonathan-Zp4isUonpHBD60Wz+7aTrA@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Testing on ARM (omap)
Date: Tue, 18 Jan 2011 23:05:21 -0700	[thread overview]
Message-ID: <20110119060521.GA2545@angua.secretlab.ca> (raw)
In-Reply-To: <E6BA3EFB-21A0-4F75-872C-1CBB23DD5A5A-Zp4isUonpHBD60Wz+7aTrA@public.gmane.org>

On Tue, Jan 04, 2011 at 04:16:46AM -0500, Jon Masters wrote:
> Folks,
> 
> Anyone point me to the latest status for testing fdt on ARM? (e.g. OMAP3)
> 
> Jon.

Hi Jon

Sorry for the delay in answering.

I published a new branch today that makes it a lot easier to start
playing around with fdt on ARM.

  git://git.secretlab.ca/git/linux-2.6 devicetree/arm

Look at the changes to versatile and tegra board support in that
branch to see how to add very basic device tree support to any
machine_desc.

U-boot already has device tree support enabled for beagleboard in the
latest release.

I've not yet published a set of instructions on how to set everything
up; I'll try to get something out there this week.

Cheers,
g.

> 
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss

      parent reply	other threads:[~2011-01-19  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04  9:16 Testing on ARM (omap) Jon Masters
     [not found] ` <E6BA3EFB-21A0-4F75-872C-1CBB23DD5A5A-Zp4isUonpHBD60Wz+7aTrA@public.gmane.org>
2011-01-19  6:05   ` Grant Likely [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=20110119060521.GA2545@angua.secretlab.ca \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jonathan-Zp4isUonpHBD60Wz+7aTrA@public.gmane.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).