On Tue, Feb 15, 2011 at 4:23 PM, Dennis Kurten <[email protected]> wrote:
> Hello Andy, I've tried some of your suggestions, but no luck so far.
>
>
> On Tue, Feb 15, 2011 at 4:09 AM, Andy Walls <[email protected]> wrote:
>> On Mon, 2011-02-14 at 13:35 +0200, Dennis Kurten wrote:
>>> Hello,
>>>
>>> This card (technisat cablestar hd 2 dvb-c) works fine when plugged
>>> into a native PCI slot. When I try it with a PCI-adapter I intend to use in
>>> mITX-builds there doesn't seem to be any data coming in through the
>>> tuner. The adapter is a transparent bridge (with a PEX 8112 chip) that
>>> goes into a 1xPCIe-slot and gets power through a 4-pin molex.
>>>
>>> [...]
>>>
>>> Kernel is 2.6.32 (+the compiled drivers)
I have upgraded my system to 2.6.35 so now I'm using "vanilla drivers" but
the problem remains: Works fine in PCI - doesn't in PCIE behind adapter.
>>> [...]
>>>
>>> Latency: 32 (2000ns min, 63750ns max)
>>> Interrupt: pin A routed to IRQ 16
>>> Region 0: Memory at fdcff000 (32-bit, prefetchable) [size=4K]
>> ^^^^^^^^^^^^
>>
>> Heh, I always find it curious when I/O peripherials claim their register
>> space is prefetchable (the CX23416 does this as well). If the chip is
>> designed right, it is valid though AFAICT.
>>
And is there any point with prefetchable mechanisms if bus mastering
is employed? This is what the adapter reports:
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fdd00000-fddfffff
Prefetchable memory behind bridge: fdc00000-fdcfffff
I'd have thought that the memory behind the bridge would include any
prefetchable segment. The tuner card happens to registers within that
"0xfdc"-segment too.
> [...]
>
> from /cat/interrupts:
> -----------------------
> 16: 9751 0 IO-APIC-fasteoi ahci, nvidia, Mantis
>
> [...]
The above shared interrupt assignment is the same for both cases. There
is however a difference how the interrupt link is set up:
Mantis 0000:05:06.0: PCI INT A -> Link[APC1] ... (<-- without bridge)
vs.
Mantis 0000:04:00.0: PCI INT A -> Link[APC7] ... (<-- with bridge)
Don't know if the different APC# is of any significance here.
Regards,
Dennis
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
