From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 21:22:52 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10E2716A4CE for ; Wed, 31 Dec 2003 21:22:52 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92E9443D62 for ; Wed, 31 Dec 2003 21:22:50 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i015MjAI016544; Wed, 31 Dec 2003 22:22:45 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 31 Dec 2003 22:22:30 -0700 (MST) Message-Id: <20031231.222230.01438468.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: "M. Warner Losh" In-Reply-To: <20040101013224.GC11668@cicely12.cicely.de> References: <20040101013224.GC11668@cicely12.cicely.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Still IRQ routing problems with bridged devices. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2004 05:22:52 -0000 In message: <20040101013224.GC11668@cicely12.cicely.de> Bernd Walter writes: : The board is an old Asus T2P4 with 3 bridged cards and $PIR table. : All IRQs behind bridges get bogusly IRQ4 instead of the right ones. : Is this only a problem on some boards or do we have a general irq : routing problem with bridges? It is a problem with some bridges and PCI BIOS interrupt routing. : At least I know that bridge irq routing works fine on alpha. : $PIR table claims to only have 7 entries - does this make sense for : a 4 slot board? Maybe you could post it. It makes sense if you have on-board PCI devices. : If this is a board specific problem - can we at least add a loader : variable to disable routing, so I don't have to patch the source on : every update and can run a standart boot disk again? Did it used to work when we were re-routing all the time? It would be easy to add this as an option, but maybe understanding your setup might help a little to make our routing code a little smarter. Warner