2007/5/24, e9hack <[EMAIL PROTECTED]>:
Manu Abraham wrote: > e9hack wrote: >> Manu Abraham wrote: >>> Trent Piepho wrote: >>>> What the stv0297 wants is: >>>> S Addr Wr [A] Comm [A] P S Addr Rd [A] [Data] NA P >>>> >>> The STV0297 is just a normal demod like the others, nothing special >>> about it (according to ST). Well of course i2cdump can be wrong. >> The stv0297 cannot handle a repeated start condition and it needs a little delay between the stop and the next start >> condition. A stop and a start condition cannot be on the same upload command of a saa7146 (on a TT 2300C). > > Any idea what the SAA7146 - STV0297 windows driver does ? > Good point. I can monitor any access to the saa7146 registers of the TT 2300C on Windows. I will check this issue. In the past, I was more interested in the high level part of the i2c-communication.
The windows driver for the TT 2300C does never use a repeated start condition for the stv0297. The stop and next start condition are always on different upload commands of the saa7146. It is a gap of 200us between the upload commands. The gap length may be an result of my runtime-patch-driver. It does insert some code on every access to the saa7146 registers. For the i2c-registers, it is also a DbgPrint call. For the other i2c-devices (MSP34x5, SAA7114, eeprom), the driver uses repeated start conditions. The driver uses no stop and next start condition for any device in one upload command. - Hartmut
_______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
