From owner-freebsd-current Wed Sep 1 15:54: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 88C2714BF8 for ; Wed, 1 Sep 1999 15:53:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA14063; Wed, 1 Sep 1999 16:52:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA20666; Wed, 1 Sep 1999 16:52:11 -0600 (MDT) Message-Id: <199909012252.QAA20666@harmony.village.org> To: Mike Smith Subject: Re: followup to apm problems. Cc: Garrett Wollman , nate@mt.sri.com (Nate Williams), Mitsuru IWASAKI , mmuir@es.co.nz, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 01 Sep 1999 15:45:00 PDT." <199909012245.PAA01429@dingo.cdrom.com> References: <199909012245.PAA01429@dingo.cdrom.com> Date: Wed, 01 Sep 1999 16:52:11 -0600 From: Warner Losh 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? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message