Success finally!! I missed loading the i2c_dev module. Once I followed this order of loading modules, everything worked. modprobe i2c_dev (i2c_core was already loaded for the motherboardboard i2c device) modprobe i2c-algo-bit modprobe lirc_i2c
The real i2c IR device shows up as /dev/lirc1, so run lircd to listen on that: /usr/local/lirc/sbin/lircd -d /dev/lirc1 What worked: - WinTV_PVR-USB2 (fourth version with IR blaster and the new PVR-350 kind of remote) http://www.mythtv.org/wiki/index.php/PVR-350_Remote_Quick_Guide - Kernel 2.6.21 with the in-tree pvrusb2 module on CentOS 4.4 - lirc 0.8.2pre2 Here is what you see in /var/log/messages: ====================================== i2c /dev entries driver lirc_dev: IR Remote Control driver registered, at major 61 lirc_i2c: no version for "lirc_unregister_plugin" found: kernel tainted. bttv: driver version 0.9.17 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture cx2388x v4l2 driver version 0.0.6 loaded lirc_i2c: chip found @ 0x18 (Hauppauge IR) lirc_dev: lirc_register_plugin: sample_rate: 10 lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150)) lirc_dev: lirc_register_plugin: sample_rate: 10 ====================================== The device found @ 0x18 is the fake one emulated by the pvrusb2 driver. Hope this helps others, - Siddhartha On 5/13/07, Mike Isely <[EMAIL PROTECTED]> wrote: > On Sun, 13 May 2007, Siddhartha Jain wrote: > > > On 5/13/07, Mike Isely <[EMAIL PROTECTED]> wrote: > > > On Sun, 13 May 2007, Siddhartha Jain wrote: > > > > > > > Thanks for the pointer, Mike. Yes, I do have one of those new units > > > > with the IR blaster. So from your earlier post, I understand that you > > > > intend to stop supporting the IR function in the pvrusb2 driver and > > > > leave it to the lirc project? > > > > > > You make it sound like a bad thing. > > > > That wasn't my intention :) I just wanted to know where to direct my > > attention - pvrusb2 or the lirc_i2c module. > > I was half joking :-) > > > > > > I fully understand and appreciate that you want to leave the IR part > > to the lirc project where it is best handled. > > > > > > > > > > > > > I did compile lirc-0.8.2-pre2 but haven't had success with that either > > > > yet :( So I will keep trying that and post to the lirc list. > > > > > > It would probably also be useful to post here specifically what you did > > > to get it working, once you have it working. (Or for that matter, hint, > > > hint, anyone else who has walked through the process of getting the new > > > IR receiver working with lirc would be welcome to post details here...) > > > > > > > I sure will do that. Right now, I am trying to disable the IR portion > > of the kernel's in-tree pvrusb2 module by passing this in > > modprobe.conf: > > options pvrusb2 ir_mode=0 > > > > And got this in dmesg: > > pvrusb2: Unknown parameter `ir_mode' > > > > So I went to the source > > [EMAIL PROTECTED] pvrusb2]# pwd > > /usr/src/linux/drivers/media/video/pvrusb2 > > > > [EMAIL PROTECTED] pvrusb2]# grep ir_mode * > > > > Returns nothing. > > > > I checked the standalone version and saw that the ir_mode option does > > exist in there. Any specific reason to exclude it from the in-tree > > version? > > Because it didn't get there yet... (The feature was only recently just > added to the standalone driver; it should get into the next appropriate > kernel version either 2.6.22 or 2.6.23 depending on whether or not the > V4L maintainer managed to push it up in time.) > > > > > > Is it absolutely necessary to disable the IR function in pvrusb2 to > > get lirc_i2c working (which shows up as /dev/lirc1 and I still haven't > > been able to get it working). > > No, it is not absolutely necessary. But realize that leaving that > "enabled" doesn't do anything except make a virtual IR receiver chip > visible on the bus that doesn't work. But if you leave it enabled and > you do eventually get the new receiver going, then you'll just have two > receivers present - one that returns codes and one that doesn't return > anything. > > -Mike > > > -- > | Mike Isely | PGP fingerprint > Spammers Die!! | | 03 54 43 4D 75 E5 CC > 92 > | isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 > E8 > | | > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
