Devicetree
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: Paul Mackerras <paulus@samba.org>
Cc: devicetree-discuss@ozlabs.org, miltonm@bga.com,
	linuxppc-dev@ozlabs.org, David Miller <davem@davemloft.net>
Subject: Re: [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function
Date: Wed, 6 Aug 2008 07:31:55 -0600	[thread overview]
Message-ID: <fa686aa40808060631k278e187ej965f0ac08c837937@mail.gmail.com> (raw)
In-Reply-To: <18585.31504.836857.829592@cargo.ozlabs.ibm.com>

On Wed, Aug 6, 2008 at 4:21 AM, Paul Mackerras <paulus@samba.org> wrote:
> David Miller writes:
>
>> On sparc platforms this is obtained differently.  We obtain the 32-bit
>> instance value of "/chosen/stdout" and convert that into a prom device
>> node path using "instance-to-path".
>
> That's actually exactly what we do too, the linux,stdout-path property
> is just a cache of the result of that process.  The difference is that
> we have to do it early on while we still have OF around, while you can
> do it later.

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).

g.

>
> Paul.
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

       reply	other threads:[~2008-08-06 13:31 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       ` Grant Likely [this message]
2008-08-06 16:25         ` [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function Segher Boessenkool
2008-08-06 17:09           ` Mitch Bradley
2008-08-07  0:40           ` David Gibson
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=fa686aa40808060631k278e187ej965f0ac08c837937@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=paulus@samba.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