From: Scott Wood <scottwood@freescale.com>
To: Tudor Laurentiu <Laurentiu.Tudor@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc/85xx: Move ePAPR paravirt initialization earlier
Date: Wed, 26 Jun 2013 13:56:45 -0500 [thread overview]
Message-ID: <1372273005.8183.32@snotra> (raw)
In-Reply-To: <51CAE047.8030605@freescale.com> (from Laurentiu.Tudor@freescale.com on Wed Jun 26 07:36:23 2013)
On 06/26/2013 07:36:23 AM, Tudor Laurentiu wrote:
> On 06/26/2013 02:14 AM, Scott Wood wrote:
>> This would require converting
>> the code to use the early device tree functions.
>>=20
>=20
> I see. Had a look at that api and it seems pretty limited.
> I couldn't find a simple way of reading a property other than =20
> scanning the entire tree with of_scan_flat_dt().
What's wrong with scanning the entire tree? The data format doesn't =20
allow any more efficient type of lookup (it was designed to be simple =20
and small, not fast).
-Scott=
prev parent reply other threads:[~2013-06-26 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 15:52 [PATCH] powerpc/85xx: Move ePAPR paravirt initialization earlier Laurentiu Tudor
2013-06-25 23:14 ` Scott Wood
2013-06-26 12:36 ` Tudor Laurentiu
2013-06-26 18:56 ` Scott Wood [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=1372273005.8183.32@snotra \
--to=scottwood@freescale.com \
--cc=Laurentiu.Tudor@freescale.com \
--cc=linuxppc-dev@lists.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).