On 03/15/2010 01:50 PM, Martin van Es wrote: > When I look at the pci layout, pci device 05 is connected to bridge 1e.0: > -[0000:00]-+-00.0 > +-1e.0-[05]--+-00.0 Philips Semiconductors SAA7146 > | \-0c.0 Philips Semiconductors SAA7146 No, this means bridge 1e.0 connects to bus number 05. > So I started to suspect that the motherboard had no way to know what > PCI int's were used behind the bridge if both cards were detected to serve > INTA (i.e. 05.0x = INTA in lspci -v) and would thus (quite stupidly?) > route any int for this slot to INTA? I don't get that sentence.. Every slot has INTA/B/C/D and each PCI function announces which one of these it uses. In most cases INTA is used. The board manufacturer for bus 05 only knows how INTx maps to APIC inputs for slot 00. He knows there are people who use riser cards, so he adds mappings for non-existent slots by permuting those interrupts available to slot 00. > Last change was to cut the original slot2 connection to INTD and gone were my > extra interrupts! It might be INTD isn't connected to the APIC. It is rarely used on cards. > So now I have two correctly recognised cards, both using int 20 and PCI INTA. > Now I wonder if this will harm the performance if both cards are recording > streams, let alone if they work, because that's the next test I still have to > do. It should work. On interrupt the driver will be called once for each card to check if the card in question caused the interrupt. As long as we are not talking about thousands of interrupts per second, this shouldn't harm performance. Daniel -- Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com Fon +49 551 30664-0, Fax -11, Bahnhofsallee 1b, 37081 Göttingen, Germany Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160 Geschäftsführer: Dr. Uwe Kracke, Ust-IdNr.: DE 205 198 055 emlix - your embedded linux partner -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
