From: Manu Abraham Date: Wed, 16 Nov 2011 13:34:24 +0000 (-0300) Subject: [media] DVB: Docbook update for DTV_ENUM_DELSYS X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=6c7ef54774a28aec6268ca325abf95c7d6956ee3;p=mv-sheeva.git [media] DVB: Docbook update for DTV_ENUM_DELSYS Signed-off-by: Manu Abraham Signed-off-by: Mauro Carvalho Chehab --- diff --git a/Documentation/DocBook/media/dvb/dvbproperty.xml b/Documentation/DocBook/media/dvb/dvbproperty.xml index 6ac803959a4..b812e3140fc 100644 --- a/Documentation/DocBook/media/dvb/dvbproperty.xml +++ b/Documentation/DocBook/media/dvb/dvbproperty.xml @@ -649,6 +649,18 @@ typedef enum fe_hierarchy { many data types via a single multiplex. The API will soon support this at which point this section will be expanded. +
+ <constant>DTV_ENUM_DELSYS</constant> + A Multi standard frontend needs to advertise the delivery systems provided. + Applications need to enumerate the provided delivery systems, before using + any other operation with the frontend. Prior to it's introduction, + FE_GET_INFO was used to determine a frontend type. A frontend which + provides more than a single delivery system, FE_GET_INFO doesn't help much. + Applications which intends to use a multistandard frontend must enumerate + the delivery systems associated with it, rather than trying to use + FE_GET_INFO. In the case of a legacy frontend, the result is just the same + as with FE_GET_INFO, but in a more structured format +
Properties used on terrestrial delivery systems