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:19:02 -0600 [thread overview]
Message-ID: <475DC966.6070301@freescale.com> (raw)
In-Reply-To: <20071210231056.GC5495@localhost.localdomain>
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.
We already have working code to implement them. This is a regression
over flatdevicetree.c, and it (or something else in libfdt) seems to be
breaking the ep8248e wrapper (it didn't make it in to the last window
because of dependency on a netdev patch, but I'll probably send it out
tomorrow).
It breaks the extremely common and useful usage of:
devp = create node;
setprop(devp, "foo", something);
setprop(devp, "bar", something);
> Especially since their use more-or-less completely precludes libfdt's
> "stateless" approach, which has significant other advantages.
It doesn't preclude stateless read-only -- what are the benefits to
stateless read-write that are worth invalidating all node references any
time something changes?
-Scott
next prev parent reply other threads:[~2007-12-10 23:18 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 3/3] Kill flatdevtree.c David Gibson
2007-12-10 3:28 ` [PATCH 1/3] Merge libfdt upstream source David Gibson
2007-12-10 3:28 ` [PATCH 2/3] Use embedded libfdt in the bootwrapper David Gibson
2007-12-10 17:32 ` Scott Wood
2007-12-10 23:10 ` David Gibson
2007-12-10 23:19 ` Scott Wood [this message]
2007-12-10 23:27 ` Scott Wood
2007-12-10 23:32 ` 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=475DC966.6070301@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.