From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754505Ab0EVKje (ORCPT ); Sat, 22 May 2010 06:39:34 -0400 Received: from ch-smtp03.sth.basefarm.net ([80.76.149.214]:36436 "EHLO ch-smtp03.sth.basefarm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754114Ab0EVKjc (ORCPT ); Sat, 22 May 2010 06:39:32 -0400 Message-ID: <4BF7B438.8000001@euromail.se> Date: Sat, 22 May 2010 12:38:48 +0200 From: Henrik Rydberg User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: Rafi Rubin CC: Dmitry Torokhov , Ping Cheng , Andrew Morton , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Mika Kuoppala , Peter Hutterer , Benjamin Tissoires , Stephane Chatty , Michael Poole Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3) References: <1274457354-5570-1-git-send-email-rydberg@euromail.se> <4BF6B673.1080507@euromail.se> <20100521165218.GA26439@core.coreip.homeip.net> <4BF6BB43.2020405@euromail.se> <20100521172222.GB26439@core.coreip.homeip.net> <4BF6C303.7030804@euromail.se> <20100521174140.GA23155@core.coreip.homeip.net> <4BF6C7B6.2020008@euromail.se> <4BF7A4E8.3050806@seas.upenn.edu> In-Reply-To: <4BF7A4E8.3050806@seas.upenn.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 83.248.196.134 X-Scan-Result: No virus found in message 1OFm6e-0004bg-BK. X-Scan-Signature: ch-smtp03.sth.basefarm.net 1OFm6e-0004bg-BK 776e95666eeba61277c87aad566a6cb2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Rafi Rubin wrote: > 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? It depends on the size of the key, does it not. :-) Getting serious, it is anyone's guess what will happen next, but I was picturing a table, with a large multitouch screen and buttons along the side of the table. Sure, we can do "ABS_BTN_0", "ABS_BTN_1", etc, but with slots in place, it seems more natural to use something like "ABS_MT_BTN_X". While at it, REL_MT event makes sense for those touchscreen techniques which register changes, like acoustic pulse recognition. > Seems to me like part of the problem here is still the overlap between tracking > id and slot id. Would you care to elaborate? Cheers, Henrik