linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Jim Thompson <jim@musenki.com>, Sergiy Kovtun <skovtun@yahoo.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: 64Mbytes on Sandpoint-X3B
Date: Fri, 31 May 2002 14:23:01 -0400	[thread overview]
Message-ID: <3CF7BF85.9AF1FB19@mvista.com> (raw)
In-Reply-To: 20020531151130.GN32412@opus.bloom.county


Tom Rini wrote:

> On Fri, May 31, 2002 at 10:01:39AM -0500, Jim Thompson wrote:
> >
> > Tom Rini writes:
> > >
> > > On Thu, May 30, 2002 at 11:02:44PM -0700, Sergiy Kovtun wrote:
> > >
> > > > Hello All,
> > > > I try to connect all my 64 Meg memoty on
> > > > Sandpoint-X3B,
> > > > but received a crash( with 32M all OK).
> > > > Source:
> > > > SP-X3B + Altimus MPC7410
> > > > HHL 2.0
> > > > Any ideas??
> > >
> > > DINK32 12.2 does not correctly initalize the memory controller on-board.
> > > DINK32 12.3 claims to do this correctly, but in some testing locally it
> > > still did not get everything correct.
> >
> > Could you be more specific as to what is missing?
>
> On the DINK32 12.2 side it blindly sets some parts up for 64mb total
> regardless of the ammount of memory.  I think there's other things as
> well, but Mark Greer would know better..

I only have 12.2 here and it initializes the wrong amount which will cause a
panic if you rely on the getting the amount of memory from how the memory ctlr
regs are set up.

The last time I really looked at what DINK was doing to the mem ctlr was back on
12.0 so my info is stale now.  Sounds like Tom has the most current, detailed
info on what DINK does.  Chances are, Sergiy, is that you'll  have to roll up
your sleeves and dig into it.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-05-31 18:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  6:02 64Mbytes on Sandpoint-X3B Sergiy Kovtun
2002-05-31 14:51 ` Tom Rini
2002-05-31 15:01   ` Jim Thompson
2002-05-31 15:11     ` Tom Rini
2002-05-31 15:20       ` Jim Thompson
2002-05-31 15:26         ` Tom Rini
2002-05-31 15:43           ` Jim Thompson
2002-05-31 17:48           ` Mark A. Greer
2002-05-31 18:13             ` Tom Rini
2002-05-31 18:18               ` Mark A. Greer
2002-05-31 18:25                 ` Tom Rini
2002-06-24  1:52                   ` PPCboot+MPC7410+Sandpoint Sergiy Kovtun
2002-06-25  0:15                     ` PPCboot+MPC7410+Sandpoint Boo Geum Jung
2002-06-25  0:19                       ` PPCboot+MPC7410+Sandpoint Wolfgang Denk
2002-06-25  0:44                         ` PPCboot+MPC7410+Sandpoint Boo Geum Jung
2002-05-31 18:23       ` Mark A. Greer [this message]
2002-05-31 20:35         ` 64Mbytes on Sandpoint-X3B Gary Milliorn
2002-05-31 17:55 ` Mark A. Greer

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=3CF7BF85.9AF1FB19@mvista.com \
    --to=mgreer@mvista.com \
    --cc=jim@musenki.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=skovtun@yahoo.com \
    --cc=trini@kernel.crashing.org \
    /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).