[mythtv-users] ir-kbd-i2c and StreamZap?

Jarod Wilson jarod at wilsonet.com
Thu Apr 7 22:40:14 UTC 2011

On Apr 6, 2011, at 8:30 PM, Brian Long wrote:

> Fedora 14
> MythTV Version   : v0.24-231-gc2baf1b
> MythTV Branch    : fixes/0.24
> Network Protocol : 63
> Library API      : 0.24.20101129-1
> QT Version       : 4.7.1
> Options compiled in:
>  linux release using_alsa using_jack using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg
> Has anyone converted to the newer kernels using ir-kbd-i2c with a StreamZap IR receiver?

Huh? That, um, makes no sense. ir-kbd-i2c is for IR receivers that
are onboard another device, such as a tuner card, and exposed over
an i2c bus... All you need is the streamzap module.

>   When I boot my frontend, I see this:
> [    6.478033] Registered IR keymap rc-streamzap
> [    6.478294] input: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:04.0/usb3/3-2/3-2:1.0/rc/rc0/input3
> [    6.478426] rc0: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:04.0/usb3/3-2/3-2:1.0/rc/rc0
> [    6.499176] streamzap 3-2:1.0: Registered Streamzap, Inc. Streamzap Remote Control on usb3:2
> ir-keytable shows this:
> Found /sys/class/rc/rc0/ (/dev/input/event3) with:
>         Driver streamzap, table rc-streamzap
>         Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other
>         Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC other
>         Repeat delay = 500 ms, repeat period = 33 ms
> ir-keytable -t with my remote shows a bunch of codes (for most buttons).  lircd is running as follows:
> /usr/sbin/lircd --driver=devinput --device=/dev/lirc0 -o /dev/lircd

This is wrong. For devinput, you need /dev/input/event3, based on your
ir-keytable output, or even better, its /dev/input/by-id/<foo> symlink.

To use /dev/lirc0, you just use the default lircd driver. You'll also
want to disable in-kernel decoding if you go this route though, or
you may get key events via both lircd and the linux input layer.

> mythfrontend starts up and connects to /dev/lircd without problems, however it does not see any of the commands.  What am I supposed to change in ~/.mythtv/lircrc or am I supposed to move that file out the the way?  I saw one post where someone using ir-kbd-i2c disabled lirc completely and just relied on the kernel driver passing this through, but I saw Jaron say lirc was still required for certain functionality.
> What am I missing?

Configuration problem.

Jarod Wilson
jarod at wilsonet.com

More information about the mythtv-users mailing list