Re: [PATCH] Ngene cam device name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/12/2011 03:57 PM, Martin Vidovic wrote:
> Andreas Oberritter wrote:
>> On 03/12/2011 03:10 PM, Issa Gorissen wrote:
>>  
>>> From: Andreas Oberritter <obi@xxxxxxxxxxx>
>>>    
>>>> On 03/11/2011 10:44 PM, Martin Vidovic wrote:
>>>>      
>>>>> Andreas Oberritter wrote:
>>>>>        
>>>>>> It's rather unintuitive that some CAMs appear as ca0, while others as
>>>>>> cam0.
>>>>>>             
>>>>> Ngene CI appears as both ca0 and cam0 (or sec0). The ca0 node is used
>>>>> as usual, to setup the CAM. The cam0 (or sec0) node is used to
>>>>> read/write
>>>>> transport stream. To me it  looks like an extension of the current
>>>>> API.
>>>>>         
>>>> I see. This raises another problem. How to find out, which ca device
>>>> cam0 relates to, in case there are more ca devices than cam devices?
>>>>
>>>>       
>>> Are you sure there can be more ca devices than cam devices ?
>>>     
>>
>> Yes. See my previous response to Ralph.
>>   
> 
> Isn't this the same as asking which 'dvr' device relates to which
> 'frontend' device?

No, because this is defined. If demuxN is configured to output to a dvr
device, then it outputs to dvrN. The input of demuxN is configured by
using DMX_SET_SOURCE, which can be frontendX or dvrY.

Regards,
Andreas
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux