# vdr-remote friendly udev rules

# Predictable event device name examples follow.  To find out the sysfs name
# for your remote control device, look at the strings in the
# /sys/class/input/input*/name files.  Or simply uncomment one of the examples
# below if one matching the input device name of your hardware is included.
# Add "-i /dev/input/event-remote" to PLUGIN_OPTIONS in
# /etc/sysconfig/vdr-plugins.d/remote.conf to make VDR use the correct device.

# On-card receivers on various Hauppauge/Technotrend DVB cards:
#SUBSYSTEM=="input", ATTRS{name}=="DVB on-card IR receiver", SYMLINK+="input/event-remote", GROUP="VDR_GROUP"

# On-card receivers on some Hauppauge Nova-T DVB cards:
#SUBSYSTEM=="input", ATTRS{name}=="cx88 IR (Hauppauge Nova-T DVB-T", SYMLINK+="input/event-remote", GROUP="VDR_GROUP"

# ATI remote wonder and friends:
#SUBSYSTEM=="input", ATTRS{name}=="X10 Wireless Technology Inc USB Receiver", KERNEL!="mouse*", SYMLINK+="input/event-remote", GROUP="VDR_GROUP"


# Example using /dev/input/event2, combine with "-i /dev/input/event2" in
# PLUGIN_OPTIONS in /etc/sysconfig/vdr-plugins.d/remote.conf.  Note that it
# is quite likely that eventN will unpredictably point to different devices
# between reboots; it is recommended to use predictable naming rules like the
# examples above instead.
#KERNEL=="event2", GROUP="VDR_GROUP"