[mythtv-users] Looking for clarity on MythTV, to LIRC, or not to LIRC, ir-keytable, and key mappings

[Paul Bender]

On 4/14/2012 9:36 AM, Dave Brown wrote:
>
>
>
>     What I do in MiniMyth is use udev to create device symbolic links
>     from the hardware's characteristics (e.g., vendor id, product id,
>     serial number). Once this is done, device can be referred to by the
>     symbolic link, which does not change as it is constructed from the
>     hardware's characteristics. For example, newer versions of udev
>     contain a rules script (60-persistent-input.rules) that does this
>     for input devices.
>
>     _________________________________________________
>     mythtv-users mailing list
>     mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
>     http://www.mythtv.org/mailman/__listinfo/mythtv-users
>     <http://www.mythtv.org/mailman/listinfo/mythtv-users>
>
>
> Hi Paul
>
> Ive tried this using udev and have it matched to the remote.   I had set
> it to REMOTE_DEVICE="/dev/input/remote" in hardware.conf. However, I
> dont get any output from the remote using irw.
>
> What im having after each boot is change the remote device to /dev/lirc0
> or /dev/lirc1 depending on where the remote is placed agains
> either /sys/class/rc/rc0/ or /sys/class/rc/rc1/
>
> I cant find anywhere to point /sys/class/rc/rc0/ to /dev/input/remote

The /dev/input devices created by udev are input devices not lirc 
devices. What I did for MiniMyth was to create my own udev script that 
created persistent device symbolic links for lirc devices.