diff options
author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-06-07 19:43:25 -0400 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-07-27 16:52:45 -0400 |
commit | df2692a6dd89fc00929a18735b83204b352ebb52 (patch) | |
tree | 61895d345c72e08e7ac879eaf05c904864b5aa23 /Documentation | |
parent | 17d8bb061fcf8ba6a56adcf193d7d255966cff79 (diff) |
[media] DocBook/frontend.xml: Recomend the usage of the new API
The old way of setting delivery system parameters were to use
an union with specific per-system parameters. However, as newer
delivery systems required more data, the structure size weren't
enough to fit. So, recomend using the DVBS2API instead.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/DocBook/media/dvb/frontend.xml | 16 |
1 files changed, 14 insertions, 2 deletions
diff --git a/Documentation/DocBook/media/dvb/frontend.xml b/Documentation/DocBook/media/dvb/frontend.xml index b1f01239d4da..086e62bcad11 100644 --- a/Documentation/DocBook/media/dvb/frontend.xml +++ b/Documentation/DocBook/media/dvb/frontend.xml | |||
@@ -221,8 +221,20 @@ by</para> | |||
221 | <section id="dvb-frontend-parameters"> | 221 | <section id="dvb-frontend-parameters"> |
222 | <title>frontend parameters</title> | 222 | <title>frontend parameters</title> |
223 | <para>The kind of parameters passed to the frontend device for tuning depend on | 223 | <para>The kind of parameters passed to the frontend device for tuning depend on |
224 | the kind of hardware you are using. All kinds of parameters are combined as an | 224 | the kind of hardware you are using.</para> |
225 | union in the FrontendParameters structure:</para> | 225 | <para>The struct <constant>dvb_frontend_parameters</constant> uses an |
226 | union with specific per-system parameters. However, as newer delivery systems | ||
227 | required more data, the structure size weren't enough to fit, and just | ||
228 | extending its size would break the existing applications. So, those parameters | ||
229 | were replaced by the usage of <link linkend="FE_GET_SET_PROPERTY"> | ||
230 | <constant>FE_GET_PROPERTY/FE_SET_PROPERTY</constant></link> ioctl's. The | ||
231 | new API is flexible enough to add new parameters to existing delivery systems, | ||
232 | and to add newer delivery systems.</para> | ||
233 | <para>So, newer applications should use <link linkend="FE_GET_SET_PROPERTY"> | ||
234 | <constant>FE_GET_PROPERTY/FE_SET_PROPERTY</constant></link> instead, in | ||
235 | order to be able to support the newer System Delivery like DVB-S2, DVB-T2, | ||
236 | DVB-C2, ISDB, etc.</para> | ||
237 | <para>All kinds of parameters are combined as an union in the FrontendParameters structure:</para> | ||
226 | <programlisting> | 238 | <programlisting> |
227 | struct dvb_frontend_parameters { | 239 | struct dvb_frontend_parameters { |
228 | uint32_t frequency; /⋆ (absolute) frequency in Hz for QAM/OFDM ⋆/ | 240 | uint32_t frequency; /⋆ (absolute) frequency in Hz for QAM/OFDM ⋆/ |