linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 2/3] Use embedded libfdt in the bootwrapper
Date: Mon, 10 Dec 2007 17:27:01 -0600	[thread overview]
Message-ID: <475DCB45.3090306@freescale.com> (raw)
In-Reply-To: <475DC966.6070301@freescale.com>

Scott Wood wrote:
> David Gibson wrote:
>> On Mon, Dec 10, 2007 at 11:32:17AM -0600, Scott Wood wrote:
>>> How does using offsets as devps work if a devp was previously
>>> acquired to a node that has to be moved due to a change later made
>>> in an earlier part of the tree?
>>
>> It doesn't; don't do that.  I just don't think truly persistent 
>> phandles are worth the code complexity to implement them.
[snip]
> It breaks the extremely common and useful usage of:
> 
> devp = create node;
> setprop(devp, "foo", something);
> setprop(devp, "bar", something);

BTW, there's code in devtree.c with your name on it that does exactly 
this. :-)

-Scott

  reply	other threads:[~2007-12-10 23:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10  3:23 [0/3] Merge libfdt into the bootwrapper David Gibson
2007-12-10  3:28 ` [PATCH 2/3] Use embedded libfdt in " David Gibson
2007-12-10 17:32   ` Scott Wood
2007-12-10 23:10     ` David Gibson
2007-12-10 23:19       ` Scott Wood
2007-12-10 23:27         ` Scott Wood [this message]
2007-12-10 23:32         ` David Gibson
2007-12-10  3:28 ` [PATCH 3/3] Kill flatdevtree.c David Gibson
2007-12-10  3:28 ` [PATCH 1/3] Merge libfdt upstream source David Gibson

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=475DCB45.3090306@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --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;
as well as URLs for NNTP newsgroup(s).