On Tue, Mar 11, 2008 at 5:05 PM, Jarryd Beck <jarro.2783@xxxxxxxxx> wrote: > > Can you take logs with vendor WHQL driver and sent for further analysis? > > http://www.afatech.com/EN/support.aspx > > > > Antti > > > > -- > > http://palosaari.fi > > > > For some reason windows didn't like that driver. When I used the installer > nothing happened, and when I used device manager it said this folder > contains no information about your device. > So I made a snoop with the driver on the CD, I hope it's good enough. > > I uploaded the snoop to > http://download.yousendit.com/2B0B420876BFB959 > > While it was snooping, I plugged it in, tuned the card to a tv channel > and pulled it out as quick as I could. > If it helps, the channel was channel 7, sydney, australia. This helps..... I can tell that your tda18211 is located at 0xC0, and it contains 0x83 in its ID register. This is the same ID byte that the tda18271c1 uses to identify itself -- hopefully that implies driver compatability, but we won't know for sure until you try it. The windows driver is only using the primary sixteen registers -- I don't know if the device even HAS the 23 extended registers that the tda18271 has... The driver that you're running does not seem to touch the extended registers at all. It's possible that the driver is simply blasting the register bytes to the tuner, without doing any calibration explicitly -- that could explain the 16 byte blasts without any transactions to the extended registers.... not sure -- this is all speculation. One thing I can say -- the Linux tda18271 driver should be able to detect your tuner at 0xC0 (0x60) as a tda18271c1 -- It's worth a try, and could certainly be possible that the driver *may* work as-is, although I suspect that some tweaking will be needed. Regards, Mike _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
