From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jcrigby@gmail.com>
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186])
	by ozlabs.org (Postfix) with ESMTP id BC51667EC3
	for <linuxppc-dev@ozlabs.org>; Tue, 14 Nov 2006 12:41:06 +1100 (EST)
Received: by nf-out-0910.google.com with SMTP id n15so76131nfc
	for <linuxppc-dev@ozlabs.org>; Mon, 13 Nov 2006 17:41:04 -0800 (PST)
Message-ID: <4b73d43f0611131741v59f1f780i827f4e95000decdf@mail.gmail.com>
Date: Mon, 13 Nov 2006 18:41:04 -0700
From: "John Rigby" <jrigby@freescale.com>
Sender: jcrigby@gmail.com
To: "Kim Phillips" <kim.phillips@freescale.com>
Subject: Re: [RFC] Draft mpc52xx device tree specification
In-Reply-To: <20061113135609.601647b0.kim.phillips@freescale.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_90167_31961934.1163468464507"
References: <528646bc0611130047v107e7171h804c674534ef8058@mail.gmail.com>
	<20061113135609.601647b0.kim.phillips@freescale.com>
Cc: jrigby@gmail.com, linuxppc-dev@ozlabs.org
Reply-To: jcrigby@gmail.com
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.ozlabs.org>
List-Unsubscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=unsubscribe>
List-Archive: <http://ozlabs.org/pipermail/linuxppc-dev>
List-Post: <mailto:linuxppc-dev@ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@ozlabs.org?subject=help>
List-Subscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=subscribe>

------=_Part_90167_31961934.1163468464507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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
>

------=_Part_90167_31961934.1163468464507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I agree with Kim.&nbsp; I would like to see some kind of merge of this an booting-without-of.<br><br><div><span class="gmail_quote">On 11/13/06, <b class="gmail_sendername">Kim Phillips</b> &lt;<a href="mailto:kim.phillips@freescale.com">
kim.phillips@freescale.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Mon, 13 Nov 2006 01:47:29 -0700<br>&quot;Grant Likely&quot; &lt;
<a href="mailto:grant.likely@secretlab.ca">grant.likely@secretlab.ca</a>&gt; wrote:<br><br>&gt;<br>&gt; This document specifies the requirements on the device-tree for mpc52xx<br>&gt; based boards.&nbsp;&nbsp;These requirements are above and beyond the details
<br>&gt; specified in the booting-without-of.txt document.<br><br>well, the definition of the compatible property has a different bias.&nbsp;&nbsp;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.
<br><br>Kim<br>_______________________________________________<br>Linuxppc-dev mailing list<br><a href="mailto:Linuxppc-dev@ozlabs.org">Linuxppc-dev@ozlabs.org</a><br><a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">
https://ozlabs.org/mailman/listinfo/linuxppc-dev</a><br></blockquote></div><br>

------=_Part_90167_31961934.1163468464507--