From mboxrd@z Thu Jan  1 00:00:00 1970
From: Henrik Rydberg <rydberg@euromail.se>
Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)
Date: Sat, 22 May 2010 19:47:18 +0200
Message-ID: <4BF818A6.6000801@euromail.se>
References: <1274457354-5570-1-git-send-email-rydberg@euromail.se>	 <AANLkTikBWzgRmso0oQNXcTxeExdKZORXYbIwK9CcMl85@mail.gmail.com>	 <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>	 <4BF7B438.8000001@euromail.se> <1274539582.13705.132.camel@cndougla-ubuntu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <linux-input-owner@vger.kernel.org>
Received: from ch-smtp03.sth.basefarm.net ([80.76.149.214]:45612 "EHLO
	ch-smtp03.sth.basefarm.net" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1755863Ab0EVRrx (ORCPT
	<rfc822;linux-input@vger.kernel.org>);
	Sat, 22 May 2010 13:47:53 -0400
In-Reply-To: <1274539582.13705.132.camel@cndougla-ubuntu>
Sender: linux-input-owner@vger.kernel.org
List-Id: linux-input@vger.kernel.org
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Rafi Rubin <rafi@seas.upenn.edu>, Dmitry Torokhov <dmitry.torokhov@gmail.com>, Ping Cheng <pinglinux@gmail.com>, Andrew Morton <akpm@linux-foundation.org>, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Mika Kuoppala <mika.kuoppala@nokia.com>, Peter Hutterer <peter.hutterer@who-t.net>, Benjamin Tissoires <tissoire@cena.fr>, Stephane Chatty <chatty@enac.fr>, Michael Poole <mdpoole@troilus.org>

Chase Douglas wrote:
> On Sat, 2010-05-22 at 12:38 +0200, Henrik Rydberg wrote:
>> 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.

s/ABS/KEY/

> 
> Shouldn't this be handled in userspace? I don't think we want to be
> quirking drivers for instances where the same touchscreen is overlaid on
> buttons in some cases, but not in others. If we don't quirk, we'd need
> some mechanism to tell the driver about such buttons.

Perhaps you would like to clarify what "this" means here, and how you arrive at
quirking drivers.

Henrik