diff options
author | Manu Abraham <abraham.manu@gmail.com> | 2011-11-16 08:34:24 -0500 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-12-12 12:03:49 -0500 |
commit | 6c7ef54774a28aec6268ca325abf95c7d6956ee3 (patch) | |
tree | edfc8bb02fdb96d5166cb3ce2b422d9093488eb6 /Documentation/DocBook | |
parent | ba2780c796badfc3741c7cb499a575ca49f17e6d (diff) |
[media] DVB: Docbook update for DTV_ENUM_DELSYS
Signed-off-by: Manu Abraham <abraham.manu@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/DocBook')
-rw-r--r-- | Documentation/DocBook/media/dvb/dvbproperty.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/DocBook/media/dvb/dvbproperty.xml b/Documentation/DocBook/media/dvb/dvbproperty.xml index 6ac803959a47..b812e3140fcb 100644 --- a/Documentation/DocBook/media/dvb/dvbproperty.xml +++ b/Documentation/DocBook/media/dvb/dvbproperty.xml | |||
@@ -649,6 +649,18 @@ typedef enum fe_hierarchy { | |||
649 | many data types via a single multiplex. The API will soon support this | 649 | many data types via a single multiplex. The API will soon support this |
650 | at which point this section will be expanded.</para> | 650 | at which point this section will be expanded.</para> |
651 | </section> | 651 | </section> |
652 | <section id="DTV_ENUM_DELSYS"> | ||
653 | <title><constant>DTV_ENUM_DELSYS</constant></title> | ||
654 | <para>A Multi standard frontend needs to advertise the delivery systems provided. | ||
655 | Applications need to enumerate the provided delivery systems, before using | ||
656 | any other operation with the frontend. Prior to it's introduction, | ||
657 | FE_GET_INFO was used to determine a frontend type. A frontend which | ||
658 | provides more than a single delivery system, FE_GET_INFO doesn't help much. | ||
659 | Applications which intends to use a multistandard frontend must enumerate | ||
660 | the delivery systems associated with it, rather than trying to use | ||
661 | FE_GET_INFO. In the case of a legacy frontend, the result is just the same | ||
662 | as with FE_GET_INFO, but in a more structured format </para> | ||
663 | </section> | ||
652 | </section> | 664 | </section> |
653 | <section id="frontend-property-terrestrial-systems"> | 665 | <section id="frontend-property-terrestrial-systems"> |
654 | <title>Properties used on terrestrial delivery systems</title> | 666 | <title>Properties used on terrestrial delivery systems</title> |