From owner-freebsd-current Wed Sep 1 12:37:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4A3221550B for ; Wed, 1 Sep 1999 12:37:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA37421; Wed, 1 Sep 1999 21:36:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Garrett Wollman , Warner Losh , 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 12:26:34 PDT." <199909011926.MAA00398@dingo.cdrom.com> Date: Wed, 01 Sep 1999 21:36:18 +0200 Message-ID: <37419.936214578@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909011926.MAA00398@dingo.cdrom.com>, Mike Smith writes: >> In message <199909011345.JAA05781@khavrinen.lcs.mit.edu>, Garrett Wollman writes: >> >< said: >> > >> >> Actually, that's almost entirely system-dependant. The BIOS may well >> >> poll the keyboard controller/USB controller, for example. >> > >> >And designs based on the Intel PIIX4 will generate SMI# interrupts for >> >whichever activities are programmed in the BIOS, completely bypassing >> >the traditional interrupt mechanism. >> >> And these interrupts will take as much as 50usec to service... > >Since in the context that we're discussing the system is asleep, I can't >actually see how this is in any way relevant... Because SMI interrupts happen all the time, not just when it is asleep :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message