From owner-freebsd-hackers  Fri Apr 25 03:31:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA06649
          for hackers-outgoing; Fri, 25 Apr 1997 03:31:19 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA06628
          for <hackers@freebsd.org>; Fri, 25 Apr 1997 03:31:08 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA25681; Fri, 25 Apr 1997 20:26:35 +1000
Date: Fri, 25 Apr 1997 20:26:35 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704251026.UAA25681@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, tony@dell.com
Subject: Re: Can't put 512MB ram in box ... Extended memory question.
Cc: hackers@freebsd.org, witr@rwwa.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> A third, perhaps unseemly, possibility, that I haven't seen mentioned 
>> before, is to make the real-mode BIOS call from the kernel init code 
>> in the same way that the APM initilization BIOS call is made, by 
>> temporarily returning the CPU to real-mode after the kernel is loaded.  
>
>If that would allow me to read in initialization values from an
>optional file in the root filesystem, just as the kernel is read in,
>at the point where userconfig() is called in machdep.c, well, I'd vote
>for it with all flags waving.  The "userconfig save" feature broke

The current bootstrap already reads in values from /boot.config (my
boot.config contains "1:sd(0,a)kernel").  There has been little interest
in this so I haven't made it pass userconfig info to the kernel yet.

Bruce