From owner-freebsd-current@FreeBSD.ORG Tue Jan 6 07:20:59 2004 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 4315216A4CE for ; Tue, 6 Jan 2004 07:20:59 -0800 (PST) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CBE343D1D for ; Tue, 6 Jan 2004 07:20:57 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 29472 invoked from network); 6 Jan 2004 15:20:55 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 6 Jan 2004 15:20:55 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i06FKqM0025495; Tue, 6 Jan 2004 10:20:52 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040105233941.GB39786@cicely12.cicely.de> Date: Tue, 06 Jan 2004 10:21:00 -0500 (EST) From: John Baldwin To: ticso@cicely.de X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: ticso@cicely12.cicely.de 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: Tue, 06 Jan 2004 15:20:59 -0000 On 05-Jan-2004 Bernd Walter wrote: > On Mon, Jan 05, 2004 at 04:33:45PM -0700, M. Warner Losh wrote: >> In message: <20040105233138.GR17023@cicely12.cicely.de> >> Bernd Walter writes: >> : On Mon, Jan 05, 2004 at 04:24:27PM -0700, M. Warner Losh wrote: >> : > In message: <20040105231533.GQ17023@cicely12.cicely.de> >> : > Bernd Walter writes: >> : > : The point is that it shouldn't take an IRQ for PCI which is configured >> : > : for an ISA device in device.hints. >> : > >> : > We don't do that. >> : >> : We do! >> : >> : /boot/device.hints: >> : hint.sio.0.irq="4" >> : >> : pci_cfgintr_virgin: using routable interrupt 4 >> : pci_cfgintr: 0:4 INTD routed to irq 4 >> >> Ah, I see what you are saying. That would be hard to implement. > > I already worried about this. > The BIOS has an implied veto for IRQ4 because it know this onboard > device and you could add veto IRQs for additional ISA components. > This table has no influence on FreeBSD. See, the BIOS is supposed to communicate that via $PIR. If it leaves IRQ 4 in $PIR, then it's broken. We can't read the BIOS's mind per se. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/