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: Mon, 20 Oct 2003 08:30:20 -0700 [thread overview]
Message-ID: <20031020153020.GA6062@ip68-0-152-218.tc.ph.cox.net> (raw)
In-Reply-To: <Pine.GSO.4.44.0310201655210.18000-100000@math.ut.ee>
On Mon, Oct 20, 2003 at 04:55:39PM +0300, Meelis Roos wrote:
> > Can you apply the following patch (2.6)? I'm expecting it to print out that
> > it hard-codes to 32mb.
>
> > + puts("Hard-coded\n");
>
> Yes, hard-coded.
Okay, thanks. I now know what the problem is. We no longer probe OF to
get the memory size. What I'm going to do is to take one of the patches
that has existed for a while now to put back the code needed so that we
can still talk with OF, and we'll add in a test for that as well. I
hope to have time this week to do it.
Just curious, what bridge is in this machine (an output of lspci would
do fine, too). Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2003-10-20 15:30 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 [this message]
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
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=20031020153020.GA6062@ip68-0-152-218.tc.ph.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.