atsc and api v5
While trying to update an application to API v5 some question arised.
Which type of "delivery_system" should be set for ATSC? <frontend.h> says...
SYS_DVBC_ANNEX_AC, <- european DVB-CSYS_DVBC_ANNEX_B, <- american ATSC QAM
..SYS_ATSC, <- oops, here we have ATSC again, cable and terrestrial not named? Is this VSB *only*?
Which one should i choose, "SYS_ATSC" for both (VSB and QAM), or should i choose SYS_DVBC_ANNEX_B for ATSC cable and SYS_ATSC for VSB?
thanks,
Winfried
Quoted 13 lines · wk
While trying to update an application to API v5 some question arised.
Which type of "
delivery_system" should be set for ATSC? <frontend.h> says...
SYS_DVBC_ANNEX_AC, <- european DVB-CSYS_DVBC_ANNEX_B, <- american ATSC QAM
..SYS_ATSC, <- oops, here we have ATSC again, cable and terrestrial not named? Is this VSB *only*?
Quoted 5 lines
Which one should i choose, "
SYS_ATSC" for both (VSB and QAM), or should i chooseSYS_DVBC_ANNEX_Bfor ATSC cable andSYS_ATSCfor VSB?thanks,
Winfried
I'm pretty sure it's SYS_ATSC for both VSB and QAM.
Devin
Signature · 3 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
Quoted 18 lines · Devin Heitmueller
Quoted 16 lines · wk
While trying to update an application to API v5 some question arised.
Which type of "
delivery_system" should be set for ATSC? <frontend.h> says...
SYS_DVBC_ANNEX_AC, <- european DVB-CSYS_DVBC_ANNEX_B, <- american ATSC QAM
..SYS_ATSC, <- oops, here we have ATSC again, cable and terrestrial not
named? Is this VSB *only*?Which one should i choose, "
SYS_ATSC" for both (VSB and QAM), or should i chooseSYS_DVBC_ANNEX_Bfor ATSC cable andSYS_ATSCfor VSB?
Quoted 10 lines
Quoted 3 lines
thanks,
WinfriedI'm pretty sure it's
SYS_ATSCfor both VSB and QAM.Devin
Meanwhile i think this is the answer..
dvb-core/dvb_frontend.c line 1076
/* Synchronise the legacy tuning parameters into the cache, so that demodulator
* drivers can use a single set_frontend tuning function, regardless of whether
* it's being used for the legacy or new API, reducing code and complexity. */
static void dtv_property_cache_sync(struct dvb_frontend *fe,
struct dvb_frontend_parameters *p)
{
.....
switch (fe->ops.info.type) {
......
case FE_ATSC:
c->modulation = p->u.vsb.modulation;
if ((c->modulation == VSB_8) || (c->modulation == VSB_16))
c->delivery_system = SYS_ATSC;
else
c->delivery_system = SYS_DVBC_ANNEX_B; <- QAM_64
and QAM_256 here
break;That means the naming is completely misleading here.
I have to choose SYS_DVBC_ANNEX_B for ATSC QAM, but ATSC VSB needs SYS_ATSC.
Winfried
Quoted 17 lines · Devin Heitmueller
Quoted 16 lines · wk
While trying to update an application to API v5 some question arised.
Which type of "
delivery_system" should be set for ATSC? <frontend.h> says...
SYS_DVBC_ANNEX_AC, <- european DVB-CSYS_DVBC_ANNEX_B, <- american ATSC QAM
..SYS_ATSC, <- oops, here we have ATSC again, cable and terrestrial not
named? Is this VSB *only*?Which one should i choose, "
SYS_ATSC" for both (VSB and QAM), or should i chooseSYS_DVBC_ANNEX_Bfor ATSC cable andSYS_ATSCfor VSB?
Quoted 6 lines
Quoted 2 lines
thanks,
WinfriedI'm pretty sure it's
SYS_ATSCfor both VSB and QAM.Devin
Hmmm...
The compatability code between the API v5 property cache and the API v3 frontend parameters use...
a. This code for translating v3 parameters into the v5 cache:
static void dtv_property_cache_sync(struct dvb_frontend *fe,
struct dvb_frontend_parameters *p)
{
struct dtv_frontend_properties *c = &fe->dtv_property_cache;
c->frequency = p->frequency;
c->inversion = p->inversion;
switch (fe->ops.info.type) {
...
case FE_ATSC:
c->modulation = p->u.vsb.modulation;
if ((c->modulation == VSB_8) || (c->modulation == VSB_16))
c->delivery_system = SYS_ATSC;
else
c->delivery_system = SYS_DVBC_ANNEX_B;
break;
}
}b. This code for translating v5 cache into the v3 parameters:
static void dtv_property_legacy_params_sync(struct dvb_frontend *fe)
{
struct dtv_frontend_properties *c = &fe->dtv_property_cache;
struct dvb_frontend_private *fepriv = fe->frontend_priv;
struct dvb_frontend_parameters *p = &fepriv->parameters;
p->frequency = c->frequency;
p->inversion = c->inversion;
switch (fe->ops.info.type) {
...
case FE_ATSC:
dprintk("%s() Preparing VSB req\n", __func__);
p->u.vsb.modulation = c->modulation;
if ((c->modulation == VSB_8) || (c->modulation == VSB_16))
c->delivery_system = SYS_ATSC;
else
c->delivery_system = SYS_DVBC_ANNEX_B;
break;
}
}So it would seem the code to fill out v3 parameter structures uses SYS_DVBC_ANNEX_B as the "delivery system" for ATSC FE's that aren't using VSB modulation.
Not that SYS_ATSC nor SYS_DVBC_ANNEX_B are used/checked as a delivery system by any driver (yet.)
I've checked DVB-C (ETSI EN 300 429 v1.2.1) Annex B and it really doesn't mention or reference ATSC QAM explicitly, but it does have a table of QAM modulations useful in 8 MHz BWs down to a 2 MHz BW.
I've also looked at A/53 Part 2 which only talks about VSB modulations.
I couldn't find any free NCTA documents on QAM for American cable systems.
I did find that ITU-T J.83 Annex B describes the framing structure, channel coding, and modulation schemes for digital cable service in North America. And that J.83 Annex A and J.83 Annex C defines the cable modulation schemes for Japanese and European regions, respectively. I'm trying to dig up a free copy if I can.
I suspect SYS_DVBC_ANNEX_B and SYS_DVB_ANNEX_AC in the Linux enumeration don't refer to the DVB C standard Annexes, but refer to ITU-T J.83 Annexes.
So I'm assumming SYS_DVBC_ANNEX_B *is* the Linux delivery system enumaeration value you want for North American Cable QAM modulations with FE_ATSC.
Anyone got the ITU-T J.83 document to confirm or refute?
BTW, I plan on starting to documenting the API v5 changes in the Linux DVB spec within the next week or so.
Regards,
Andy