From owner-freebsd-hackers Wed Nov 11 20:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22638 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 20:34:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22633 for ; Wed, 11 Nov 1998 20:34:48 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA14636 for ; Thu, 12 Nov 1998 15:04:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 12 Nov 1998 15:00:09 +1030 (CST) From: "Daniel O'Connor" To: freebsd-hackers@FreeBSD.ORG Subject: PCI interrupts Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We make a custom data acquisition PCI card, and we are experiencing some problems :) I am wondering if anyone could tell me how FreeBSD would handle having the PCI interrupt line continually asserted after calling the interrupt handler for the device in question. ie would the interrupt routine keep getting called? or would it only get called once? This probably intersects with PCI specifics as well, so I'll mail the PCI mailing list too.. Any help gratefully received.. I could probably send you some real Australian beer if you want =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message