Next question: ;-)
looking on: * frontend.h (cvs 1.18)
[...]
typedef enum fe_type {
FE_QPSK,
FE_QAM,
FE_OFDM,
FE_ATSC
} fe_type_t;
[...]
I do not understand FE_ATSC here,
because QPSK, QAM QFDM are modulations.
Why is FE_ATSC here?
ATSC supports several modulations...
Shouldn't there be the modulation named (e.g. VSB)?
Next:
Currently this is an enum field, but what happens
if you are having a frontend supporting more than one modulation?
(e.g. DVB-CT --> FE_QAM|FE_OFDM )
cu Rainer
typedef en
Rainer.scherg schrieb:
> Hi,
>
> I need some help to understand the ATSC extension of the dvb api.
> looking into the source I have some questions for understanding
> (doc doesn't seems to be up to date):
>
>
> 1.) It seems dvb api 3 has been upgraded for ATSC support: FE_ATSC
> Could we have an ioctl/function call to retrieve current api version
> or subversion during runtime (checking device pathes is not
> sufficient). And checking for FE_ATSC: this might only to be set, if
> there is a proper card/hardware plugged in...
