From: Scott Wood <scottwood@freescale.com>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: machine check in kernel for a mpc870 board
Date: Fri, 2 Jul 2010 12:47:13 -0500 [thread overview]
Message-ID: <20100702124713.2e2d300c@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <AANLkTikELusybzh2uTh3KJ6QwelgSHW6HWWPLh-4Zc0b@mail.gmail.com>
On Fri, 2 Jul 2010 10:06:47 -0700
Shawn Jin <shawnxjin@gmail.com> wrote:
> > Or more generally update this section to hold whatever is connected
> > to the localbus on your board. =A0The first cell is the chipselect.
>=20
> The chipselect? Isn't it just the child-bus-addr? BTW, do we have to
> define the #address-cells to 2? 1 is not enough?
The first cell of the child bus address is the chip select, the second
cell is the offset into the chip select.
> SDRAM uses CS0/6, each 64MB. BDI2000 configuration is as follows.
> ; init memory controller
> WM32 0xFA200104 0xfe000ff6 ;;OR0: Flash 32MB
> WM32 0xFA200100 0xfc000001 ;;BR0: Flash at 0xFC000000,
> 32bit, R/W, no parity, use GPCM
> WM32 0xFA20010C 0xfc000e00 ;;OR1: SDRAM 64MB, all
> accesses WM32 0xFA200108 0x00000081 ;;BR1: SDRAM at
> 0x00000000, 32bit, R/W, no parity, use UPMA
> WM32 0xFA200134 0xfc000e00 ;;OR6: SDRAM 64MB, all
> accesses WM32 0xFA200130 0x04000081 ;;BR6: SDRAM at
> 0x04000000, 32bit, R/W, no parity, use UPMA
That looks like SDRAM is on CS1/6, not CS0/6.
We haven't been putting ordinary RAM under the localbus node, even
though it's connected through the localbus on these chips.
> When defining memory's reg property, can a single pair <0 0x08000000>
> be enough? Or must it be <0 0x04000000 0x04000000 0x04000000>?
A single pair is fine.
-Scott
next prev parent reply other threads:[~2010-07-02 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 7:59 machine check in kernel for a mpc870 board Shawn Jin
2010-06-29 8:06 ` Joakim Tjernlund
2010-06-29 8:37 ` Shawn Jin
2010-06-29 18:56 ` Scott Wood
2010-06-30 6:14 ` Shawn Jin
2010-06-30 16:16 ` Scott Wood
2010-06-30 22:25 ` Shawn Jin
2010-07-01 7:50 ` Shawn Jin
2010-07-01 17:42 ` Scott Wood
2010-07-01 20:17 ` Shawn Jin
2010-07-01 20:25 ` Scott Wood
2010-07-02 17:06 ` Shawn Jin
2010-07-02 17:47 ` Scott Wood [this message]
2010-07-02 19:16 ` Shawn Jin
2010-07-02 19:41 ` Scott Wood
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=20100702124713.2e2d300c@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).