Hi, there.
My 3200 remote isn't working properly with v4l-dvb current drivers. Some buttons are switched (power button is 2, 2 is 4, 3 is 5 and so on) or unresponsive.
Any ideas as what's going on were? There was a fix for multiproto that involved patching yourpath/linux/drivers/media/dvb/ttpci/budget-ci.c with something like:
break; case 0x1010: case 0x1017: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);
to something like:
break; case 0x1010: case 0x1017: case 0x1019: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);
Editing the file on v4l-dvb shows this:
break; case 0x1010: case 0x1017: case 0x101a: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);
The third value on v4l-dvb is different. Any ideas?
On Tuesday 04 of November 2008, hudo kkow wrote:
Hi, there.
My 3200 remote isn't working properly with v4l-dvb current drivers. Some buttons are switched (power button is 2, 2 is 4, 3 is 5 and so on) or unresponsive.
Any ideas as what's going on were? There was a fix for multiproto that involved patching yourpath/linux/drivers/media/dvb/ttpci/budget-ci.c with something like:
break; case 0x1010: case 0x1017: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);to something like:
break; case 0x1010: case 0x1017: case 0x1019: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);
Editing the file on v4l-dvb shows this:
break; case 0x1010: case 0x1017: case 0x101a: /* for the Technotrend 1500 bundled remote */ ir_input_init(input_dev, &budget_ci->ir.state, IR_TYPE_RC5, ir_codes_tt_1500);
The third value on v4l-dvb is different. Any ideas?
On some markets the TT S2-3200 is sold with remote originally from TT 1500, so in this cases the table from TT 1500 should be used. Edit the code to:
break; case 0x1010: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */
and everything should be ok.
BR,
Ales
Ales Jurik wrote:
On some markets the TT S2-3200 is sold with remote originally from TT 1500, so in this cases the table from TT 1500 should be used. Edit the code to:
break; case 0x1010: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */
and everything should be ok.
I originally added the TT 1500 remote keymap handling and on my TT1500 C device the correct subsystem id was 0x1017. It seems like 0x1019 would need to be added for the 3200. I've also had people tell me that the TT 1500 T has the subsystem id 0x1012, so in order to make the bundled remote work with the T model that case should be moved here too.
Is anyone on the list aware of any breakage which would occur on their systems if the code was changed to be like this:
case 0x1010: case 0x1012: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */
If not, I could make the patch and mail it to the linux-dvb list.
On Tue, Nov 4, 2008 at 2:00 PM, Ville-Pekka Vainio vpivaini@cs.helsinki.fi wrote:
Ales Jurik wrote:
On some markets the TT S2-3200 is sold with remote originally from TT 1500, so in this cases the table from TT 1500 should be used. Edit the code to:
break; case 0x1010: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */
and everything should be ok.
I originally added the TT 1500 remote keymap handling and on my TT1500 C device the correct subsystem id was 0x1017. It seems like 0x1019 would need to be added for the 3200. I've also had people tell me that the TT 1500 T has the subsystem id 0x1012, so in order to make the bundled remote work with the T model that case should be moved here too.
Is anyone on the list aware of any breakage which would occur on their systems if the code was changed to be like this:
case 0x1010: case 0x1012: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */If not, I could make the patch and mail it to the linux-dvb list.
-- Ville-Pekka Vainio
Hi. I've already done the patch for my case (case 0x1019:). I was ready to send it to ML if there are more cases with troublesome remotes, I can add it to my my patch, or you send yours.
Stay in touch. Thanks.
hudo kkow wrote:
Hi. I've already done the patch for my case (case 0x1019:). I was ready to send it to ML if there are more cases with troublesome remotes, I can add it to my my patch, or you send yours.
Stay in touch. Thanks.
Please send your patch since you already have one. You could change case 0x1012 to use the Technotrend 1500 code as well, so that we'd have "out-of-the-box" support for the Technotrend 1500-T. Thanks.
On Tue, Nov 4, 2008 at 4:47 PM, Ville-Pekka Vainio vpivaini@cs.helsinki.fi wrote:
hudo kkow wrote:
Hi. I've already done the patch for my case (case 0x1019:). I was ready to send it to ML if there are more cases with troublesome remotes, I can add it to my my patch, or you send yours.
Stay in touch. Thanks.
Please send your patch since you already have one. You could change case 0x1012 to use the Technotrend 1500 code as well, so that we'd have "out-of-the-box" support for the Technotrend 1500-T. Thanks.
-- Ville-Pekka Vainio
Ok. Patch sent do dvb ML.
http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030145.html
Thanks
-
Ales Jurik -
hudo kkow -
Ville-Pekka Vainio