Evdev, buttonup events and lirc (Cinergy 400/saa7134)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hello all, thanks for the help so far.

I now have a working remote control both in kbd and lirc, running on 2.4.22 w/kraxel patches and CVS snapshot 101603. There are really only two issues that I have to sort out before everything is perfect, and they are as follows:

- Lirc CVS version is reading values out of /dev/input/event0, but it's only reading one value at a time. Each button press on the remote generates two events, of which the second one seems to be the button release. However, the button up event stays on the stack until next time I press a button, so that when lircd reads the new value it gets the button up event instead, while the new button goes to the top of the stack. And the third time I press a button, the second button is popped off and sent to the client app .. forcing me to do delayed navigation by predicting the required buttons in advance.. you see the problem I presume ;)

Now, I am not a programmer and definitely not familiar with the inner workings of evdev modules, however if I were to speculate I'd guess that every button press generates an event that informs the evdev-aware client that a new event is on the stack. Lircd in its ignorance then only reads the first value off the stack and either recognizes this as a known eventcode or discards it and logs a warning. I am awaiting a response to a similar query on the lirc mailing list, however there may not be any good ways of solving this from within lirc so I am looking for a way to make saa7134-input.c only send the button down events, if possible. Other suggestions are of course welcome.

- Disregarding the dysfunctional aspects of the current situation there still remains the problem of having a keyboard event generated in addition to a lirc event, when using apps that support both. Especially the arrow keys are hard to use, you end up only being able to navigate to itens with an odd number (starting at one and adding two, four etc). Can the keyboard emulation be turned off by a module parameter? if not, which lines do I comment out to plug this up for the time being?

Cheers,

Ole Andre




[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux