From 16ff950683d9ba42b6daf820619302cce634f012 Mon Sep 17 00:00:00 2001 From: Manu Abraham Date: Wed, 16 Nov 2011 10:34:24 -0300 Subject: [PATCH] --- yaml --- r: 285381 b: refs/heads/master c: 6c7ef54774a28aec6268ca325abf95c7d6956ee3 h: refs/heads/master i: 285379: f50560940bca7e33f584e58ad1feaba0a4874e79 v: v3 --- [refs] | 2 +- .../Documentation/DocBook/media/dvb/dvbproperty.xml | 12 ++++++++++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 6e0f7c6da9d6..10bb65a41d05 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ba2780c796badfc3741c7cb499a575ca49f17e6d +refs/heads/master: 6c7ef54774a28aec6268ca325abf95c7d6956ee3 diff --git a/trunk/Documentation/DocBook/media/dvb/dvbproperty.xml b/trunk/Documentation/DocBook/media/dvb/dvbproperty.xml index 6ac803959a47..b812e3140fcb 100644 --- a/trunk/Documentation/DocBook/media/dvb/dvbproperty.xml +++ b/trunk/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