From: Timur Tabi <timur@freescale.com>
To: Timur Tabi <timur@freescale.com>,
Grant Likely <grant.likely@secretlab.ca>,
linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Could the DTS experts look at this?
Date: Tue, 12 Feb 2008 17:47:23 -0600 [thread overview]
Message-ID: <47B2300B.4060101@freescale.com> (raw)
In-Reply-To: <20080212232639.GD21230@localhost.localdomain>
David Gibson wrote:
> I can pretty much guarantee you that someone will find that
> insufficient and want to expand the conditional representation. This
> way madness lies.
Then let them. We can have version numbers associated with the conditional
expressions. If they want to make more complex condition expressions, they can
bump the version number and define a spec and write code to parse it.
> No. As Grant says, that's not what the version number is for. It
> represents the version of the encoding, not the content. If you must
> version the content (which you should try really hard to avoid) the
> correct way is to add versioning properties to the root node.
And that's why I prefer updating the DTB format to allow attaching conditional
expressions to nodes. This would then necessitate bumping the version number.
Older U-Boots will reject this new DTB. We can also modify DTC to support
conditional nodes, so that if a customer has an older U-Boot he can't update, he
can use DTC to generate a V17 DTB that has the conditionals already processed.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-02-12 23:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 23:30 Could the DTS experts look at this? Sean MacLennan
2008-02-10 5:47 ` Arnd Bergmann
2008-02-10 6:05 ` Sean MacLennan
2008-02-11 17:57 ` Timur Tabi
2008-02-11 23:54 ` David Gibson
2008-02-11 23:56 ` David Gibson
2008-02-12 0:21 ` Arnd Bergmann
2008-02-12 0:36 ` David Gibson
2008-02-12 18:51 ` Scott Wood
2008-02-12 23:17 ` David Gibson
2008-02-12 23:41 ` Timur Tabi
2008-02-12 23:50 ` David Gibson
2008-02-12 15:44 ` Timur Tabi
2008-02-12 18:58 ` Grant Likely
2008-02-12 19:08 ` Timur Tabi
2008-02-12 19:34 ` Grant Likely
2008-02-12 19:45 ` Timur Tabi
2008-02-12 20:43 ` Grant Likely
2008-02-12 23:35 ` David Gibson
2008-02-12 23:50 ` Timur Tabi
2008-02-13 0:10 ` Grant Likely
2008-02-12 23:26 ` David Gibson
2008-02-12 23:47 ` Timur Tabi [this message]
2008-02-13 0:08 ` David Gibson
2008-02-13 0:15 ` Grant Likely
2008-02-12 23:21 ` David Gibson
2008-02-11 0:14 ` David Gibson
2008-02-11 2:40 ` Sean MacLennan
2008-02-11 3:11 ` David Gibson
2008-02-11 3:49 ` Sean MacLennan
2008-02-11 23:59 ` David Gibson
2008-02-12 1:07 ` Sean MacLennan
2008-02-12 0:20 ` David Gibson
2008-02-12 0:41 ` Sean MacLennan
2008-02-12 0:48 ` David Gibson
2008-02-12 18:52 ` Scott Wood
2008-02-12 19:03 ` Grant Likely
2008-02-12 19:10 ` Scott Wood
2008-02-17 10:22 ` David Woodhouse
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=47B2300B.4060101@freescale.com \
--to=timur@freescale.com \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--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).