Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)

From: Rafi Rubin
Date: Sat May 22 2010 - 05:34:48 EST

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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at