From owner-freebsd-current  Mon Sep 28 15:57:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA15415
          for freebsd-current-outgoing; Mon, 28 Sep 1998 15:57:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15355
          for <current@FreeBSD.ORG>; Mon, 28 Sep 1998 15:56:55 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA13260;
	Tue, 29 Sep 1998 08:56:36 +1000
Date: Tue, 29 Sep 1998 08:56:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809282256.IAA13260@godzilla.zeta.org.au>
To: bde@zeta.org.au, nate@mt.sri.com
Subject: Re: VM86 and APM
Cc: current@FreeBSD.ORG, tlambert@primenet.com,
        yokota@zodiac.mech.utsunomiya-u.ac.jp
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Also, apm configured/disabled system don't necessary use the i8254
>timecounter unless they use the APM_BROKEN_STATCLOCK option (which is
>turned on by default, but is not a requirement.)

Yes they do.  Read what I wrote.  This has nothing to do with
APM_BROKEN_STATCLOCK.

>However, Bruce is correct that *IF* the APM BIOS is both configured in
>the BIOS *AND* disabled in UserConfig then some of the side-effects ares
>not completely disabled in FreeBSD.

There are side effects in some cases even if the APM BIOS doesn't
exist, since sometimes nothing is done to change apm_version from 0
to AMPMINI_CANTFIND.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message