From: Dirk V. <dir...@ya...> - 2011-03-09 20:32:39
|
After modprobe ir-kbd-i2c i see the devices: input: i2c IR (Hauppauge WinTV PVR-350 as /devices/virtual/rc/rc1/input10 rc1: i2c IR (Hauppauge WinTV PVR-350 as /devices/virtual/rc/rc1 ir-kbd-i2c: i2c IR (Hauppauge WinTV PVR-350 detected at i2c-9/9-0018/ir0 [ivtv i2c driver #0] Thanks for help, Dirk > On Mar 8, 2011, at 1:13 PM, Dirk Vornheder wrote: > >> Hi ! >> >> After updating to kernel 2.6.38rc7 and lirc from git lirc dosen't work. >> >> dmesg | grep -i lirc >> >> lirc_dev: IR Remote Control driver registered, major 253 >> IR LIRC bridge handler initialized >> >> Kernel doesn't notice the lirc device from my Hauppauge PVR 350 ! > > Because there isn't one. :) > > The PVR-350's IR part is supported by ir-kbd-i2c. Its not a raw IR > interface, so passing data along via the lirc interface doesn't > really make sense. The signals are decoded in kernel by ir-kbd-i2c > and made available via an input event device, which lircd can grab. > > (lirc_i2c was removed from staging, as its entirely redundant). > > |