From owner-freebsd-current Mon Aug 23 11:31:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8B9BA1585B; Mon, 23 Aug 1999 11:31:34 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA57510; Mon, 23 Aug 1999 14:29:59 -0400 (EDT) Message-Id: <199908231829.OAA57510@cs.rpi.edu> To: freebsd-current@freebsd.org Cc: new-bus@freebsd.org Subject: PCI interrupt routing in -Current/newbus Date: Mon, 23 Aug 1999 14:29:59 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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?!?. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message