linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [dtc] Allow multipart property values
Date: Wed, 7 Feb 2007 15:46:16 +1100	[thread overview]
Message-ID: <20070207044616.GF23870@localhost.localdomain> (raw)
In-Reply-To: <41B393C3-9A8F-46EC-9B47-FCF8E0733994@kernel.crashing.org>

On Tue, Feb 06, 2007 at 10:37:25PM -0600, Kumar Gala wrote:
> 
> On Feb 6, 2007, at 9:23 PM, David Gibson wrote:
> 
> > 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>
> 
> Mind adding examples to the testsuite?

What testsuite...?

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-02-07  4:46 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 [this message]
2007-02-07  4:50     ` Kumar Gala
2007-02-07  5:37       ` David Gibson
2007-02-08 23:29         ` Jon Loeliger
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=20070207044616.GF23870@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --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).