linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: Add a detailed multi-touch finger data report protocol
Date: Fri, 7 Nov 2008 09:36:57 -0500	[thread overview]
Message-ID: <3aaafc130811070636g681accf5qae252679c2edcdb9@mail.gmail.com> (raw)
In-Reply-To: <49145016.7090206@euromail.se>

On Fri, Nov 7, 2008 at 9:26 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
> J.R. Mauro wrote:
>> On Fri, Nov 7, 2008 at 6:15 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
>>> In order to utilize the full power of the new multi-touch devices, a
>>> way to report detailed finger data to user space is needed. This patch
>>> adds a multi-touch (MT) protocol which allows drivers to report details
>>> for an arbitrary number of fingers.
>>
>> This is a great idea, Henrik. How will things like X11 go about
>> leveraging this functionality?
>
> What I have in mind is this:
>
> 1. Add support for the MT interface in the trackpad drivers, to the extent
> they support the information. First out is bcm5974, for which the interface
> is designed. A patch is prepared, but I will keep it on hold for a little
> while longer.
>
> 2. Add support for the MT protocol in Xorg synaptics and/or a new Xorg
> multitouch driver. As you might have guessed, I have an experimental
> driver, utilizing the MT protocol. It uses proper matching techniques
> to obtain smooth multi-finger actions. My plan is to launch this in user
> space as soon as there is kernel support.
>
> Henrik
>

Have you worked with MPX? Or was a vanilla-X11 driver simple enough?
How does this all get presented to userspace applications? Multiple
mouse inputs or special stuff that applications would need a rewrite
to leverage?

  reply	other threads:[~2008-11-07 14:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 11:15 [PATCH] input: Add a detailed multi-touch finger data report protocol Henrik Rydberg
2008-11-07 13:34 ` J.R. Mauro
2008-11-07 14:26   ` Henrik Rydberg
2008-11-07 14:36     ` J.R. Mauro [this message]
2008-11-07 14:52       ` Henrik Rydberg
2008-11-07 14:57         ` J.R. Mauro
2008-11-07 15:07           ` Henrik Rydberg
2008-11-11  4:08         ` Peter Hutterer
2008-11-08  0:51 ` Arjan Opmeer
2008-11-08 10:43   ` Henrik Rydberg
2008-11-08 11:29     ` Arjan Opmeer
2008-11-08 12:02       ` Henrik Rydberg
2008-11-11  4:13       ` Peter Hutterer
2008-11-11  4:20 ` Peter Hutterer
2008-11-11 11:19   ` Henrik Rydberg
2008-11-19 16:37 ` Dmitry Torokhov
2008-11-19 16:54   ` Jim Gettys
2008-11-19 23:34     ` Henrik Rydberg
2008-11-21 14:43       ` Jim Gettys
2008-11-19 23:31   ` Henrik Rydberg
2008-11-21 14:44   ` Henrik Rydberg
2008-11-21 16:04     ` Dmitry Torokhov

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=3aaafc130811070636g681accf5qae252679c2edcdb9@mail.gmail.com \
    --to=jrm8005@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rydberg@euromail.se \
    /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).