From: "Grant Likely" <grant.likely@secretlab.ca>
To: jcrigby@gmail.com
Cc: jrigby@gmail.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Draft mpc52xx device tree specification
Date: Mon, 27 Nov 2006 10:53:31 -0700 [thread overview]
Message-ID: <528646bc0611270953p3f1aa3adx3dd2261b5f0b307b@mail.gmail.com> (raw)
In-Reply-To: <4b73d43f0611131741v59f1f780i827f4e95000decdf@mail.gmail.com>
On 11/13/06, John Rigby <jrigby@freescale.com> wrote:
> I agree with Kim. I would like to see some kind of merge of this an
> booting-without-of.
okay, I understand the point, and I agree. However I've also received
the comment that this document also needs to address boards with real
OFW, and that booting_without_of.txt is kind of limited in that regard
Perhaps it would be better to split off a 'device tree binding
conventions' document; use booting_without_of.txt to describe the
mechanism for non-OFW ports, and use another doc to describe layout
expectation/conventions for common SoC's and devices.
I'm about to post a patch set for the 52xx boards which includes this
document. For the time being, I'm going to leave the document as is
because I haven't had a chance to do any revision, but I'll take a
look at shuffling stuff around once the 52xx patches are suitable for
inclusion in .20
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2006-11-27 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 8:47 [RFC] Draft mpc52xx device tree specification Grant Likely
2006-11-13 19:56 ` Kim Phillips
2006-11-14 1:41 ` John Rigby
2006-11-27 17:53 ` 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=528646bc0611270953p3f1aa3adx3dd2261b5f0b307b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jcrigby@gmail.com \
--cc=jrigby@gmail.com \
--cc=linuxppc-dev@ozlabs.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).