On Thu, Oct 22, 2009 at 12:03 AM, Franklin Meng <fmeng2002@xxxxxxxxx> wrote: > Here are some more stuff in the trace that was not decoded by the parse_em28xx script.. > > So what we know from this list of unknowns... > > 0xa0 is the eeprom > 0x4a is the SAA > 0x42 ??. > 0xd0 ?? > 0x20 ?? > 0xc6 ?? > 0xc4 ?? > 0xc2 Thomson tuner. c4 and c6 are probably also the tuner. I know that K-World makes some products with the same name but different regions. Is your version of the 315U an ATSC hybrid tuner? If so, then one of those addresses is probably the demod. Also, the trace you sent is just an excerpt, but it's possible that the driver is probing for devices and the requests are failing because the hardware isn't present (the Windows driver supports a variety of different hardware combinations). Usually you can tell by looking for a read from register 0x05 immediately after the i2c read. If register 0x05 is nonzero, then the i2c read operation failed. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
