On Sat, 2007-05-19 at 23:45 +0200, e9hack wrote: > Thanks, I need only the dump with the running application and with the i2c-address 0xc (tda10021). I forgot, that exists > some more devices on the i2c-bus. The windows driver uses a small buffer (188kB), in odd/even buffer mode. The line > width is 188 Byte. The line count is a multiple of 512 like the current linux driver. The interesting thing is: the > register 0x12 of the tda10021 is set to 0xa1. Before my change, the linux driver has used 0xa1 without a CI/CAM and 0xa0 > with a CI/CAM. Some of the registers (0x20 and 0x2c), which are also responsible for the output configuration of the > tda10021, make no sense. The value 0x95 is to often and always on a multiple of 4 within the dump. Can you create such a > dump again? > > Currently, I've no idea why it works in single buffer mode and why not with odd/even buffers. > A few years back I proposed the original change to the budget driver to switch from 2 odd/even buffers to a single one because I was seeing some data corruption when using 2 buffers. At the time I found that the hardware had issues when switching between the 2 buffers and would often indicate the wrong one during the switchover. Maybe something like the patch the linked email is worth trying again? http://www.linuxtv.org/mailinglists/linux-dvb/2003/08-2003/msg00467.html The patch was discarded when I later found that just using a single buffer was a simpler solution. > - Hartmut > > > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
