I would like to contact someone developing also the driver to share
information, and to give a kick to the driver forward. I am heavily
torturing the device...
I have submitted a patch to the linux-dvd distribution list I think solving
the "NULL pointer dereference"
I am getting initial answers from the device. I am able to attach the mt352
(demod).
It seems that the first byte to send on the USB for reading is "0x02".
For example with these sequence:
0x10 0x00
0x15 0x00
0x16 0x01
0x02 0x3e 0x01 0x01 0x7f
I can read the mt352 CHIP_ID and register the mt352.
The:
0x10 0x00
0x15 0x00
0x16 0x01
Seems to be needed, otherwise I don't get the right answer if I don't send
those first.
The answer is:
0x02 0x00 0x13
So the 3rd byte is the value of the register, 0x13 is the right CHIP_ID.
BR,
Juan
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
