From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Segher Boessenkool <segher@kernel•crashing.org>
Cc: Matt Porter <mporter@embeddedalley•com>,
Paul Mackerras <paulus@samba•org>,
linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Start arch/powerpc/boot code reorganization
Date: Fri, 29 Sep 2006 00:53:21 +0400 [thread overview]
Message-ID: <451C3641.60107@ru.mvista.com> (raw)
In-Reply-To: <D47FC822-2AB1-459A-B2EC-50A99552DC9A@kernel.crashing.org>
Hello.
Segher Boessenkool wrote:
>>>Yes. Except a "cell" is not what you think it is. A "cell" is the
>>>size of numbers OF deals with internally; just deal with it. Of
>>>course, there's things like "#address-cells", which really mean
>>>"#-32bit-things-per-address".
>>Okay, well, when I talked about cells I meant "#-32bit-things-per-
>>address".
>>Obviously it was silly of me to think that "#address-cells" meant
>>the # of
>>address cells...
> Some background might clear things up (or not)... A "cell" is the
> unit of data in a Forth system. When OF was young (and not yet
> called OF), all systems were 32-bit, and the 32-bit-thingies in
> the properties (which weren't yet called properties) in the device
> tree were called cells as well. When 64-bit came into the picture,
> everything fell apart. The "correct" name for the property thingies
> now is "integers as encoded with encode-int".
I looked into the OF 64-bit extensions spec, and "cell" is 64-bit there.
So, "address" should look valid. I don't know whether PPC64 boxes support
64-bit OF, or only 32-bit, however, the kernel doesn't seem to deal with
64-bit ones correctly, so I'm assuming that 32-bit OF is at least available...
Anyway, I'm still missing the point of not using "address" which is
clearly intended for such case.
WBR, Sergei
next prev parent reply other threads:[~2006-09-28 20:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 23:00 [PATCH] Start arch/powerpc/boot code reorganization Paul Mackerras
2006-09-20 1:20 ` Mark A. Greer
2006-09-20 1:28 ` Mark A. Greer
2006-09-20 20:58 ` Mark A. Greer
2006-09-20 3:10 ` Josh Boyer
2006-09-20 20:23 ` Segher Boessenkool
2006-09-20 21:04 ` Josh Boyer
2006-09-20 21:32 ` Benjamin Herrenschmidt
2006-09-20 21:57 ` Mark A. Greer
2006-09-21 0:07 ` Segher Boessenkool
2006-09-21 13:37 ` Matt Porter
2006-09-21 14:15 ` Jon Loeliger
2006-09-21 14:26 ` Matt Porter
2006-09-21 15:31 ` Segher Boessenkool
2006-09-22 1:24 ` Mark A. Greer
2006-09-22 8:43 ` Segher Boessenkool
2006-09-22 18:59 ` Mark A. Greer
2006-09-22 19:36 ` Sergei Shtylyov
2006-09-22 20:40 ` Mark A. Greer
2006-09-22 20:43 ` Sergei Shtylyov
2006-09-22 20:52 ` Mark A. Greer
2006-09-22 20:56 ` Sergei Shtylyov
2006-09-23 0:57 ` Segher Boessenkool
2006-09-23 15:48 ` Sergei Shtylyov
2006-09-23 0:54 ` Segher Boessenkool
2006-09-23 8:18 ` Mark A. Greer
2006-09-23 10:15 ` Segher Boessenkool
2006-09-25 17:53 ` Mark A. Greer
2006-09-25 23:40 ` Segher Boessenkool
2006-09-25 23:44 ` Segher Boessenkool
2006-09-25 23:46 ` Mark A. Greer
2006-09-28 20:53 ` Sergei Shtylyov [this message]
2006-09-30 8:36 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 3:21 Paul Mackerras
2006-09-19 4:22 ` Michael Ellerman
2006-09-19 4:29 ` Paul Mackerras
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=451C3641.60107@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mporter@embeddedalley$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=segher@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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