On Mon, May 24, 2010 at 10:21 AM, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote: > On Monday 24 May 2010 10:06:15 am Ping Cheng wrote: >> >> This topic is outside of the _MT_ protocol discussion. >> >> >> >> However, it is indeed an issue with all filtered input events, both >> >> for MT and regular ones. >> >> >> >> 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. Oh, My God! I should have listened to Mark Twain :). Ping -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
