Messages in this thread | | | Date | Mon, 24 May 2010 19:48:00 +0200 | From | Henrik Rydberg <> | Subject | Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev2) |
| |
Dmitry Torokhov wrote: [...] >>>> I think we need to add an ioctl to enable user land driver/client to >>>> signal the kernel driver to send all events without filtering, just >>>> once. Hot-plugged devices and X driver starts after user has contacted >>>> with the device are two examples that the client would miss filtered >>>> events. >>>> >>>> Dmitry, do you think it is a valid suggestion? >>> What about using EVIOCGKEY/EVIOCGSW/EVIOCGABS? >> Those EVIOCs only give us the static values (max/min/supported keys, >> etc.). We need their dynamic input data here, the actual x, y, >> button, pressure, etc. Am I missing something about those EVIOs? >> > > Yes you are ;) Supported events are reported via EVIOCGBIT, EVIOCGKEY and > EVIOCGSW will return current state of keys/switches. As far as EVIOCGABS > goes, it also returns, besides min/max/etc, last reported _values_ of the > ABS_* events. >
Ping is not alone. :-)
But it does not work for MT events -- yet.
Henrik
| |