[PATCH 15/16] Add device tree for Ebony

[Yoder Stuart-B08248]

> -----Original Message-----
> From: linuxppc-dev-bounces+b08248=freescale.com at ozlabs.org 
> [mailto:linuxppc-dev-bounces+b08248=freescale.com at ozlabs.org] 
> On Behalf Of Segher Boessenkool
> Sent: Thursday, February 15, 2007 8:57 AM
> To: Jon Loeliger
> Cc: linuxppc-dev at ozlabs.org; David Gibson
> Subject: Re: [PATCH 15/16] Add device tree for Ebony 
> 
> >> The first option.  Anywhere a number can be used, "d# xxx"
> >> would mean decimal.
> >>
> >> When you would say <d# 1234  5678>, 1234 is decimal and
> >> 5678 is hexadecimal.
> >
> > Where do the tokens end?  Is "d#1234" valid and equal to "d# 1234"?
> > Or is "d#" an independent token?
> 
> In OF, there has to be whitespace inbetween.
> 
> > And are there other bases to
> > this model?  Like, maybe, "b#", "o#" and "h#" as well?
> 
> o# d# h# are standard defined; b# exists on many implementations.

1275 specifies whitespace inbetween, but isn't this due to 
the way they are describing things for the forth / stack-based
operations?

I would prefer in the DTS files to have no whitespace in 
between--  <d#1234 #h5678> seems much more readable
than <d# 1234 #h 5678>.

Or even better-- just use standard C notation
    <1234 0x5678>

That is very readable.  Why bring unnecessary complexity into
this?

Stuart