From owner-freebsd-hackers Mon Dec 7 12:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12384 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 12:32:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-22-dbn.dial-up.net [196.34.155.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12374 for ; Mon, 7 Dec 1998 12:32:37 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA00262; Mon, 7 Dec 1998 22:31:10 +0200 (SAT) From: Robert Nordier Message-Id: <199812072031.WAA00262@ceia.nordier.com> Subject: Re: How could this work? In-Reply-To: <199812072007.NAA05124@harmony.village.org> from Warner Losh at "Dec 7, 98 01:07:30 pm" To: imp@village.org (Warner Losh) Date: Mon, 7 Dec 1998 22:31:02 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > I was looking at the libretto confin program that was just ported to > FreeBSD via the ports mechanism. It has code that looks like: > > movl 8(%ebp),%eax > movl 12(%ebp),%ebx > movl 16(%ebp),%ecx > inb $0x0b2,%al /* invoke SMI */ > > How the heck can that work? I'm confused... IIRC, reads and writes involving port 0xb2 are done for their side-effects (to cause an SMI, put CPU into sleep mode, etc). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message