Hi Rene,
DVB-S2
I would have expected the relevant modules to be loaded after detecting
the bridge, and after ddbridge detecting the relevant HW behind. This is
apparently not happening, so how to trigger?
Cheers
Rudy
On 18-07-14 16:27, René wrote:
Hi Rudy,
ddbridge is a ... bridge. So it is an interface between PCIe and a
"DVB" device. So missing info is what frontend and demux (at least)
devices type. Is it DVB-C(2)/T(2)/S(2) ?
René
--------------------------------------------------
From: "Rudy Zijlstra" <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 18, 2014 3:28 PM
To: "Linux Media Mailing List" <linux-media@xxxxxxxxxxxxxxx>
Subject: ddbridge -- kernel 3.15.6
Dears,
I have a ddbridge device:
03:00.0 Multimedia controller: Device dd01:0003
Subsystem: Device dd01:0021
Flags: fast devsel, IRQ 17
Memory at f0900000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [90] Express Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000
Rev=0 Len=00c <?>
Kernel driver in use: DDBridge
The kernel recognises as seen in dmesg:
[ 1.811626] Digital Devices PCIE bridge driver, Copyright (C)
2010-11 Digital Devices GmbH
[ 1.813996] pci 0000:01:19.0: enabling device (0000 -> 0002)
[ 1.816033] DDBridge driver detected: Digital Devices PCIe bridge
[ 1.816273] HW 0001000d FW 00010004
But /dev/dvb remains empty, only /dev/ddbridge exists.
Any pointers are much appreciated
Cheers
Rudy
--
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
--
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
