From owner-freebsd-hackers Tue Nov 3 04:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01266 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:31:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01249 for ; Tue, 3 Nov 1998 04:31:11 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id OAA20788; Tue, 3 Nov 1998 14:28:57 +0200 (SAT) From: John Hay Message-Id: <199811031228.OAA20788@zibbi.mikom.csir.co.za> Subject: Re: chaining interrupt handler In-Reply-To: <199811031159.MAA00990@borg.kryptokom.de> from Etienne de Bruin at "Nov 3, 98 12:59:39 pm" To: Etienne.Debruin@KryptoKom.DE (Etienne de Bruin) Date: Tue, 3 Nov 1998 14:28:57 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > > my questions is, how does one chain one's interupt handler together > with all the other exisiting interupt handler routines? > > i.e. > > void fc_pci_intr() > { > if certain flags set { > handle interupt > } > else { > chain interrupt > } > } You shouldn't need the else part. The generic pci handler should do that for you. That way you don't even have to know which device is sharing the interrupt with you. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message