> OK. Here we see the confluance of two problems. First, irq 0 is
> bogus and likely illegal per the pci spec for devices that do
> interrupt. Even if it isn't illegal, it is wrong wrong wrong wrong,
> but lots of people do it. I have a patch for -stable, but not for
> current.
Well, the car
In message <[EMAIL PROTECTED]> Andy Sparrow writes:
: pci_cfgintr_search: linked (62) to configured irq 0 at 0:31:0
: pci_cfgintr: 0:30 INTC routed to irq 0
: pcib2: routed slot 5 INTA to irq 0
: pcic0: irq 0 at device 5.0 on pci2
: pcib2: device pcic0 requested unsupported memory range 0x440
In message <[EMAIL PROTECTED]> Andy Sparrow writes:
: > Gotta love one problem report hitting 5 problems all at once :-)
:
: You do? :-/
Yes, and I wasn't even counting your sound problems :-)
hopefully I can resolve at least the interrupt routing issue soonish.
Would you be game to be a guinee