Date: Tue, 6 Jan 2004 00:44:31 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: "M. Warner Losh" <imp@bsdimp.com> Cc: current@FreeBSD.org Subject: Re: Still IRQ routing problems with bridged devices. Message-ID: <20040105234430.GC39786@cicely12.cicely.de> In-Reply-To: <20040105233941.GB39786@cicely12.cicely.de> References: <20040105231533.GQ17023@cicely12.cicely.de> <20040105.162427.30502300.imp@bsdimp.com> <20040105233138.GR17023@cicely12.cicely.de> <20040105.163345.129782176.imp@bsdimp.com> <20040105233941.GB39786@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 06, 2004 at 12:39:42AM +0100, 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 <ticso@cicely12.cicely.de> writes: > > : On Mon, Jan 05, 2004 at 04:24:27PM -0700, M. Warner Losh wrote: > > : > In message: <20040105231533.GQ17023@cicely12.cicely.de> > > : > Bernd Walter <ticso@cicely12.cicely.de> 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. After rethinking - it wouldn't be a good idea either, because GENERIC.hints would block to many possible IRQs :( Too bad that ISA components have to be attached after PCI. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040105234430.GC39786>