From owner-freebsd-hackers Mon Nov 10 02:05:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19257 for hackers-outgoing; Mon, 10 Nov 1997 02:05:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA19251 for ; Mon, 10 Nov 1997 02:05:52 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA18323; Mon, 10 Nov 1997 04:00:37 -0600 Message-Id: <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Mon, 10 Nov 1997 03:45:09 -0600 To: Mike Smith From: Tony Overfield Subject: Re: >64MB Cc: John-Mark Gurney , Chuck Robey , Terry Lambert , jamil@trojanhorse.ml.org, hackers@freebsd.org, Jonathan Mini In-Reply-To: <199711070205.MAA00455@word.smith.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:34 PM 11/7/97 +1030, Mike Smith wrote: >The kernel is loaded above 1M, so you would have to be careful to make >sure that your BIOS calls came out of the lowest 64K. That could be >done with a dispatcher in locore.s though. I assume you mean the lowest 640K. But yes, a dispatcher would have to exist down there, with a buffer large enough for your INT 13h calls and etc. >The other reason is that I don't know how to make the change. 8) If I >did, I'd certainly consider it, although vm86 has a few other uses that >argue for using it just out of commonality. Have you seen this? /pub/NetBSD-current/src/sys/arch/i386/bioscall/biostramp.S I don't know if it works, but it looks simple enough. I do realize it offends the sensibilities of some real-mode fearing folks. If you can't trust the BIOS after the kernel is in memory, how can you trust it to load the kernel into memory? While the kernel is still "booting...", the BIOS should be safe enough to call in real-mode. - Tony