From owner-freebsd-current Wed May 19 12:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id D6BEB14DEE for ; Wed, 19 May 1999 12:41:26 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA00959; Wed, 19 May 1999 14:41:14 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA03700; Wed, 19 May 1999 14:41:12 -0500 Message-ID: <19990519144111.52604@right.PCS> Date: Wed, 19 May 1999 14:41:11 -0500 From: Jonathan Lemon To: Mike Smith Cc: Luoqi Chen , ctapang@easystreet.com, current@FreeBSD.ORG, jerry.alexandratos@perspectives.net Subject: Re: FBSDBOOT.EXE References: <199905191729.NAA14869@lor.watermarkgroup.com> <199905191927.MAA00410@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199905191927.MAA00410@dingo.cdrom.com>; from Mike Smith on May 05, 1999 at 12:27:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 05, 1999 at 12:27:31PM -0700, Mike Smith wrote: > The issue here is that the BIOS will tell us how much memory we are > _allowed_to_use_, which is not always the same as the amount of > physical memory present in the system. Some memory may be (is > sometimes) reserved for use by eg. APM/ACPI. We fare badly at the > moment on these systems because we ignore this and use all the memory > we can find. Yup. That's probably the problem with the Thinkpads; the code patch I just sent out will dump the ACPI System Address map, so I can figure out what is happening. I bet that it declares one memory range for all the ram, and then overlays a second "reserved" address on top of it. Right now, I don't handle that correctly. It "should" be simple to write some code to aggregate this map and fill in the phys_avail[] structure; then the entire memory probe in machdep.c can go away. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message