Still IRQ routing problems with bridged devices.
ticso at cicely12.cicely.de
Mon Jan 5 15:45:09 PST 2004
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 at cicely12.cicely.de>
> > Bernd Walter <ticso at cicely12.cicely.de> writes:
> > : On Mon, Jan 05, 2004 at 04:24:27PM -0700, M. Warner Losh wrote:
> > : > In message: <20040105231533.GQ17023 at cicely12.cicely.de>
> > : > Bernd Walter <ticso at 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 at bwct.de info at bwct.de
More information about the freebsd-current