On 01.04.2012 15:19, Michael Büsch wrote:
Great work. I'll rebase my tree on the new branch and check those firmware files asap.
Hm, none of these firmwares fix the problem. Maybe it's not a firmware
problem after all, but just incorrectly setup tuner-i2c.
Here's the dmesg log:
[...]
[ 132.018549] af9033: firmware version: LINK=11.10.10.0 OFDM=5.33.10.0
[ 132.018566] DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
[ 132.028370] i2c i2c-8: Fitipower FC0011 tuner attached
[ 132.028388] dvb-usb: Afatech Technologies DVB-T stick successfully initialized and connected.
[ 132.028405] af9035_init: USB speed=3 frame_size=0ff9 packet_size=80
[ 132.040019] usbcore: registered new interface driver dvb_usb_af9035
[ 145.407991] af9035_ctrl_msg: command=03 failed fw error=2
[ 145.408008] i2c i2c-8: I2C write reg failed, reg: 07, val: 0f
I also tried the other firmware. Same result.
It must then be I2C adapter or I2C client issue.
Adapter code is here, and it known to work with TUA9001. TUA9001 sends
1x byte register and then followed 2xbytes data.
u8 buf[4 + msg[0].len];
struct usb_req req = { CMD_I2C_WR, 0, sizeof(buf), buf, 0, NULL };
buf[0] = msg[0].len;
buf[1] = msg[0].addr << 1;
buf[2] = 0x01;
buf[3] = 0x00;
memcpy(&buf[4], msg[0].buf, msg[0].len);
ret = af9035_ctrl_msg(d->udev, &req);
Maybe you have given I2C address as a "8bit" format? Maybe adapter bytes
buf[2] and buf[3] are wrong? If you have taken sniffs from windows it is
very easy to see what is wrong.
regards
Antti
--
http://palosaari.fi/
--
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
