From: "John Rigby" <jrigby@freescale.com>
To: "Kim Phillips" <kim.phillips@freescale.com>
Cc: jrigby@gmail.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Draft mpc52xx device tree specification
Date: Mon, 13 Nov 2006 18:41:04 -0700 [thread overview]
Message-ID: <4b73d43f0611131741v59f1f780i827f4e95000decdf@mail.gmail.com> (raw)
In-Reply-To: <20061113135609.601647b0.kim.phillips@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
I agree with Kim. I would like to see some kind of merge of this an
booting-without-of.
On 11/13/06, Kim Phillips <kim.phillips@freescale.com> wrote:
>
> On Mon, 13 Nov 2006 01:47:29 -0700
> "Grant Likely" <grant.likely@secretlab.ca> wrote:
>
> >
> > This document specifies the requirements on the device-tree for mpc52xx
> > based boards. These requirements are above and beyond the details
> > specified in the booting-without-of.txt document.
>
> well, the definition of the compatible property has a different bias. I'm
> not saying the definition in booting-without-of is necessarily better (I
> know the document is too linux- and freescale-specific in places), I'm just
> saying that this document has good ideas, but is creating an unnecessary
> diversion, and amending booting-without-of would help maintain consistency
> with other platforms' efforts.
>
> Kim
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 1531 bytes --]
next prev parent reply other threads:[~2006-11-14 1:41 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 [this message]
2006-11-27 17:53 ` Grant Likely
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=4b73d43f0611131741v59f1f780i827f4e95000decdf@mail.gmail.com \
--to=jrigby@freescale.com \
--cc=jcrigby@gmail.com \
--cc=jrigby@gmail.com \
--cc=kim.phillips@freescale.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).