lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 22 May 2010 05:33:28 -0400 From: Rafi Rubin <rafi@...s.upenn.edu> To: Henrik Rydberg <rydberg@...omail.se> CC: Dmitry Torokhov <dmitry.torokhov@...il.com>, Ping Cheng <pinglinux@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, Mika Kuoppala <mika.kuoppala@...ia.com>, Peter Hutterer <peter.hutterer@...-t.net>, Benjamin Tissoires <tissoire@...a.fr>, Stephane Chatty <chatty@...c.fr>, Michael Poole <mdpoole@...ilus.org> Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3) On 05/21/10 13:49, Henrik Rydberg wrote: > Dmitry Torokhov wrote: >> >> I guess this is where our disconnect lies as when I am looking at the >> event names I view all *_MT_* events as related to the multitouch >> protocol handling. >> > > Yes. It is true that slot control is MT related, but I am looking at this from > the perspective of future expansions like KEY_MT, KEY_REL, and such, finding a > way to signal to user space which events are handled via slots. If we had > ABS_MT_SLOT, we would most likely get applications which store ABS_MT_SLOT as an > attribute of the slot together with ABS_MT_POSITION_X, ABS_MT_TOUCH_MAJOR, etc, > which is just not right. So the proposal is ABS_SLOT. May we have your verdict, > please. :-) > > Henrik > How many fingers can type on cap of a key? (sorry, couldn't resist). Seems to me like part of the problem here is still the overlap between tracking id and slot id. Rafi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists