Re: DTS Bytestrings Representation in /dts-v1/ files
On Thu, 08 Nov 2007 13:18:50 -0600 Jon Loeliger [EMAIL PROTECTED] 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 ]; 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? My off-the-cuff opinion is to leave them as they are today. They seem to mostly be used for MAC addresses, and you don't really see a whole lot of those with the 0x prefix before every number. At the same time, inconsistency sucks. josh ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
DTS Bytestrings Representation in /dts-v1/ files
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 ]; 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 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: DTS Bytestrings Representation in /dts-v1/ files
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 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
