From: Dirk V. <dir...@ya...> - 2011-03-08 18:26:45
|
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 ! Mar 7 18:52:01 pcneu lircd: lircd(default) ready, using /var/run/lirc/lircd Mar 7 19:00:19 pcneu lircd: accepted new client on /var/run/lirc/lircd Mar 7 19:00:19 pcneu lircd: could not get file information for /dev/lirc Mar 7 19:00:19 pcneu lircd: default_init(): No such file or directory Mar 7 19:00:19 pcneu lircd: WARNING: Failed to initialize hardware lircd is compiled with ./configure --with-driver=userspace --prefix=/usr ps -ef | grep -i lircd root 5970 1 0 17:34 ? 00:00:00 /usr/sbin/lircd grep -i ir /usr/src/linux/.config CONFIG_LIRC=m CONFIG_IR_NEC_DECODER=m CONFIG_IR_RC5_DECODER=m CONFIG_IR_RC6_DECODER=m CONFIG_IR_JVC_DECODER=m CONFIG_IR_SONY_DECODER=m CONFIG_IR_RC5_SZ_DECODER=m CONFIG_IR_LIRC_CODEC=m CONFIG_IR_ENE=m CONFIG_IR_IMON=m CONFIG_IR_MCEUSB=m CONFIG_IR_NUVOTON=m CONFIG_IR_STREAMZAP=m CONFIG_IR_WINBOND_CIR=m CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_LIRC_STAGING=y CONFIG_LIRC_BT829=m CONFIG_LIRC_IGORPLUGUSB=m CONFIG_LIRC_IMON=m CONFIG_LIRC_IT87=m CONFIG_LIRC_ITE8709=m CONFIG_LIRC_PARALLEL=m CONFIG_LIRC_SASEM=m CONFIG_LIRC_SERIAL=m CONFIG_LIRC_SERIAL_TRANSMITTER=y CONFIG_LIRC_SIR=m CONFIG_LIRC_TTUSBIR=m CONFIG_LIRC_ZILOG=m Dirk |
From: Jarod W. <ja...@wi...> - 2011-03-08 18:55:05
|
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). -- Jarod Wilson ja...@wi... |
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). > > |