Devicetree
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	David Miller <davem@davemloft.net>,
	miltonm@bga.com
Subject: Re: [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function
Date: Thu, 7 Aug 2008 10:40:22 +1000	[thread overview]
Message-ID: <20080807004022.GA24443@yookeroo.seuss> (raw)
In-Reply-To: <C5C0AA60-C45F-4467-AC76-AA24A00CA4AC@kernel.crashing.org>

On Wed, Aug 06, 2008 at 06:25:48PM +0200, Segher Boessenkool wrote:
>> It's not what we do with flattened device trees blobs though.  In the
>> flattened tree we're not using a /chosen/stdout property, just the
>> linux,stdout-path one.
>>
>> The question that remains is; should there be?  Should the dt blobs
>> use /chosen/stdout also?  (I'm not familiar enough with real OF to
>> know the answer.  I'm assuming that an instance value is not the same
>> as a phandle).
>
> ihandles and phandles are not the same thing in OF.  Since in the
> "flat world" we cannot have instances, we should use phandles instead
> of ihandles for the things in /chosen.  I thought we agreed on that
> already, perhaps I am wrong?

Not that I recall.  In general we've been avoiding using anything that
traditionally contains an ihandle; hence the direct use of
linux,stdout-path when using a flat tree.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  parent reply	other threads:[~2008-08-07  0:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080806055214.30717.86092.stgit@trillian.secretlab.ca>
     [not found] ` <20080806060239.30717.79273.stgit@trillian.secretlab.ca>
     [not found]   ` <20080805.233205.201125898.davem@davemloft.net>
     [not found]     ` <18585.31504.836857.829592@cargo.ozlabs.ibm.com>
2008-08-06 13:31       ` [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function Grant Likely
2008-08-06 16:25         ` Segher Boessenkool
2008-08-06 17:09           ` Mitch Bradley
2008-08-07  0:40           ` David Gibson [this message]
2008-08-07 22:35         ` Benjamin Herrenschmidt
     [not found]   ` <ed82fe3e0808060946v39992095pfb6b85726b7d307d@mail.gmail.com>
     [not found]     ` <20080807061254.GB12571@yookeroo.seuss>
2008-08-07 17:28       ` Yoder Stuart
2008-08-07 18:11         ` Timur Tabi
2008-08-07 19:20 Milton Miller
2008-08-07 19:22 ` Timur Tabi
     [not found]   ` <489B4B89.1010507-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-08-07 19:38     ` Scott Wood

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=20080807004022.GA24443@yookeroo.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=segher@kernel.crashing.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