From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [dtc] Add support for flat device tree format version 17
Date: Wed, 14 Mar 2007 17:11:04 -0400 [thread overview]
Message-ID: <45F864E8.40501@smiths-aerospace.com> (raw)
In-Reply-To: <45F863DF.5050709@freescale.com>
Timur Tabi wrote:
> David Gibson wrote:
>> libfdt defined a new version of the flattened device tree format,
>> version 17. It is backwards compatible with version 16, just adding
>> an extra header field giving the size of the blob's structure blob.
>
> Question:
>
> Since the DTB is compatible with V16, then technically U-Boot can work with it. What
> would happen if U-Boot added some nodes to the DTB, but it didn't update size_dt_struct?
> Would the value of size_dt_struct still be correct? If not, then does that mean that
> U-Boot should reject V17 DTBs?
Ahh, now I see your concern and don't know the answer at this point.
The best solution, which I'm making progress on but slowly, is to pull
David Gibson's libfdt utilities into u-boot and use them to manipulate
the tree. I very much want v17 blobs because that removes my
"write-in-place" restrictions on changing the properties.
gvb
next prev parent reply other threads:[~2007-03-14 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 6:22 [dtc] Add support for flat device tree format version 17 David Gibson
2007-03-13 21:10 ` Mark A. Greer
2007-03-14 0:02 ` David Gibson
2007-03-14 21:06 ` Timur Tabi
2007-03-14 21:11 ` Jerry Van Baren [this message]
2007-03-14 21:20 ` Timur Tabi
2007-03-14 23:07 ` David Gibson
2007-03-14 21:41 ` Timur Tabi
2007-03-15 1:32 ` Jerry Van Baren
2007-03-15 1:37 ` Timur Tabi
2007-03-15 2:49 ` Jerry Van Baren
2007-03-15 1:38 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 0:02 David Gibson
2007-03-14 15:32 ` Timur Tabi
2007-03-14 20:41 ` Jon Loeliger
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=45F864E8.40501@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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.