From owner-freebsd-new-bus Mon Aug 23 13:36:54 1999 Delivered-To: freebsd-new-bus@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FEF31501B; Mon, 23 Aug 1999 13:36:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA59830; Mon, 23 Aug 1999 21:45:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 23 Aug 1999 21:45:24 +0100 (BST) From: Doug Rabson To: "David E. Cross" Cc: freebsd-current@freebsd.org, new-bus@freebsd.org Subject: Re: PCI interrupt routing in -Current/newbus In-Reply-To: <199908231829.OAA57510@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, David E. Cross wrote: > How are PCI interrupts routed in CURRENT/NewBus? For example almost all of > my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI > world, but how does the interrupt dispatch routine decide which ints to > route where? I recently put a panic() in a intr routine of mine just to > see the call stack, but all it showed has Xintr11 (which upon grepping the > source found no matches, but a nm /kernel did find it?!?. The bios informs the kernel what irq each device is mapped to and we build a chain of interrupt handlers for each one. All the handlers registered for a given irq are called when it fires. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message