From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 9 Nov 2007 11:21:38 +1100 From: David Gibson To: Jon Loeliger Subject: Re: DTS Bytestrings Representation in /dts-v1/ files Message-ID: <20071109002138.GE18592@localhost.localdomain> References: <20071106231120.GG31367@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Nov 08, 2007 at 01:18:50PM -0600, Jon Loeliger wrote: > > Folks, > > When the new DTS /dts-v1/ support is released Real Soon Now, > it will support C-like literal constants. Hex values will be > prefixed with 0x, binary with 0b, and bare numbers will be > decimal unless they start with a leading 0. > > One outstanding question on which I'd like some feedback > is the issue of bytestring value representation. > > Currently they look like this: > > stuff = [ 0b 31 22 de ea ad be ef ]; Or, equivalently, like this: stuff = [0b3122deeaadbeef]; I think it's important to be aware of the more compact form when considering whether to change the representation. > One opinion is to have them continue to look like that > and be in hex only. > > Another opinion is to allow the new, consistent C-style > literals and expressions so that one could have: > > new_stuff = [ 0x31 49 '1' 23 17 ]; > > Opinions? > > Thanks, > jdl -- 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