[mythtv-users] DVB delivery systems

[Mike Perkins]

On 21/09/15 12:07, Stuart Auchterlonie wrote:
> On 20/09/15 10:20, Devin Heitmueller wrote:
>>> As I recall (it's been a while since I last configured my tuners) the
>>> different standards (T vs. C) are exposed as different device nodes, but
>>> don't quote me on that.
>>
>> This only applies to devices where there are two separate demodulator
>> chips in the device.  If the device has a single demod which supports
>> both DVB-T and DVB-C, then it still gets represented as a single
>> frontend device node and you have to tell it which mode to operate in.
>>
>> That said, I don't know whether MythTV ever got around to setting the
>> delivery system.
>>
>
> I'm pretty sure we are going to have to add explicit support for this.
>
Following up on my somewhat vague message above, I have now had the chance to 
access my backend and dmesg gives me:

[   10.246892] Linux video capture interface: v2.00
[   10.255654] dib0700: loaded with support for 21 different device-types
[   10.256235] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
[   10.256379] dvb-usb: will pass the complete MPEG2 transport stream to the 
software demuxer.
[   10.257499] DVB: registering new adapter (Hauppauge Nova-T Stick)
[   10.318566] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, 
interface 0, class 0)
[   10.318689] em28xx #0: chip ID is em28174
[   10.464567] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[   10.625437] em28xx #0: Identified as PCTV nanoStick T2 290e (card=78)
[   10.674933] DiB0070: successfully identified
[   10.700072] Registered IR keymap rc-pinnacle-pctv-hd
[   10.700327] input: em28xx IR (em28xx #0) as 
/devices/pci0000:00/0000:00:02.1/usb1/1-3/rc/rc0/input3
[   10.700526] rc0: em28xx IR (em28xx #0) as 
/devices/pci0000:00/0000:00:02.1/usb1/1-3/rc/rc0
[   10.700934] em28xx #0: v4l2 driver version 0.1.3
[   10.705740] em28xx #0: V4L2 video device registered as video0
[   10.705813] usbcore: registered new interface driver em28xx
[   10.705818] em28xx driver loaded
[   10.724077] Registered IR keymap rc-dib0700-rc5
[   10.724445] input: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:02.1/usb1/1-5/rc/rc1/input4
[   10.725229] rc1: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:02.1/usb1/1-5/rc/rc1
[   10.725453] dvb-usb: schedule remote query interval to 50 msecs.
[   10.725463] dvb-usb: Hauppauge Nova-T Stick successfully initialized and 
connected.
[   10.725573] dib0700: rc submit urb failed
[   10.725578]
[   10.728662] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
[   10.728847] dvb-usb: will pass the complete MPEG2 transport stream to the 
software demuxer.
[   10.730125] DVB: registering new adapter (Hauppauge Nova-T Stick)
[   10.940322] DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...

...

[   12.267085] tda18271 6-0060: creating new instance
[   12.271685] TDA18271HD/C2 detected @ 6-0060
[   12.526085] tda18271 6-0060: attaching existing instance
[   12.526096] DVB: registering new adapter (em28xx #0)
[   12.526106] DVB: registering adapter 2 frontend 0 (Sony CXD2820R (DVB-T/T2))...
[   12.526313] DVB: registering adapter 2 frontend 1 (Sony CXD2820R (DVB-C))...
[   12.533764] em28xx #0: Successfully loaded em28xx-dvb
[   12.533775] Em28xx: Initialized (Em28xx dvb Extension) extension

It's not clear from the order of messages since it appears to be initializing 
three tuners at once but I'm guessing the (DVB-T/T2) and (DVB-C) messages refer 
to the pc-290e, proving it has separate endpoints for those modes.

-- 

Mike Perkins