Date: Wed, 19 May 1999 14:41:11 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Mike Smith <mike@smith.net.au> Cc: Luoqi Chen <luoqi@watermarkgroup.com>, ctapang@easystreet.com, current@FreeBSD.ORG, jerry.alexandratos@perspectives.net Subject: Re: FBSDBOOT.EXE Message-ID: <19990519144111.52604@right.PCS> In-Reply-To: <199905191927.MAA00410@dingo.cdrom.com>; from Mike Smith on May 05, 1999 at 12:27:31PM -0700 References: <199905191729.NAA14869@lor.watermarkgroup.com> <199905191927.MAA00410@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990519144111.52604>