|
|
@@ -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.</para>
|
|
|
</section>
|
|
|
+ <section id="DTV_ENUM_DELSYS">
|
|
|
+ <title><constant>DTV_ENUM_DELSYS</constant></title>
|
|
|
+ <para>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 </para>
|
|
|
+ </section>
|
|
|
</section>
|
|
|
<section id="frontend-property-terrestrial-systems">
|
|
|
<title>Properties used on terrestrial delivery systems</title>
|
Manu Abraham