All of lore.kernel.org
 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: Tue, 14 Oct 2003 16:25:11 -0700	[thread overview]
Message-ID: <20031014232511.GA17741@ip68-0-152-218.tc.ph.cox.net> (raw)
In-Reply-To: <Pine.GSO.4.44.0310142257010.28944-100000@math.ut.ee>

On Tue, Oct 14, 2003 at 10:58:05PM +0300, Meelis Roos wrote:
> > > This is Motorola Poserstack Pro4000 (UtahII), it has no residual data,
> > > at least the messages say so.
> >
> > Does that machine have openfirmware by chance?
> 
> Yes, OF is present.

Ah-ha!

> I will be away and can access this computer only on next Monday again.

Can you apply the following patch (2.6)?  I'm expecting it to print out that
it hard-codes to 32mb.

===== arch/ppc/boot/prep/misc.c 1.18 vs edited =====
--- 1.18/arch/ppc/boot/prep/misc.c	Tue Jan  7 13:25:58 2003
+++ edited/arch/ppc/boot/prep/misc.c	Tue Oct 14 16:23:55 2003
@@ -224,14 +224,18 @@
 	if (((pci_viddid & 0xffff) == PCI_VENDOR_ID_MOTOROLA)
 			&& ((pci_did == PCI_DEVICE_ID_MOTOROLA_MPC105)
 				|| (pci_did == PCI_DEVICE_ID_MOTOROLA_MPC106)
-				|| (pci_did == PCI_DEVICE_ID_MOTOROLA_MPC107)))
+				|| (pci_did == PCI_DEVICE_ID_MOTOROLA_MPC107))) {
+		puts("Probing for memory\n");	
 		TotalMemory = get_mem_size();
 	/* If it's not, see if we have anything in the residual data. */
-	else if (residual && residual->TotalMemory)
+	} else if (residual && residual->TotalMemory) {
+		puts("Residual? Shouldn't!\n");
 		TotalMemory = residual->TotalMemory;
 	/* Fall back to hard-coding 32MB. */
-	else
+	} else {
+		puts("Hard-coded\n");
 		TotalMemory = 32*1024*1024;
+	}
 
 
 	/* assume the chunk below 8M is free */

Thanks.

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

  reply	other threads:[~2003-10-14 23:25 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 [this message]
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
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=20031014232511.GA17741@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.