From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: "Mark A. Greer" <mgreer@mvista•com>
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, 22 Sep 2006 23:36:11 +0400 [thread overview]
Message-ID: <45143B2B.7060501@ru.mvista.com> (raw)
In-Reply-To: <20060922185923.GB25738@mag.az.mvista.com>
Hello.
Mark A. Greer wrote:
> Here is where I think we are for getting the effective base addr
> of the regs for the console uart in the bootwrapper:
> 1) We add the "fw,address" property to the uart's dt node. That
> property provides the effective base address of the uart's registers
> left over by the firmware. The format is similar to that of the
> "reg" property in that it contains an "address size" tuple.
> 2) The effective address width (32 or 64 bits) (i.e., the # cells in
> the "address" portion of the tuple) is indicated by the presence of the
> "/cpus/64-bit" property. If it exists, the effective addr space is
> 64-bits wide (2 cells); if not, its 32-bits wide (1 cell).
>
> 3) The number of cells in the "size" portion of the tuple is indicated
> by the nearest #size-cells as you go up the tree. Just like the "reg"
> property.
Well, is there need for duplication of size if "reg" prop must be present
anyway?
WBR, Sergei
next prev parent reply other threads:[~2006-09-22 19:36 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 [this message]
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
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=45143B2B.7060501@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mgreer@mvista$(echo .)com \
--cc=mporter@embeddedalley$(echo .)com \
--cc=paulus@samba$(echo .)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