Holger Waechtler wrote: > Oliver Endriss wrote: > > Holger Waechtler wrote: > > > > The new lirc extension is just another driver compiled into lircd. > > /dev/lirc is not used! It simply takes the codes from > > /dev/input/eventX and feeds them into lircd. This way it should be > > possible to use any /dev/input/* device to control lirc. The driver > > itself is very short. The hard thing is understanding the lirc > > source code :-) > > (one more reason for a direct input driver;)
Perhaps, but it's already working. :-) > > Ok, I'll try. > > 1. If I press a key on my hauppauge remote control, the *old* > > firmware emits a key-down event. When I release the key, a key-up > > event is generated. > > no. Key up events were gererated in the firmware immidiatly after > each key down event. Sorry, but this is wrong (with the haupauge remote control, at least). I am absolutely sure about this, see the following excerpt from /var/log/messages (note the timestanmps): hold down the key '1': | Sep 25 13:24:36 orion kernel: GPIO0 irq 8 4 | Sep 25 13:24:36 orion kernel: GPIO0 irq 08 | Sep 25 13:24:36 orion kernel: dvb: ircommand = 80000001 | Sep 25 13:24:36 orion kernel: GPIO0 irq exit 0 release the key '1': | Sep 25 13:24:42 orion kernel: GPIO0 irq 8 4 | Sep 25 13:24:42 orion kernel: GPIO0 irq 08 | Sep 25 13:24:42 orion kernel: dvb: ircommand = 00000001 | Sep 25 13:24:42 orion kernel: GPIO0 irq exit 0 Oliver -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
