TT S2-3200 LIRC remote - Multiproto drivers merge?
Hello again,
I finally got the Technotrend S2-3200 to work on LinuxMCE 0710, now I'm wondering how to get the IR transceiver to work. (Not that I've managed to get mythtv working, but since activity on that subject is a bit slower...)
I already tried to ask on the lirc mailing list, but it seems like a very dead place.
My dmesg output proves the transceiver is discovered and I have a /dev/class/input kind of file, I just don't know how to get lirc to work, or how to get a /dev/lirc0 file (I actually already have another transceiver on this computer which apparantly only works with MCE remotes (it's an integrated IR transceiver in my Antec Fusion v2 case)) since there isn't a specific driver in lirc for this technotrend card.
Now, I want to get some facts straight about the multiproto driver:
Is it "done"? What's the big difference between multiproto and multiproto plus? (Even though there hasn't been an update in 5 weeks for the regular drivers, the plus drivers seemed to have more activity)
Or is it correct to assume that now only the software applications need to get a patch to work with our multiproto drivers?
And, looking at the multiproto_plus drivers, I see they "merged" with v4l-dvb - what does this mean exactly?
Thank you for your time,
Jelle De Loecker
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 29 lines · Jelle De Loecker
Hello again,
I finally got the Technotrend S2-3200 to work on LinuxMCE 0710, now I'm
wondering how to get the IR transceiver to work. (Not that I've managed
to get mythtv working, but since activity on that subject is a bit slower...)I already tried to ask on the lirc mailing list, but it seems like a very dead place.
My dmesg output proves the transceiver is discovered and I have a
/dev/class/inputkind of file, I just don't know how to get lirc to work, or how to get a/dev/lirc0file (I actually already have anothertransceiver on this computer which apparantly only works with MCE remotes (it's an integrated IR transceiver in my Antec Fusion v2 case))
since there isn't a specific driver in lirc for this technotrend card.Now, I want to get some facts straight about the multiproto driver:
Is it "done"? What's the big difference between multiproto and multiproto plus? (Even though there hasn't been an update in 5 weeks for
the regular drivers, the plus drivers seemed to have more activity)
Quoted 7 lines
Or is it correct to assume that now only the software applications need
to get a patch to work with our multiproto drivers?And, looking at the
multiproto_plusdrivers, I see they "merged" with v4l-dvb - what does this mean exactly?
I have a patch to make it work, I will post it on the list in a short while.
Bye
Manu
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 38 lines · manu
Quoted 10 lines · Jelle De Loecker
Hello again,
I finally got the Technotrend S2-3200 to work on LinuxMCE 0710, now I'm
wondering how to get the IR transceiver to work. (Not that I've managed
to get mythtv working, but since activity on that subject is a bit slower...)I already tried to ask on the lirc mailing list, but it seems like
a
Quoted 13 lines
very dead place.
My dmesg output proves the transceiver is discovered and I have a
/dev/class/inputkind of file, I just don't know how to get lirc to work, or how to get a/dev/lirc0file (I actually already have anothertransceiver on this computer which apparantly only works with MCE remotes (it's an integrated IR transceiver in my Antec Fusion v2 case))
since there isn't a specific driver in lirc for this technotrend card.Quoted 3 lines
Now, I want to get some facts straight about the multiproto driver:
Is it "done"? What's the big difference between multiproto and multiproto plus? (Even though there hasn't been an update in 5weeks
Quoted 8 lines
for
the regular drivers, the plus drivers seemed to have more activity)Or is it correct to assume that now only the software applications need
to get a patch to work with our multiproto drivers?And, looking at the
multiproto_plusdrivers, I see they "merged"
Quoted 8 lines
with
Quoted 2 lines
v4l-dvb - what does this mean exactly?
I have a patch to make it work, I will post it on the list in a short while.
Bye
Manu
And here it is. It has been generated against a 1- months old multiproto treebut I think it should be OK.
HTH
Bye
Manu
multiproto-bis/multiproto/linux/drivers/media/common/ir-keymaps.c renamed from drivers/media/common/ir-keymaps.c +51 -0
@@ -1507,6 +1507,57 @@EXPORT_SYMBOL_GPL (ir_codes_hauppauge_new); +/* Hauppauge: the newer, gray remotes (seems there are multiple +* slightly different versions), shipped with cx88+ivtv cards. +* almost rc5 coding, but some non-standard keys */ + +IR_KEYTAB_TYPE ir_codes_tt_3200[IR_KEYTAB_SIZE ] = { +/* Keys 0 to 9 */ + [0x03 ] =KEY_1 , + [0x04 ] =KEY_2 , + [0x05 ] =KEY_3 , + [0x06 ] =KEY_4 , + [0x07 ] =KEY_5 , + [0x08 ] =KEY_6 , + [0x09 ] =KEY_7 , + [0x0a ] =KEY_8 , + [0x0b ] =KEY_9 , + [0x0c ] =KEY_0 , + + [0x19 ] =KEY_TEXT ,/* keypad asterisk as well */ + [0x14 ] =KEY_RED ,/* red button */ + [0x12 ] =KEY_MENU ,/* The "i" key */ + [0x18 ] =KEY_MUTE , + [0x25 ] =KEY_VOLUMEUP , + [0x26 ] =KEY_VOLUMEDOWN , + [0x0d ] =KEY_UP , + [0x11 ] =KEY_DOWN , + [0x0e ] =KEY_LEFT , + [0x10 ] =KEY_RIGHT , + + [0x22 ] =KEY_EPG ,/* Guide */ + [0x1a ] =KEY_TV , + [0x1e ] =KEY_NEXTSONG ,/* skip >| */ + [0x13 ] =KEY_EXIT ,/* back/exit */ + [0x23 ] =KEY_CHANNELUP ,/* channel / program + */ + [0x24 ] =KEY_CHANNELDOWN ,/* channel / program - */ + [0x22 ] =KEY_CHANNEL ,/* source (old black remote) */ + [0x0f ] =KEY_ENTER ,/* OK */ + [0x26 ] =KEY_SLEEP ,/* minimize (old black remote) */ + [0x17 ] =KEY_BLUE ,/* blue button */ + [0x15 ] =KEY_GREEN ,/* green button */ + [0x3e ] =KEY_PAUSE ,/* pause */ + [0x3d ] =KEY_REWIND ,/* backward << */ + [0x3f ] =KEY_FASTFORWARD ,/* forward >> */ + [0x3b ] =KEY_PLAY , + [0x3c ] =KEY_STOP , + [0x3a ] =KEY_RECORD ,/* recording */ + [0x16 ] =KEY_YELLOW ,/* yellow key */ + [0x01 ] =KEY_POWER ,/* system power */ +}; + +EXPORT_SYMBOL_GPL (ir_codes_tt_3200); +IR_KEYTAB_TYPE ir_codes_npgtech[IR_KEYTAB_SIZE ] = { [0x1d ] =KEY_SWITCHVIDEOMODE ,/* switch inputs */ [0x2a ] =KEY_FRONT ,
multiproto-bis/multiproto/linux/drivers/media/dvb/ttpci/budget-ci.c renamed from drivers/media/dvb/ttpci/budget-ci.c +11 -0
@@ -249,6 +249,17 @@else budget_ci->ir.rc5_device = rc5_device;break ; +case 0x1019 : +/* For the TT 3200 bundled remote */ +ir_input_init (input_dev, &budget_ci->ir.state, +IR_TYPE_RC5 , ir_codes_tt_3200); + +if (rc5_device <0 ) +/* I don't know the device for now so...*/ + budget_ci->ir.rc5_device =IR_DEVICE_ANY ; +else + budget_ci->ir.rc5_device = rc5_device; +break ;default :/* unknown remote */ ir_input_init(input_dev, &budget_ci->ir.state,
multiproto-bis/multiproto/linux/include/media/ir-common.h renamed from include/media/ir-common.h +1 -0
@@ -139,6 +139,7 @@extern IR_KEYTAB_TYPE ir_codes_asus_pc39[IR_KEYTAB_SIZE ];extern IR_KEYTAB_TYPE ir_codes_encore_enltv[IR_KEYTAB_SIZE ];extern IR_KEYTAB_TYPE ir_codes_tt_1500[IR_KEYTAB_SIZE ]; +extern IR_KEYTAB_TYPE ir_codes_tt_3200[IR_KEYTAB_SIZE ];extern IR_KEYTAB_TYPE ir_codes_fusionhdtv_mce[IR_KEYTAB_SIZE ];extern IR_KEYTAB_TYPE ir_codes_behold[IR_KEYTAB_SIZE ];extern IR_KEYTAB_TYPE ir_codes_pinnacle_pctv_hd[IR_KEYTAB_SIZE ];
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb