linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping Cheng <pinglinux@gmail.com>
To: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
	Chase Douglas <chase.douglas@canonical.com>,
	Rafi Rubin <rafi@seas.upenn.edu>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: Wacom based devices and the mt kernel protocol.
Date: Sat, 19 Jun 2010 22:35:43 -0700	[thread overview]
Message-ID: <AANLkTikExwM_LBUw_-z2eimO96Dxs_fNfAM4jlftXyHM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinq_3P-QrTqsEdtyMbBtc9EXhahclER_4s5_Kx2@mail.gmail.com>

Hi Mohamed,

I am glad that you've initiated this email thread. Otherwise, I would
have to find a proper way to explain the current status of Wacom MT
support. Please see my comments inline.

Thank you,

Ping

On Fri, Jun 18, 2010 at 4:20 AM, Mohamed Ikbel Boulabiar
<boulabiar@gmail.com> wrote:
> Hi,
>
> Now we can find many multitouch devices based on wacom Wacom panel/digitizer
> Bamboo Pen&Touch, HP tm2, Fujitsu LifeBook T4410 & T4310, etc...
>
> it seems that these devices are supported in some way in Linux Kernel,
> but I want to know if they are compliant with the MT Linux protocol.

As most of you know, the current Wacom two finger touch devices have
been supported on Linux since last Oct.  However, they are not
supported with the current in-kernel MT protocol, aka, MT type A
protocol.

I know you would ask me why. The reason is simple: it doesn't support
the Wacom case - finger tracking.  If you wonder why I don't work with
the other developers to support Wacom MT case, I can assure you that I
am working with them. We will support Wacom MT devices once the
appropriate protocol is available.

> N-Trig based devices and Stantum ones are the most compliant,

That's fair since they don't need to track the fingers.

> so Wacom situation needs to be clarified specially considering they are HID
> devices (meaning similar to the others devices which respect the
> protocol).

Well, it is not a pure HID issue.  It is more of how we want to
support MT on Linux issue.

> This impact very much the decision of a Linux user wanting to buy wacom mt device.

I think end users have already got the Linux support from Wacom.  Can
you share the specific issues that are preventing Linux end users from
buying a Wacom MT devices? If I didn't misunderstand your point here,
you are talking about Linux users, not Linux developers/hackers,
right?

> Ping can you clarifie the situation of wacom based devices ?

What else do you need me to clarify? I am all ears and I am ready to
clarify any thing that puzzles you.

Ping

> Thanks,
>
> ik.
>
> On Tue, Jun 15, 2010 at 7:01 PM, Henrik Rydberg <rydberg@euromail.se> wrote:
>>
>> g number of intelligent multi-contact and
>> multi-user devices, the need to send digested, filtered information
>> from a set of different sources within the same device is imminent.
>> This patch adds the concept of slots to the MT protocol. The slots
>> enumerate a set of identified sources, such that all MT events
> --
> 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
>
--
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:[~2010-06-20  5:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 11:20 Wacom based devices and the mt kernel protocol Mohamed Ikbel Boulabiar
2010-06-20  5:35 ` Ping Cheng [this message]
2010-06-20 19:22   ` Rafi Rubin
2010-06-21  0:31     ` Ping Cheng
2010-06-21  1:19       ` Rafi Rubin
2010-06-21  5:30         ` Ping Cheng
2010-06-21  9:09           ` Mohamed Ikbel Boulabiar

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=AANLkTikExwM_LBUw_-z2eimO96Dxs_fNfAM4jlftXyHM@mail.gmail.com \
    --to=pinglinux@gmail.com \
    --cc=boulabiar@gmail.com \
    --cc=chase.douglas@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafi@seas.upenn.edu \
    --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).