# vdr-remote friendly udev rules

# Set group for things that look like event devices of remote controls, and
# point the /dev/input/ir symlink to (some) one of them.  This may be enough
# if a remote control matches, and there is only one of them.

SUBSYSTEM=="input", ATTRS{name}=="*DVB*|*dvb*|*saa7146*|X10 Wireless Technology Inc USB Receiver", KERNEL!="mouse*", SYMLINK+="input/ir", GROUP="VDR_GROUP"


# On the other hand, if there are multiple matching devices, /dev/input/ir may
# not always end up pointing to the desired one, so here are some examples that
# add an additional /dev/input/event-remote symlink for a specific device.  We
# assume that the desired GROUP setting was already applied for the device by
# the above rule.  Combine with "-i /dev/input/event-remote" in PLUGIN_OPTIONS
# in /etc/sysconfig/vdr-plugins.d/remote.conf.

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

# 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"

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


# 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"