From: Timur Tabi <timur@freescale.com>
To: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [dtc] Add support for flat device tree format version 17
Date: Wed, 14 Mar 2007 16:20:29 -0500 [thread overview]
Message-ID: <45F8671D.1010905@freescale.com> (raw)
In-Reply-To: <45F864E8.40501@smiths-aerospace.com>
Jerry Van Baren wrote:
> 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 don't think that will help, because the problem is how do you update a device tree that
you don't know everything about?
> I very much want v17 blobs because that removes my
> "write-in-place" restrictions on changing the properties.
Another idea which just came to light is to have the compatibility field be only useful to
code that just *reads* the DTB. Any code that *writes* the DTB should look it.
Since the kernel only reads the DTB, it can use the compatibility field. Since U-Boot
writes to the DTB, it should currently only accept true V16 DTBs.
If the kernel were to ever write to the DTB, then it would have to be as restrictive.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-03-14 21:20 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
2007-03-14 21:20 ` Timur Tabi [this message]
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=45F8671D.1010905@freescale.com \
--to=timur@freescale.com \
--cc=gerald.vanbaren@smiths-aerospace.com \
--cc=linuxppc-dev@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).