From owner-freebsd-alpha Thu Feb 24 13:14:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D6BF737B9C0 for ; Thu, 24 Feb 2000 13:13:59 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA14416; Thu, 24 Feb 2000 16:12:53 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA49692; Thu, 24 Feb 2000 16:12:22 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Feb 2000 16:12:21 -0500 (EST) To: mjacob@feral.com Cc: Vladimir Kravchuk , Doug Rabson , freebsd-alpha@FreeBSD.ORG Subject: Re: UP2000/DP264 In-Reply-To: References: <14517.39997.734455.74296@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14517.40509.360595.957164@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > fWIW, I see 2GB fine on an alpha 8200. > As do the TestDrive people on their XP1000. I think the problem might be that we unconditionally return 1 in pmap_uses_prom_console(). I might be missing something in a quick read, but I do not see how we can go back & read a second MDDT_SYSTEM cluster after we've read the first system cluster and physmem has been set to a non-zero value. I think this guy's problem might be that he's got his 2GB spread across 2 clusters with system tags. The patch I mailed him makes pmap_uses_prom_console return 0 in his case, which should allow the detection of a second system cluster. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message