From: matthieu castet <castet.matthieu@free.fr>
To: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: tm6010 : strange i2c
Date: Thu, 29 Jan 2009 23:51:26 +0100 [thread overview]
Message-ID: <498232EE.8060209@free.fr> (raw)
Hi,
I am trying to make work my hauppauge HVR900H, and I start looking at
http://linuxtv.org/hg/~mchehab/tm6010/ drivers and windows usb trace.
After some experiment I found that the i2c is very strange :
* for the zl10353 demodulator, the register read only seems to work if
the register address is odd and we read at least 2 bytes[1]. And the
windows driver seems to really do that according usb trace (read always
2 bytes at odd address).
* the windows driver read the eeprom in the strange way : it use
REQ_14_SET_GET_I2C_WR2_RDN, but setting the offset in the high byte of
wIndex. And it does 16 bytes read, 1 bytes read for reading again the
last 16th byte, and continue 16 bytes read, 1 byte read.
Did the people that worked on the tm6000 driver saw that weird i2c ?
Matthieu
[1]
Doing REQ_16_SET_GET_I2C_WR1_RDN on the demodulator with different
register address and read size.
0051: 00
------
0051: 00
------
0052: 00
------
0050: 00
------
004f: 00
------
0050: 00
------
0051: 44 46
------
0051: 44 46
------
0052: 46 46
------
0050: 46 46
------
004f: 46 0c
------
0050: 0c 0c
------
0051: 44 46 15 0f
------
0051: 44 46 15 0f
------
0052: 0f 0f 00 00
------
0050: 00 00 00 00
------
004f: 00 0c 44 46
------
0050: 46 46 00 00
------
0051: 44 46 15 0f 00 00 00 00
------
0051: 44 46 15 0f 00 00 00 00
------
0052: 00 00 00 00 00 00 00 00
------
0050: 00 00 00 00 00 00 00 00
------
004f: 00 0c 44 46 15 0f 00 00
------
0050: 00 00 00 00 00 00 00 00
------
0051: 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d 0d 00
------
0051: 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d 0d 00
------
0052: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
004f: 00 0c 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d
------
0050: 0d 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
0051: 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d 0d 00
0061: 4d 0a 0f 0f 0f 0f c2 00 00 80 00 00 00 00 00 00
------
0051: 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d 0d 00
0061: 4d 0a 0f 0f 0f 0f c2 00 00 80 00 00 00 00 00 00
------
0052: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0062: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
004f: 00 0c 44 46 15 0f 00 00 00 00 00 48 00 75 0d 0d
005f: 0d 00 4d 0a 0f 0f 0f 0f c2 00 00 80 00 00 00 00
------
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------
reply other threads:[~2009-01-29 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498232EE.8060209@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox