From: Meelis Roos <mroos@linux.ee>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PPC & 2.6.0-test3: wrong mem size & hang on ifconfig
Date: Thu, 19 Aug 2004 13:48:45 +0300 (EEST) [thread overview]
Message-ID: <Pine.GSO.4.44.0408191346130.15736-100000@math.ut.ee> (raw)
In-Reply-To: <20040106153737.GJ2415@stop.crashing.org>
> 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 :)
Tis is not very urgent though, there are other problems with this
machine before it's production quality with 2.6 - like tulip (and now
maybe also a usb uhci hcd) hanging. I'll try to narrow these down too.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2004-08-19 10:56 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 [this message]
2004-09-01 18:44 ` Tom Rini
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=Pine.GSO.4.44.0408191346130.15736-100000@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--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).