On Mon, 15 May 2006, Manu Abraham wrote: > > Thank for your answers. I think the task I wanted to do, find out if a > > front-end supports ATSC and QAM-256, can not be done. It appears that the > > only way to do this, is to tell the front-end to use QAM-256, and then see if > > this fails. > > > > I didn't follow your question. Do you follow it now, or are you saying that you still do not follow it? > > Is this correct? The only way for an application to check if a front-end > > supports a certain modulation or FEC rate or other parameter is to call > > DVBFE_SET_PARAMS to change the frontend settings and then see if the ioctl > > failed. Finding out if an ATSC tuner supports both 8-VSB and 256-QAM will > > require re-loading the firmware and programming the demod over I2C, to change > > modes with DVBFE_SET_PARAMS and then see if this fails. > > You mean to have modulation as a static bitfield in dvbfe_info ? I'm not making any suggestions about what to change. I am just asking, how will I accomplish a task with this new API? I wrote code do this with the old API, how will I port it? How will other developers port their code? > 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? _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
