From owner-freebsd-hackers Thu Nov 6 05:48:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14579 for hackers-outgoing; Thu, 6 Nov 1997 05:48:22 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14567 for ; Thu, 6 Nov 1997 05:48:16 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.7/8.8.5) with SMTP id HAA07313; Thu, 6 Nov 1997 07:40:22 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Thu, 6 Nov 1997 07:40:21 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Mike Smith cc: Tony Overfield , Terry Lambert , jamil@trojanhorse.ml.org, hackers@FreeBSD.ORG Subject: Re: >64MB In-Reply-To: <199711061242.XAA00382@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 6 Nov 1997, Mike Smith wrote: > > > > Speaking of vm86(), why not just use real-mode? It's easier and much > > better for compatibility while booting. > > How do you copy the kernel into memory > 1M in real mode? If you could > elaborate on this (and how to *stay* in real mode while running over > 1M, ie. so that the kzip pass and subsequent real-mode startup > requirements could be met), I'd be *very*happy* Huh? Is that the limitation? I haven't personally used them, but there are methods to do this, if you can go into protected mode first, set limits, then go back to real mode. Can you do that one? If so, I'll personally test such a thing, I can do that here. The method I'm talking about is commonly known (among those that use it) as voodoo memory, I think. The word voodoo is in there somewhere, anyways. Some game folks have written programs that run completely in such a environment, although that seems really unsafe to me. The limits you set in pmode stay active in real-mode. I haven't addressed this before, so if this is completely off-base, you can ignore me. > > > The APM init code seems to have a good example of > > making real-mode BIOS calls from the kernel during initialization. > > ??!! You should actually take a look at it some day, I think. The APM > real-mode code sucks. > > One of my greatest desires is actually to move it from very early (in > locore) to very late (after the vm86daemon is started), and do the > initial startup from vm86 mode. This is the same way that the SMB > BIOS will (hopefully) be started. First thing though is getting vm86 > working for this in the kernel... > > I *know* you're well informed on these matters, but also busy. However > any assistance you may be able to offer would be not only appreciated > but _used_. > > mike > (Yes, I've been keeping various references from your messages... 8) > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------