Johannes Stezenbach wrote:
On Mon, May 15, 2006, Trent Piepho wrote:
On Mon, 15 May 2006, Manu Abraham wrote:
I thought ATSC tuners supported 256QAM additionally for digital cable,
alongwith VSB8/16 for OTA.
nxt200.c:
.caps = FE_CAN_8VSB | FE_CAN_QAM_64 | FE_CAN_QAM_256
or51211.c:
.caps = FE_CAN_8VSB
or11132.c:
.caps = FE_CAN_QAM_64 | FE_CAN_QAM_256 | FE_CAN_QAM_AUTO | FE_CAN_8VSB
bcm3510.c:
.caps = FE_CAN_8VSB | FE_CAN_16VSB | FE_CAN_QAM_16 | FE_CAN_QAM_64 | FE_CAN_QAM_128 | FE_CAN_QAM_256
lgdt330x.c:
.caps = FE_CAN_QAM_64 | FE_CAN_QAM_256 | FE_CAN_8VSB
As you can see, it is not always the same. What will happen when new
front-ends come out that have new abilities?
It seems the fundamental difference between ATSC and DVB is that
there are clearly defined DVB standards for DVB-S, DVB-C, DVB-T,
DVB-H and DVBS2, but ATSC people don't make the distinction
between ATSC-C (FE_CAN_QAM_64, FE_CAN_QAM_256) and
ATSC-T (FE_CAN_8VSB). What a mess!
Should we really care about it that way ? Just OR all the bitfields for
ATSC. We can say in the ATSC struct that it is composed of all the mess.
(DVB-S + DVB-C + DVB-T = ATSC)
I came across some place that ATSC over satellite was finally considered
nonsense by the people who went after it, with the advent of DVB-S2. In
the satellite spec 8PSK was also described.
Manu
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
