From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: devicetree-discuss@lists.ozlabs.org,
Randy Dunlap <rdunlap@xenotime.net>,
linaro-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [RFC] (early draft) dt: Linux dt usage model documentation
Date: Mon, 13 Jun 2011 17:32:04 -0600 [thread overview]
Message-ID: <BANLkTik-+6RSbE2ycm4zz+Cxm12UEnpC5g@mail.gmail.com> (raw)
In-Reply-To: <d8b25dce-9086-45e3-8dc7-012947e47ed2@VA3EHSMHS018.ehs.local>
On Mon, Jun 13, 2011 at 5:29 PM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
>
>> +Some time later, FDT infrastructure was generalized to be usable by
>> +all architectures. At the time of this writing, 5 mainlined
>> +architectures (arm, mips, powerpc, sparc, and x86) and 1 out of
>
> microblaze too?
Oops, I knew I was missing something. Thanks
g.
>
>> +mainline architecture (nios) have some level of DT support.
>> +
>
> Steve
>
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
>
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2011-06-13 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 13:32 [RFC] (early draft) dt: Linux dt usage model documentation Grant Likely
2011-06-13 16:50 ` Randy Dunlap
2011-06-13 17:12 ` Stephen Warren
2011-06-13 23:29 ` Stephen Neuendorffer
2011-06-13 23:32 ` Grant Likely [this message]
2011-06-14 3:10 ` David Gibson
[not found] ` <BANLkTim_Vzx2ojk33YX+Y6dC-FXsGhm9zw@mail.gmail.com>
2011-06-14 17:47 ` Grant Likely
2011-06-15 7:13 ` Shawn Guo
2011-06-16 16:26 ` Shawn Guo
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=BANLkTik-+6RSbE2ycm4zz+Cxm12UEnpC5g@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stephen.neuendorffer@xilinx.com \
/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).