From: David W. <dw...@in...> - 2003-06-17 22:09:33
|
On Tue, 2003-06-17 at 19:58, Paul van Gool wrote: > BTW turning on PCI debugging I see the following: > PCI: Error mapping IRQ on device ... > PCI: Bad IRQ mapping request for slot ... Hmmm. That looks unhappy but leave it for now -- we can deal with interrupts once you have the resource allocation working and can actually talk to the hardware in question. > PCI: pcibios_allocate_resources pass 0 called > PCI: Resource 00001000-00001fff (f=1208, d=0, p=0) > PCI: Resource 00000020-0000003f (f=101, d=0, p=0) > PCI: Resource 00000080-000000ff (f=101, d=0, p=0) > PCI: Resource 00000100-0000013f (f=101, d=0, p=0) > PCI: Resource 00000140-0000015f (f=101, d=0, p=0) > PCI: Resource 00002000-00002fff (f=200, d=0, p=0) OK, the resources it's allocating there are completely bogus as far as I can tell. Can you double-check the values of PCIBIOS_MIN_MEM and PCIBIOS_MIN_IO as seen in drivers/pci/setup-res.c::pci_assign_resource() Make it stop assigning resources which your board I/O code doesn't think are PCI, and you'll be most of the way there :) > So it seems my WiFi card has the same IRQ as my Ethernet card (13) and that > the sound card is having trouble mapping its IRQ. Sharing IRQs is fine. My SH3 box has everything on IRQ 0 :) > > pvg slot 00:00.0 > ... > pvg slot 00:00.0 > ... > pvg slot 00:00.0 > ... > pvg slot 00:00.0 > ... > pvg slot 00:0f.0 > OK so the only devices for which it found pre-existing resource allocations and kept them were the host bridge (00:00.0) and the USB controller (00:0f.0). It's not relevant to the cards with which you're having problems -- although it is probably broken in theory. Ignore it for now and fix the resource allocation when it _is_ assigning resources. One thing at a time... :) -- dwmw2 |