From owner-freebsd-alpha Fri Nov 17 4:22:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (unknown [167.216.157.206]) by hub.freebsd.org (Postfix) with ESMTP id 3F81637B479 for ; Fri, 17 Nov 2000 04:22:35 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAHCTHF11040 for ; Fri, 17 Nov 2000 04:29:17 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011171229.eAHCTHF11040@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Subject: PCI interrupt routing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Nov 2000 04:29:17 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks; in a conversation a little while back it was suggested that PCI interrupt routing for the Alphas would actually be pretty straightforward. What I don't recall is whether the comments implied that interrupt routing was likely to be constant per chipset or per platform. I want to implement the pcib_route_interrupt handler for Alpha chipsets to remove the i386 define in pci/pci.c, and provide an interface for correctly swizzling these. I guess that ideally I just want a per-whatever table of hose/bus/slot/intpin -> intline mappings, and a common lookup function that knows what the current 'whatever' is. What should 'whatever' be? Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message