Devin, Thanks for the info.. Should the parse_em28xx.pl script be updated to reflect this? I'm assuming other em28xx boards also have the eeprom at address 0xa0. There are a couple more entries that I am unsure about.. I'll post those when I get home tonight. Are you interested in looking at some traces? I am pretty sure I have most of the analog and input stuff figured out though I probably don't have the GPIO sequence correct. Anyways, if your interested I can send you what I know. Thanks Franklin Meng --- On Wed, 10/21/09, Devin Heitmueller <dheitmueller@xxxxxxxxxxxxxx> wrote: > From: Devin Heitmueller <dheitmueller@xxxxxxxxxxxxxx> > Subject: Re: Kworld 315U help? > To: "Franklin Meng" <fmeng2002@xxxxxxxxx> > Cc: linux-media@xxxxxxxxxxxxxxx > Date: Wednesday, October 21, 2009, 5:55 AM > On Wed, Oct 21, 2009 at 1:35 AM, > Franklin Meng <fmeng2002@xxxxxxxxx> > wrote: > > I was wondering if someone would be able to help me > with getting the analog and inputs for the Kworld 315U > working. I was able to get the digital part working with > help from Douglas Schilling and wanted to get the remaining > portions of the device working. > > > > I have traces but have not made much progress. In > addition I also have some questions about the information > that the parse_em28xx.pl skips and does not decode. > > > > For example here is some of the data that doesn't seem > to be decoded.. > > unknown: 40 03 00 00 a0 00 01 00 >>> 08 > > unknown: c0 02 00 00 a0 00 01 00 <<< d0 > > unknown: 40 03 00 00 a0 00 01 00 >>> 08 > > unknown: c0 02 00 00 a0 00 01 00 <<< d0 > > unknown: 40 03 00 00 a0 00 01 00 >>> 22 > > unknown: c0 02 00 00 a0 00 01 00 <<< 01 > > unknown: 40 03 00 00 a0 00 01 00 >>> 04 > > unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb > > unknown: 40 03 00 00 a0 00 01 00 >>> 20 > > unknown: c0 02 00 00 a0 00 01 00 <<< 46 > > unknown: 40 03 00 00 a0 00 01 00 >>> 14 > > unknown: c0 02 00 00 a0 00 04 00 <<< 4e 07 01 > 00 > > > > Anyways, any help that can be provided is > appreciated. > > Those look like i2c commands to the onboard eeprom, which > is at i2c > address 0xa0. For example: > > unknown: 40 03 00 00 a0 00 01 00 >>> 04 > // set eeprom read offset to 0x04 > unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb > // read two bytes back from eeprom > > Cheers, > > 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 > -- 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
