From owner-freebsd-hackers  Tue Aug 27 21:19:46 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA24983
          for hackers-outgoing; Tue, 27 Aug 1996 21:19:46 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24974
          for <hackers@freebsd.org>; Tue, 27 Aug 1996 21:19:42 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA29894; Tue, 27 Aug 1996 22:19:34 -0600 (MDT)
Date: Tue, 27 Aug 1996 22:19:34 -0600 (MDT)
Message-Id: <199608280419.WAA29894@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Sean Eric Fagan <sef@kithrup.com>
Cc: hackers@freebsd.org
Subject: Re: boot message about basemem and RTC
In-Reply-To: <199608280200.TAA15663@kithrup.com>
References: <199608280200.TAA15663@kithrup.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Okay... should I worry when it tells me that BIOS basemem != RTC basemem?
> (649k vs 640k, respectively...)

No, and I will be committing some code that'll make sure FreeBSD doesn't
walk on anything that might get messed up.  My desktop box used to spit
this out until I added my patch, and many laptops do this as well.  On
the ThinkPads, the 1K space is used by the APM bios.

For non-laptop machines it can be safely ignored, and for laptops it can
be mostly ignored.


Nate