[mythtv-users] mceusb as an input device

Harry Orenstein holists at optonline.net
Mon Mar 7 04:01:27 UTC 2011


On Saturday, March 05, 2011 10:53:48 pm Jarod Wilson wrote:

> So does that thing actually come with a TiVo remote? The in-kernel driver
> is only set up to handle the MCE remotes, its likely the TiVo remote uses
> different signaling. Judging from TiVo lircd.conf's out there, that's the
> case. Not sure exactly what it uses, and/or if the protocol is known by
> the in-kernel decoders. Worst-case, you should be able to use it the same
> old /dev/lirc0 way though.
> 
The remote seems to really be a TiVo remote.  It even has the key with the 
little TiVo guy and the thumb keys.  It turns out that the transceiver also 
recognizes RC-5 codes, so my recent work getting ir-kbd-i2c working with my 
PVR-250 is applicable.  I just replaced the default keymap for rc_rc6_mce in 
the /etc/rc_maps.cfg with one I created and set the protocol for the device to 
RC-5 using ir-keytable.
> 
> Nope, I think its just a case of this being the one and only mceusb device
> I know of that comes with a non-RC6 MCE remote.

Using the TiVo remote would be nice, but I can get by with my JP-1 OFA 
universal (guess the effort we spent 7 years ago was worth it).  I may spend 
some time playing around with the TiVo remote to see if any remote with a 
supported kernel module responds to it, but it would be impolite for me to ask 
if anyone is working on a kernel module specifically to handle TiVo codes when 
I am not able to do the coding myself.        This is me not asking ;)

I hate to ask more questions after all your good help, but now that I'm more 
"mainstream" with my MCE transceiver I'm curious about the best approach to 
using it.  The standard keymap for MCE remotes maps scancodes to non-ASCII 
keys (e.g.: Play to KEY_PLAY, Menu to KEY_MENU, etc.).  Is the best way to 
handle this to set up the key mappings in Myth to use these defaults?  If so, 
how do I know what the key codes should be in Myth (KEY_UP = Up?  KEY_VOLUMEUP 
= VolumeUp?  Just drop "KEY_" and case doesn't matter?) and what about keys 
that get picked up by the OS (like volume up/down, mute, power, etc.), which 
get acted on outside of Myth?

One more question.  When I set up my custom keymap I have to use ir-keytable 
to set the protocol to RC-5 to use it.  What is the best way to automate that 
on boot up?  Should I put 'echo RC-5 > /sys/class/rc/rc0/protocols' in 
rc.local?  Should I use ir-keytable instead?  Is there a way to do this in a 
modprobe conf file (executing the command after the module loads)?

Sorry to be such a pain.  It's the first time I'm doing a major upgrade on my 
Myth system since I originally set it up.  Getting everything to work just 
right is taking more effort than I would have guessed.

-- Harry O.


More information about the mythtv-users mailing list