From owner-freebsd-alpha  Thu May 31 11:22:51 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id A364437B423; Thu, 31 May 2001 11:22:48 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA03716;
	Thu, 31 May 2001 14:22:48 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f4VIMIs56094;
	Thu, 31 May 2001 14:22:18 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15126.35802.41704.920301@grasshopper.cs.duke.edu>
Date: Thu, 31 May 2001 14:22:18 -0400 (EDT)
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: alpha@FreeBSD.ORG
Subject: Re: PCI Interrupt Routing Broken on my Miata
In-Reply-To: <XFMail.010531103629.jhb@FreeBSD.org>
References: <XFMail.010531103629.jhb@FreeBSD.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-alpha.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-alpha>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-alpha>
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? 

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message