From owner-freebsd-mobile@FreeBSD.ORG Wed Jul 26 03:57:25 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E004516A4E2 for ; Wed, 26 Jul 2006 03:57:25 +0000 (UTC) (envelope-from douglas_goodall@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F08743D46 for ; Wed, 26 Jul 2006 03:57:25 +0000 (GMT) (envelope-from douglas_goodall@mac.com) Received: from mac.com (smtpin04-en2 [10.13.10.149]) by smtpout.mac.com (Xserve/8.12.11/smtpout13/MantshX 4.0) with ESMTP id k6Q3vP3e011665 for ; Tue, 25 Jul 2006 20:57:25 -0700 (PDT) Received: from dougwide (pool-71-102-161-156.snloca.dsl-w.verizon.net [71.102.161.156]) (authenticated bits=0) by mac.com (Xserve/smtpin04/MantshX 4.0) with ESMTP id k6Q3v9rT008294 for ; Tue, 25 Jul 2006 20:57:24 -0700 (PDT) From: "Douglas W. Goodall" To: Date: Tue, 25 Jul 2006 20:57:18 -0700 Message-ID: <002601c6b067$9d7ddf70$6dce46c0@dougwide> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: AcawZ5aLEiUacABSSam7F4ejRuC95A== Subject: Regarding spurious IR7 Interrupts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 03:57:26 -0000 Intel 386 EX Embedded Microprocessor User's Manual Order Number 272485-002 Says: 9.4.3 Spurious Interrupts For both edge and level-triggered interrupts, a high level must be maintained on the IR line until after the falling edge of the first INTA# pulse (see Figure 9-18). A spurious interrupt request is generated if this stipulation is not met. A spurious interrupt on any IR line generates the same vector number as an IR7 request. The spurious interrupt, however, does not set the in-service bit for IR7. Therefore, an IR7 interrupt service routine must check the in-service register to determine whether the interrupt source was a valid IR7 (the in-service bit is set) or a spurious interrupt (the in-service bit is cleared). Respectfully, Douglas W. Goodall