linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PPC & 2.6.0-test3: wrong mem size & hang on ifconfig
Date: Wed, 1 Sep 2004 11:44:20 -0700	[thread overview]
Message-ID: <20040901184420.GE19730@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.GSO.4.44.0408191346130.15736-100000@math.ut.ee>

On Thu, Aug 19, 2004 at 01:48:45PM +0300, Meelis Roos wrote:
> > On Tue, Jan 06, 2004 at 02:00:20PM +0200, Meelis Roos wrote:
> >
> > > > > >  			if (getprop(dev_handle, "reg", mem_info,
> > > > > > -						sizeof(mem_info) != 8))
> > > > > > +						sizeof(mem_info) != 8)) {
> > >
> > > > 	if ((n = getprop(dev_handle, "reg", mem_info, sizeof(mem_info))
> > > > 	!= 8) {
> > >
> > > I tried it (applied it by hand and fixed parens) and it did not print n
> > > and found the right RAM size with todays BK (2.4.24-pre3 by Makefile). I
> > > was confused but did read the patch 3 times. Now I see it - one closing
> > > parenthesis was in the wrong place. Seems you have fixed it in 2.4 tree
> > > already since it's ok in BK.
> > >
> > > So 2.4 is OK again on my Motorola Powerstack II Pro4000 (prep, no
> > > residual, OF present). Thanks! dmesg now tells
> > > Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
> > > Total memory = 64MB; using 128kB for hash table (at c0240000)
> > >
> > > 2.6 probably needs the same fix (current 2.6 is not OK).
> >
> > I hope to get this fixed in 2.6.2 (2.6 lacks the add OF back to PReP
> > bits, and the patch is kinda big).
> 
> Well, now that my Powerstack II boots 2.6 again, I'm missing the
> additional memory - I now have 192M and it only detects 32M :)

Hmm.  Can you change arch/ppc/boot/simple/misc-prep.c so that it will
only try to look in residual data or OF ?  I'm guessing that
mpc10x_get_mem_size() is returning 32MB.

Or does this board not have an MPC105||MPC106 ?

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-09-01 18:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 19:12 PPC & 2.6.0-test3: wrong mem size & hang on ifconfig Meelis Roos
2003-08-29 18:49 ` Tom Rini
2003-10-10  9:20   ` Meelis Roos
2003-10-13 16:02     ` Tom Rini
2003-10-14 18:25       ` Meelis Roos
2003-10-14 18:42         ` Tom Rini
2003-10-14 18:44           ` Meelis Roos
2003-10-14 18:53             ` Tom Rini
2003-10-14 19:58               ` Meelis Roos
2003-10-14 23:25                 ` Tom Rini
2003-10-20 13:55                   ` Meelis Roos
2003-10-20 15:30                     ` Tom Rini
2003-10-20 15:41                       ` Meelis Roos
2003-10-20 20:33                     ` Tom Rini
2003-10-22 15:31                       ` Meelis Roos
2003-10-22 15:47                         ` Tom Rini
2003-12-10 13:21                       ` Meelis Roos
2003-12-10 16:11                         ` Tom Rini
2003-12-11 13:51                           ` Meelis Roos
2003-12-24 21:20                             ` Tom Rini
2004-01-06 12:00                               ` Meelis Roos
2004-01-06 15:37                                 ` Tom Rini
2004-08-19 10:48                                   ` Meelis Roos
2004-09-01 18:44                                     ` Tom Rini [this message]
2003-10-13 22:46     ` Tom Rini

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=20040901184420.GE19730@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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).