[linux-dvb] Re: Alternative v4 demux API

[Holger Waechtler <holger@convergence.de>]

Ralph Metzler wrote:
> Holger Waechtler writes:
>  
>  > If we want to remove even more ambinguities we should distinguish in the 
>  > demux API between general purpose filter banks and decoder-attached 
>  > filter banks.
>  > 
>  > Maybe this would even simplify using the API since the routing might get 
>  > more straightforward.
>
> True. Again this is the question wether to tell the application about all
> capabilities (wether it be through "CAP-ioctls" or the mere existence
> of devices) or to let the driver deal with it.
I'd prefer a capability ioctl which tells the userspace app about the 
actual available filter banks. Too much intelligence in the driver is 
almost always considered a bad thing.

> In the latter case suddenly telling the driver to "decrypt a PID" can
> cause major headaches depending on the state of filter allocation ... 
right.

> And there are even more kinds of filter modes which cannot
> always be done by all filter banks. And there can be restrictions on
> which section filters can be used with which PID filters from which
> banks, etc. 
We should think about a clever way to describe such interdependencies in 
the capability ioctl. Maybe multiple alternative capability sets for 
different scenarios? Then the application could choose from...

Holger



--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.