[dvblast-devel] CA device addressing

[Christophe Massiot]

I don’t think there is a way to achieve what you want without patching the source and adding options to specify frontend and CA devices. Actually, I didn’t think what you wanted to achieve was possible at all ;).

> On 10 Aug 2015, at 12:10, Kompan Kolia <kompan at yandex.ru> wrote:
> 
> I try to use mknod for "symlink" of /adapter1/ca0 as /adapter0/ca1
> It`s work with -y option.
> 
> In this case I need two instance of dvblast.
> One for receive signal from adapter0 and cam0
> Second for receive signal from adapter0 and cam1 (symlink of adapter1/ca0)
> 
> But second instance can`t start because frontend0 is use. 
> 
> 10.08.2015, 12:59, "Doychin Dokov" <dokov at silistra.tv>:
>> I believe TBS cards are not capable of what you want to achieve - each CA slot is hardwired to the appropriate tuner and not routable the way you want it.
>> 
>> - D.
>> 
>> 2015-08-10 12:50 GMT+03:00 Kompan Kolia <kompan at yandex.ru>:
>>> Sorry for repeating, but previous letter was in HTML format, and I don`t receive any comments.
>>> 
>>> Hello All :)
>>> 
>>> I have system with few TBS (TBS 6991SE) with two inputs.
>>> 
>>> This cards are made like two tuners on one board.
>>> Each card consists of two tuners and two CI slots
>>> 
>>> After system boot in /dev/dvb folder looks like that:
>>> 
>>> /dev/dvb/adapter0:
>>> total 0
>>> crw-rw---T 1 root video 212, 53 Jul 13 17:25 ca0
>>> crw-rw---T 1 root video 212, 50 Jul 13 17:25 demux0
>>> crw-rw---T 1 root video 212, 51 Jul 13 17:25 dvr0
>>> crw-rw---T 1 root video 212, 54 Jul 13 17:25 frontend0
>>> crw-rw---T 1 root video 212, 52 Jul 13 17:25 net0
>>> 
>>> /dev/dvb/adapter1:
>>> total 0
>>> crw-rw---T 1 root video 212, 58 Jul 13 17:25 ca0
>>> crw-rw---T 1 root video 212, 55 Jul 13 17:25 demux0
>>> crw-rw---T 1 root video 212, 56 Jul 13 17:25 dvr0
>>> crw-rw---T 1 root video 212, 59 Jul 13 17:25 frontend0
>>> crw-rw---T 1 root video 212, 57 Jul 13 17:25 net0
>>> 
>>> We want to achieve following:
>>> 
>>> First instance of dvblast:
>>> 1 Receives encrypted DVB-S2 signal from the first input (/dev/dvb/adapter0/frontend0)
>>> 2 CA0 (/dev/dvb/adapter0/ca0) decrypts it.
>>> 
>>> Second instance of dvblast:
>>> 1 Receives encrypted DVB-S2 signal from the same FIRST input (/dev/dvb/adapter0/frontend0)  (the same transponder)
>>> 2 CA0 from second card (/dev/dvb/adapter1/ca0) decrypts it.
>>> 
>>> Third instance of dvblast:
>>> Receives unencrypted FTA DVB-S2 signal from second input (/dev/dvb/adapter1/frontend0) from some other transponder.
>>> 
>>> We know about -y (--ca) feature, but it does not work for us, because second CA (adapter1/ca0) assigned to other DVB-tuner (adapter1) during boot.
>>> 
>>> Is there any solution or workaround for specifying input source for receive stream and CA to decode it.
>>> 
>>> Example:
>>> 
>>> ######### For First Input #################
>>> 
>>> dvblast  -a 0 -f xxxxx -s xxxxxx -v 13 -c /dvblast.cfg
>>> 
>>> ------------ dvblast.cfg ------------
>>> 
>>> # Channel 1, /adapter0/frondend0, /adapter0/ca0
>>> 
>>> 224.5.5.1:1234 1 216
>>> 
>>> # Channel 2, /adapter0/frondend0, /adapter1/ca0
>>> 224.5.5.2:1234/ca=/adapter1/ca0 1 217
>>> 
>>> ------- end of dvblast.cfg ----------
>>> 
>>> ######### END For First Input #################
>>> 
>>> ######### For Second Input #################
>>> 
>>> dvblast  -a 0 -f xxxxx -s xxxxxx -v 13 -c /dvblast.cfg
>>> 
>>> ------------ dvblast.cfg ------------
>>> # Channel 1, /adapter1/frondend0
>>> 
>>> 224.5.5.1:1234 0 210
>>> 
>>> ------- end of dvblast.cfg ----------
>>> 
>>> ######### END For Second Input #################
>>> 
>>> or something else.
>>> 
>>> Thank for advise.
>>> _______________________________________________
>>> dvblast-devel mailing list
>>> dvblast-devel at videolan.org
>>> https://mailman.videolan.org/listinfo/dvblast-devel
>> 
>> ,
>> 
>> _______________________________________________
>> dvblast-devel mailing list
>> dvblast-devel at videolan.org
>> https://mailman.videolan.org/listinfo/dvblast-devel
> _______________________________________________
> dvblast-devel mailing list
> dvblast-devel at videolan.org
> https://mailman.videolan.org/listinfo/dvblast-devel