Terratec Cinergy T USB XXS: remote does not work with 1.20 firmware
[This is a repost of a message sent to the obsolete [email protected] list.]
Hi.
I am trying to get the remote controller with a Terratec Cinergy T USB XXS. With the firmware dvb-usb-dib0700-1.10.fw, the remote sends codes (not perfectly, but I can see where I am going).
On the other hand, with dvb-usb-dib0700-1.20.fw, the remote does not detect anything. After some tracking, I found that in dib0700_rc_query_v1_20 (from dib0700_devices.c), the status from usb_bulk_msg is always -110 (-ETIMEDOUT).
Is there some way I can help fixing things? I do not mind using the old firmware, but I would like to help improving things.
Regards,
Signature · 1 line
Nicolas George
Quoted 13 lines · Nicolas George
[This is a repost of a message sent to the obsolete [email protected] list.]
Hi.
I am trying to get the remote controller with a Terratec Cinergy T USB XXS. With the firmware dvb-usb-dib0700-1.10.fw, the remote sends codes (not perfectly, but I can see where I am going).
On the other hand, with dvb-usb-dib0700-1.20.fw, the remote does not detect anything. After some tracking, I found that in
dib0700_rc_query_v1_20(fromdib0700_devices.c), the status fromusb_bulk_msgis always -110 (-ETIMEDOUT).
Quoted 7 lines
Is there some way I can help fixing things? I do not mind using the old firmware, but I would like to help improving things.
Regards,
--
Nicolas George
That's code I wrote, based on information provided by Patrick over at Dibcom.
I would have to look at the code, but if I recall, the code is designed to return -ETIMEDOUT during normal operation when no key press is detected. That said, seeing that return condition should not be perceived as a problem.
Are there any cases where it returns something *other* than -ETIMEDOUT? Because if so, then the keypress is probably being received but not processed properly.
I would recommend you add a line of code to printk() any return condition other than -ETIMEDOUT, and see if something shows up in the log when you try to use the remote control.
Devin
Signature · 3 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
Hi. Thanks for your reply.
Le duodi 2 ventôse, an CCXVII, Devin Heitmueller a écrit :
Quoted 3 lines
I would have to look at the code, but if I recall, the code is designed to return
-ETIMEDOUTduring normal operation when no key press is detected.
That is what I thought it was supposed to do.
Quoted 3 lines
Are there any cases where it returns something *other* than
-ETIMEDOUT? Because if so, then the keypress is probably being received but not processed properly.
I just re-did it:
if(status != -ETIMEDOUT)
printk("dib0700_rc_query_v1_20: status = %d\n", status);just after usb_bulk_msg. Then I press keys on the remote: I see mostly nothing, but once in a while, I get:
[ 800.589349] dib0700_rc_query_v1_20: status = 0 [ 800.589366] dib0700: Unknown remote controller key: 00 13 36 c9
I did not manage to find any pattern in the keys that come through: that seems completely random.
If I do use the 1.10 firmware and do the same in dib0700_rc_query_legacy just after the test against 0.0.0.0, I get a diagnosis line (or several) each time I press a key on the remote, without any loss.
I fear this means the problem is in the firmware itself. I am willing to do further tests, but I have no competence at all regarding firmwares for such devices.
Regards,
Signature · 1 line
Nicolas George
Le tridi 3 ventôse, an CCXVII, Nicolas George a écrit :
Quoted 11 lines
I just re-did it:
if(status != -ETIMEDOUT) printk("dib0700_rc_query_v1_20: status = %d\n", status);just after
usb_bulk_msg. Then I press keys on the remote: I see mostly nothing, but once in a while, I get:[ 800.589349] dib0700_rc_query_v1_20: status = 0 [ 800.589366] dib0700: Unknown remote controller key: 00 13 36 c9
Quoted 6 lines
I did not manage to find any pattern in the keys that come through: that seems completely random.
If I do use the 1.10 firmware and do the same in
dib0700_rc_query_legacyjust after the test against 0.0.0.0, I get a diagnosis line (or several) each time I press a key on the remote, without any loss.
Excuse-me to insist, but isn't there anything at all I can do to help get this remote controller working?
Regards,
Signature · 1 line
Nicolas George