linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Stéphane Chatty" <chatty@enac.fr>
Cc: Peter Hutterer <peter.hutterer@who-t.net>,
	Rafi Rubin <rafi@seas.upenn.edu>,
	Benjamin Tissoires <tissoire@cena.fr>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] Support for 3M multitouch panel
Date: Sat, 12 Dec 2009 00:30:54 -0800	[thread overview]
Message-ID: <20091212083053.GB7534@core.coreip.homeip.net> (raw)
In-Reply-To: <810DC55F-0AEC-4ED9-9EE8-1671810D810E@enac.fr>

On Sat, Dec 12, 2009 at 09:13:01AM +0100, Stéphane Chatty wrote:
>
> Le 11 déc. 09 à 23:36, Dmitry Torokhov a écrit :
>
>> Hi Stephane,
>>
>>
>>> +static int emulate_touchscreen = 1;
>>> +module_param_named(emulate_touchscreen, emulate_touchscreen, int,  
>>> 0600);
>>> +MODULE_PARM_DESC(emulate_touchscreen,
>>> +		"Touchscreen emulation on 3M multitouch panel (0=off, 1=on)");
>>> +
>>
>> I thought we agreed that this option is unnecessary.
>>
>
> Well, actually I was unsure what the conclusion of your discussion was. I 
> decided that I would send this patch as is to see what happens :-)
>
> Here are our options:
>  1) mix touchscreen emulation and multitouch at all times
>  2) only activate touchscreen emulation when requested (module  
> parameter, or something else)
>  3) have separate input nodes
>  4) kill the touchscreen emulation code, let the higher layers do it if 
> necessary
>
> I personally would rule out option 4. The others are OK to me. Your  
> thoughts?

#1 until everyone moves on to multitouch... and everyone means
_everyone_, not only X and distributions. I could consider #3 if we see
that multitouch data overwhelms oldish userspace, but OTOH users would
probably prefer to update their userspace to take advantage of their
hardware so the multitouch data will be opened anyway... so we back to
#1.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-12  8:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 10:12 [PATCH] Support for 3M multitouch panel Stephane Chatty
2009-12-11 12:42 ` Petr Štetiar
2009-12-11 14:10   ` Fwd: " Stephane Chatty
2009-12-11 22:36     ` Dmitry Torokhov
2009-12-12  8:13       ` Stéphane Chatty
2009-12-12  8:30         ` Dmitry Torokhov [this message]
2009-12-22 18:00       ` Stéphane Chatty
2009-12-22 18:56         ` Dmitry Torokhov
2009-12-22 19:27           ` Stéphane Chatty
2009-12-22 22:04           ` Stephane Chatty
2009-12-23  0:22             ` Jiri Kosina
2009-12-23  0:33             ` Jiri Kosina
2009-12-23  9:47               ` Stéphane Chatty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091212083053.GB7534@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=chatty@enac.fr \
    --cc=linux-input@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rafi@seas.upenn.edu \
    --cc=tissoire@cena.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).