Em Mon, 4 Sep 2017 11:40:59 +0200
Honza Petrouš escreveu:
> > So, IMHO, the interface is broken by design. Perhaps that's
> > the reason why no upstream driver uses it.
>
> I have the same feeling regarding brokenness.
>
> >
> > What seems to be a much better design would be to use the demux
2017-09-04 11:06 GMT+02:00 Mauro Carvalho Chehab :
> Em Mon, 4 Sep 2017 09:12:49 +0200
> Honza Petrouš escreveu:
>
>> 2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
>> > Em Sun, 3 Sep 2017 22:05:23 +0200
>> > Honza Petrouš escreveu:
>> >
>> >> 1) #define CA_SET_DESCR _IOW('o', 134, ca_des
Em Mon, 4 Sep 2017 09:12:49 +0200
Honza Petrouš escreveu:
> 2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
> > Em Sun, 3 Sep 2017 22:05:23 +0200
> > Honza Petrouš escreveu:
> >
> >> 1) #define CA_SET_DESCR _IOW('o', 134, ca_descr_t)
> >>
> >
2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
> Em Sun, 3 Sep 2017 22:05:23 +0200
> Honza Petrouš escreveu:
>
>> 1) #define CA_SET_DESCR _IOW('o', 134, ca_descr_t)
>>
>>
>> CA_SET_DESCR is used for feeding descrambler device
>> with correct key
Em Sun, 3 Sep 2017 22:05:23 +0200
Honza Petrouš escreveu:
> > There is still a gap at the CA API, as there are three ioctls that are used
> > only by a few drivers and whose structs are not properly documented:
> > CA_GET_MSG, CA_SEND_MSG and CA_SET_DESCR.
> >
> > The first two ones seem to be re
Em Sun, 3 Sep 2017 22:05:23 +0200
Honza Petrouš escreveu:
> 1) #define CA_SET_DESCR _IOW('o', 134, ca_descr_t)
>
>
> CA_SET_DESCR is used for feeding descrambler device
> with correct keys (called here "control words") what
> allows to get servic
> There is still a gap at the CA API, as there are three ioctls that are used
> only by a few drivers and whose structs are not properly documented:
> CA_GET_MSG, CA_SEND_MSG and CA_SET_DESCR.
>
> The first two ones seem to be related to a way that a few drivers
> provide to send/receive messages.
> There is still a gap at the CA API, as there are three ioctls that are used
> only by a few drivers and whose structs are not properly documented:
> CA_GET_MSG, CA_SEND_MSG and CA_SET_DESCR.
>
> The first two ones seem to be related to a way that a few drivers
> provide to send/receive messages.
The DVB documentation was negligected for a long time, with
resulted on several gaps between the API description and its
documentation.
I'm doing a new reading at the documentation. As result of it,
this series:
- improves the introductory chapter, making it more generic;
- Do some adjustments at
