Re: PCI riser cards and PCI irq routing, etc

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Wed, Feb 21, 2007 at 10:24:28AM +0100, Udo van den Heuvel wrote:
> Udo van den Heuvel wrote:
> > Any ideas about how to proceed?
> > What to test?
> 
> I found some info on the VIA dual PCI extender card at
> http://www.itx-warehouse.co.uk/Product.aspx?ProductID=410.
> The text says:
> 
> The EXT-PCI is a PCI riser card which expands a PCI slot into two PCI slots.
> 
> EXT-PCI slot 1 (lower slot) uses the system resources (Device ID, INT)
> of the PCI slot of the motherboard.
> 
> EXT-PCI slot 2 (Upper slot) uses device 19 and INT_A.
> 
> 
> 
> So if my non-VIA riser card can use DN 19 and also INT_A things should work?
> (assuming that VIA Epia EN BIOS 1.07 is enough to use this card)
> 
> So, if not (as in my situation) how can I find out what is wrong?
> Or find out if the BIOS works OK with the card?
> How can I verify that the correct routing for the IRQ is in place?
> The DN is the only variable so INT lines are hardwired on the riser card?
> Then same for the motherboard.

It is quite likely that the interrupts are set based on the DN.  Now if
they use whatever the parent slot uses as INTD as INTA for the second
slot (since it is set to 19 which is 1 below 20 of the main slot), then
that probably isn't what the BIOS is likely to assign.  It really sounds
like via decided to do things their own way and only riser cards done
their way, or riser cards with a pci to pci bridge are going to work
with it.

> I.o.w.: how can I find the root cause?

Does the documentation say which interrupts are INTA, B, C and D on the
main board?  I would expect slot 20 to have INTA mapped to INTA but then
again being a weird main board it doesn't have to be that way.  It is
certainly possible via decided to just support DN19 and 20 and assign
them both INTA, which would certainly make for a very simple riser card.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/