Commit 0969ec18 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab

[media] DocBook/frontend.xml: Correlate dvb delivery systems

As the DVB API provides two ways to specify the delivery
systems, correlate both ways into a table.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
parent 95e61e01
...@@ -23,40 +23,45 @@ cards, in which case there exists no frontend device.</para> ...@@ -23,40 +23,45 @@ cards, in which case there exists no frontend device.</para>
<section id="fe-type-t"> <section id="fe-type-t">
<title>Frontend type</title> <title>Frontend type</title>
<para>For historical reasons frontend types are named after the type of modulation used in <para>For historical reasons, frontend types are named by the type of modulation used in
transmission. The fontend types are given by fe_type_t type, defined as:</para> transmission. The fontend types are given by fe_type_t type, defined as:</para>
<table pgwide="1" frame="none" id="fe-type"> <table pgwide="1" frame="none" id="fe-type">
<title>Frontend types</title> <title>Frontend types</title>
<tgroup cols="2"> <tgroup cols="3">
&cs-def; &cs-def;
<thead> <thead>
<row> <row>
<entry>fe_type</entry> <entry>fe_type</entry>
<entry>Description</entry> <entry>Description</entry>
<entry><link linkend="DTV-DELIVERY-SYSTEM">DTV_DELIVERY_SYSTEM</link> equivalent type</entry>
</row> </row>
</thead> </thead>
<tbody valign="top"> <tbody valign="top">
<row> <row>
<entry id="FE_QPSK"><constant>FE_QPSK</constant></entry> <entry id="FE_QPSK"><constant>FE_QPSK</constant></entry>
<entry>For DVB-S standard</entry> <entry>For DVB-S standard</entry>
<entry><constant>SYS_DVBS</constant></entry>
</row> </row>
<row> <row>
<entry id="FE_QAM"><constant>FE_QAM</constant></entry> <entry id="FE_QAM"><constant>FE_QAM</constant></entry>
<entry>For DVB-C standard</entry> <entry>For DVB-C annex A/C standard</entry>
<entry><constant>SYS_DVBC_ANNEX_AC</constant></entry>
</row> </row>
<row> <row>
<entry id="FE_OFDM"><constant>FE_OFDM</constant></entry> <entry id="FE_OFDM"><constant>FE_OFDM</constant></entry>
<entry>For DVB-T standard. Also used for ISDB-T on compatibility mode</entry> <entry>For DVB-T standard</entry>
<entry><constant>SYS_DVBT</constant></entry>
</row> </row>
<row> <row>
<entry id="FE_ATSC"><constant>FE_ATSC</constant></entry> <entry id="FE_ATSC"><constant>FE_ATSC</constant></entry>
<entry>For ATSC standard (terrestrial or cable)</entry> <entry>For ATSC standard (terrestrial) or for DVB-C Annex B (cable) used in US.</entry>
<entry><constant>SYS_ATSC</constant> (terrestrial) or <constant>SYS_DVBC_ANNEX_B</constant> (cable)</entry>
</row> </row>
</tbody></tgroup></table> </tbody></tgroup></table>
<para>Newer formats like DVB-S2, ISDB-T, ISDB-S and DVB-T2 are not described at the above, as they're <para>Newer formats like DVB-S2, ISDB-T, ISDB-S and DVB-T2 are not described at the above, as they're
supported via the new <link linkend="FE_GET_SET_PROPERTY">FE_GET_PROPERTY/FE_GET_SET_PROPERTY</link> method. supported via the new <link linkend="FE_GET_SET_PROPERTY">FE_GET_PROPERTY/FE_GET_SET_PROPERTY</link> ioctl's, using the <link linkend="DTV-DELIVERY-SYSTEM">DTV_DELIVERY_SYSTEM</link> parameter.
</para> </para>
</section> </section>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment