Date: Sun, 27 Sep 1998 21:32:56 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Terry Lambert <tlambert@primenet.com> Cc: Nate Williams <nate@mt.sri.com>, yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: VM86 and APM Message-ID: <19980927213256.46318@right.PCS> In-Reply-To: <199809280101.SAA08172@usr05.primenet.com>; from Terry Lambert on Sep 09, 1998 at 01:01:41AM %2B0000 References: <199809280029.SAA14347@mt.sri.com> <199809280101.SAA08172@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 09, 1998 at 01:01:41AM +0000, Terry Lambert wrote: > > > I think the APM VM86() call will detect this because it uses > > > BIOS-specific code that knows about the CMOS setting, but the > > > non-VM86() code ignores the CMOS setting (which can cause other, > > > interesting problems, like being able to suspend, but the laptop > > > not waking up on an event that should result in a "resume"). > > > > Not. We used to use our own VM86 switcher to do the probe earlier, and > > Mike converted to use the GENERIC VM86 switcher. If it worked before, > > it *should* work now (modulo any bugs, which is essentially the > > problem the poster is pointing out). > > Mea culpa. > > The only thing I can hazard a guess on this, then, is that with > VM86, the apm stuff is called much earlier in locore.s than it > is without it... Actually, it's called later. The custom vm86 code in apm probed apm from locore whenn booting (IIRC), and just returned the status code from this during the "probe" routine later in the boot process. The new vm86 code actually tries to connect to apm at probe time. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980927213256.46318>