1 .. -*- coding: utf-8; mode: rst -*-
9 For historical reasons, frontend types are named by the type of
10 modulation used in transmission. The fontend types are given by
11 fe_type_t type, defined as:
16 .. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.7cm}|
18 .. flat-table:: Frontend types
30 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` equivalent
49 - For DVB-C annex A standard
51 - ``SYS_DVBC_ANNEX_A``
69 - For ATSC standard (terrestrial) or for DVB-C Annex B (cable) used
72 - ``SYS_ATSC`` (terrestrial) or ``SYS_DVBC_ANNEX_B`` (cable)
75 Newer formats like DVB-S2, ISDB-T, ISDB-S and DVB-T2 are not described
76 at the above, as they're supported via the new
77 :ref:`FE_GET_PROPERTY/FE_GET_SET_PROPERTY <FE_GET_PROPERTY>`
78 ioctl's, using the :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
81 In the old days, struct :c:type:`dvb_frontend_info`
82 used to contain ``fe_type_t`` field to indicate the delivery systems,
83 filled with either FE_QPSK, FE_QAM, FE_OFDM or FE_ATSC. While this
84 is still filled to keep backward compatibility, the usage of this field
85 is deprecated, as it can report just one delivery system, but some
86 devices support multiple delivery systems. Please use
87 :ref:`DTV_ENUM_DELSYS <DTV-ENUM-DELSYS>` instead.
89 On devices that support multiple delivery systems, struct
90 :c:type:`dvb_frontend_info`::``fe_type_t`` is
91 filled with the currently standard, as selected by the last call to
92 :ref:`FE_SET_PROPERTY <FE_GET_PROPERTY>` using the
93 :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` property.