Still IRQ routing problems with bridged devices.
M. Warner Losh
imp at bsdimp.com
Wed Dec 31 21:22:52 PST 2003
In message: <20040101013224.GC11668 at cicely12.cicely.de>
Bernd Walter <ticso at cicely12.cicely.de> 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
More information about the freebsd-current
mailing list