From owner-freebsd-current Wed Sep 1 16: 5:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 719CD1558F for ; Wed, 1 Sep 1999 16:05:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01495; Wed, 1 Sep 1999 15:54:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909012254.PAA01495@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: Mike Smith , Garrett Wollman , nate@mt.sri.com (Nate Williams), Mitsuru IWASAKI , mmuir@es.co.nz, freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. In-reply-to: Your message of "Wed, 01 Sep 1999 16:52:11 MDT." <199909012252.QAA20666@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Sep 1999 15:54:49 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199909012245.PAA01429@dingo.cdrom.com> Mike Smith writes: > : It's reasonable to assume this, yes. However it's also worth bearing > : in mind that since the BIOS isn't using these interrupts to _detect_ > : activity, turning them off is pretty pointless. > > Then why does the key up event cause the suspend to fail? Because whatever mechanism the BIOS _is_ using to detect keyboard activity is catching it. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message