Hi Gerd, I had a fiddle with the latest saa7134-0.2.9 snapshot (20030910) using Linux 2.4.22 and v4l2-20030826 patches. I wanted to see if I could get the remote control on my Flyvideo3000 working. I managed to compile the module, and load it in fine. However I'm not seeing any output in the syslog when I press remote buttons. I changed the batteries too, just to make sure. I tried loading the module as follows: modprobe ir-common debug=4 (this loads the input.o module) modprobe saa7134 card=2 But still no messages. lsmod shows ir-common in use by saa7134. I loaded the evdev module but it remains 'unused', regardless of whether I load it before or after ir-common or saa7134. What more do I need to do? I'd love to play around with this stuff, debug it, test it, use it... but I'm not sure where I go from here...? BTW there's nothing in /dev/input even with input.o and ir-common.o loaded and I'm using Gentoo with devfs. Cheers, David. --------------------------------- Original Email: # To: video4linux list <video4linux-list@xxxxxxxxxx> # Subject: bttv9 + saa7134 + IR + input layer ... # From: Gerd Knorr <kraxel@xxxxxxxxxxx> # Date: Thu, 28 Aug 2003 14:45:00 +0200 Hi, People following the snapshots closely might have noticed already that I've started adding input layer support for the infrared remote controls to the drivers. For bttv this new stuff will coexist with the current lirc drivers. For saa7134 it very likely will be the only way to receive input from the remote control. I'm not going to add a very hackish gpio interface for other kernel modules again. What is there now: * [both] a ir-common.[ch] module with some common code for IR remote controls. * [bttv] a ir-kbd-i2c.c module which supports i2c IR chips (i.e. replaces lirc_i2c). Currently supports Hauppauge only, others need fixes. Requires a 2.6.x kernel. * [bttv] there is a new bttv-input.c source file with gpio remote control support. Avermedia should work, others need fixes. * [saa7134] there is a new saa7134-input.c file ... That one has a debug printk only for now which should print something into the kernel log for flyvideo cards. If you press a key on the remote these events will be passed as key press and release events to the input layer. The IR remote will act very much like a keyboard, with auto-repeat and all that. auto-repeat can be disabled through (repeat=0 insmod option for ir-common). If you want to play with / debug that stuff you might want to download http://bytesex.org/snapshot/input-<date>.tar.gz with some input layer userspace tools (list devices, dump input events, change keycode maps, ...). Don't forget to load the evdev module for that. If you prefere to have your IR keys processed by lircd, not as keyboard key strokes, you might check out the latest lirc cvs. lircd recently got support for receiving input from /dev/input/event<n>. I havn't tested that myself yet through. To build the latest driver snapshots you either need a 2.4.0-test[34] kernel or a 2.4.22 kernel with bytesex.org patches. Comments? Questions? Flames? Patches? Gerd -- You have a new virus in /var/mail/kraxel
