From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [dtc] Allow multipart property values
Date: Thu, 08 Feb 2007 17:29:03 -0600 [thread overview]
Message-ID: <E1HFIhL-0003bU-UX@jdl.com> (raw)
In-Reply-To: Your message of "Wed, 07 Feb 2007 16:37:50 +1100." <20070207053750.GG23870@localhost.localdomain>
So, like, the other day David Gibson mumbled:
>
> There's nothing in tests/ though - I always meant to make a testsuite,
> but I never got around to it. Current plan is to implement a
> testsuite by merging libfdt into the dtc tree.
>
> Here's a revised patch which adds an example usage to test.dts
>
> [dtc] Allow multipart property values
>
> At present each property definition in a dts file must give as the
> value either a string ("abc..."), a bytestring ([12abcd...]) or a cell
> list (<1 2 3 ...>). This patch allows a property value to be given as
> several of these, comma-separated. The final property value is just
> the components appended together. So a property could have a list of
> cells followed by a string, or a bytestring followed by some cells.
> Cells are always aligned, so if cells are given following a string or
> bytestring which is not a multiple of 4 bytes long, zero bytes are
> inserted to align the following cells.
>
> The primary motivation for this feature, however, is to allow defining
> a property as a list of several strings. This is what's needed for
> defining OF 'compatible' properties, and is less ugly and fiddly than
> using embedded \0s in the strings.
>
> Signed-off-by: David Gibson <dwg@au1•ibm.com>
Applied.
Thanks,
jdl
next prev parent reply other threads:[~2007-02-08 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 3:23 [dtc] Allow multipart property values David Gibson
2007-02-07 4:37 ` Kumar Gala
2007-02-07 4:46 ` David Gibson
2007-02-07 4:50 ` Kumar Gala
2007-02-07 5:37 ` David Gibson
2007-02-08 23:29 ` Jon Loeliger [this message]
2007-02-07 14:35 ` Jon Loeliger
2007-02-07 16:40 ` 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=E1HFIhL-0003bU-UX@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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