RE: [PATCH 15/16] Add device tree for Ebony

=20

-----Original Message-----
From: linuxppc-dev-bounces+b08248=3Dfreescale.com@ozlabs.org=20
[mailto:linuxppc-dev-bounces+b08248=3Dfreescale.com@ozlabs.org]=20
On Behalf Of Segher Boessenkool
Sent: Thursday, February 15, 2007 8:57 AM
To: Jon Loeliger
Cc: linuxppc-dev@ozlabs.org; David Gibson
Subject: Re: [PATCH 15/16] Add device tree for Ebony=20
=20

quoted

quoted

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?

=20
In OF, there has to be whitespace inbetween.
=20

quoted

And are there other bases to
this model?  Like, maybe, "b#", "o#" and "h#" as well?

=20
o# d# h# are standard defined; b# exists on many implementations.

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

I would prefer in the DTS files to have no whitespace in=20
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