Hi Bengt,

I use udev SYMLINKs to do mine:

  1. cat /proc/bus/input/devices – Look for the IR one, mine is “Bus=0001 Vendor=0070 Product=9202 Version=0001″
  2. Note the “S:” line
  3. cd /sys<everything after the = in the Sysfs line
  4. cat uevent
  5. Note the NAME= line
  6. sudo vi /etc/udev/rules.d/10-local.rules (This is a new file. Please substitute vi with nano/pico/emacs/etc if you prefer)
  7. Add a line into the file ATTRS{name}==”cx88 IR (Hauppauge Nova-S-Plus “, SYMLINK+=”input/dvb-ir”
  8. Note the Space after the word Plus, it’s needed
  9. sudo vi /etc/lirc/hardware.conf – Comment out the REMOTE_MODULES line and add devinput to REMOTE_DRIVER
  10. Replace REMOTE_DEVICE with /dev/input/dvb-ir
This is a copy and paste from my blog entry, ignore the steps you already have :)



On 12/05/2011 22:22, Bengt Nilsson wrote:

I have a Intel DP55SB mobo with a CIR header and a nuvoton-cir device on it.
I just assembled a simple receiver with a 82 ohm resistor and a Everlight IRM-3638N3, and a filter capcitor.

Works fine using "ir-keytable -s" and a MCE remote.

However, there is a problem to set it up in lirc as devinput, since the target number for it in /dev/input/event* is often changing between boots.

When using usb devices, it is convenient to use /dev/input/by-id, since the stable device name can be found there which can be entered into /etc/lirc/hardware.conf.
There is no such entry for the nuvotron-cir device in /dev/input/by-id or by-path.

Is it possible to set up a similar scheme with a stable name reference for the nuvoton-cir device using other methods?

------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay