Em Thu, 28 Mar 2013 10:52:01 +0200 Timo Teras <timo.teras@xxxxxx> escreveu: > On Wed, 27 Mar 2013 16:10:49 +0200 > Timo Teras <timo.teras@xxxxxx> wrote: > > > On Tue, 26 Mar 2013 10:20:56 +0200 > > Timo Teras <timo.teras@xxxxxx> wrote: > > > > > I did manage to get decent traces with USBlyzer evaluation version. > > > > Nothing _that_ exciting there. Though, there's quite a bit of > > differences on certain register writes. I tried copying the changed > > parts, but did not really help. > > > > Turning on saa7115 debug gave: > > > > saa7115 1-0025: chip found @ 0x4a (ID 000000000000000) does not match > > a known saa711x chip. > > Well, I just made saa7115.c ignore this ID check, and defeault to > saa7113 which is apparently the chip used. > > And now it looks like things start to work a lot better. > > Weird that the saa7113 chip is missing the ID string. Will continue > testing. That could happen if saa7113 is behind some I2C bridge and when saa7113 is not found when the detection code is called. > > - Timo -- Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
