From owner-freebsd-alpha Thu May 31 11:26: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 0347537B423 for ; Thu, 31 May 2001 11:25:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo.feral.com [192.67.166.71]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f4VIPvg56975 for ; Thu, 31 May 2001 11:25:57 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 31 May 2001 11:25:57 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: Re: PCI Interrupt Routing Broken on my Miata In-Reply-To: <15126.35802.41704.920301@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > OK, it turns out that its not as simple as I thought.. > pcib_route_interrupt() doesn't using my hack. I had a feeling my hack > was too simple. > > I think what we'll need to do to make all platforms work is to: > > a) Undo the breakage I just introduced > > b) Undo the platform changes that msmith made earlier this year when > this intr routing nonsense was introduced. By this, I mean that the > platform.pci_intr_map and all its implementations come back exactly as > they are in -stable > > c) Have all the chipset read_config routines call > alpha_platform_assign_pciintr() in the case of a read of INTLINE > alpha_platform_assign_pciintr() conses up cfgregs & calls the relavent > platform routine, or returns 255 > > > d) Have have alpha_pci_route_interrupt() call > alpha_platform_assign_pciintr(). > > Opinions? #d, yes- because it's only the specific platforms that know the right thing to do. Look at NetBSD. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message