e9hack wrote: > 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. Any news about this? Imho Trent's patch to add I2C_M_STOP makes sense. According to the stv0299 datasheet, the stv0299 requires this STOP condition, too. This chip seems to be more tolerant though. The current driver does not send STOP before READ, and it works. CU Oliver -- -------------------------------------------------------- VDR Remote Plugin 0.3.9 available at http://www.escape-edv.de/endriss/vdr/ -------------------------------------------------------- _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
