From owner-freebsd-hackers Wed Aug 27 19:37:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA01913 for hackers-outgoing; Wed, 27 Aug 1997 19:37:40 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA01908 for ; Wed, 27 Aug 1997 19:37:37 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00423; Thu, 28 Aug 1997 12:06:25 +0930 (CST) Message-Id: <199708280236.MAA00423@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Gary Kendall cc: Mike Smith , freebsd-hackers@freebsd.ORG Subject: Re: Sizing mem > 64MB at boot-time In-reply-to: Your message of "Mon, 25 Aug 1997 15:05:53 -0400." <199708251905.PAA00599@ccomp.inode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Aug 1997 12:06:25 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk > I saw Jonathan's post re real-mode access from the kernel, and I got a > copy of the code (which should prove to be quite usefull for DOS emulation), > but it won't solve the problem I'm trying to solve. I want the boot program > to size the memory so that the kernel, during initialization, can use the > memory size to allocate buffers, etc. Jonathan's code doesn't come into > play until the machine has already booted the kernel, and is executing it. > His real-mode code is through a system call interface, and as such, happens > "too late" for my purposes. Gotcha. > However, it would be nice if someone familiar with the biosboot code > and/or Intel processors could look at what I have written and point me in > the right direction with respect to accessing a buffer while in real-mode. I've been looking for this sort of help for a while; I think Jonathan is still The Man to see about this. If you're serious about the three-stage-boot thing, then there are lots of things have been said about it; you should start by looking at the standalone libraries that the NetBSD people have, and then come back and we can talk 8) mike