Date:	Mon, 21 Jun 2010 11:09:52 +0200
From:	Mohamed Ikbel Boulabiar <boulabiar@...il.com>
To:	Ping Cheng <pinglinux@...il.com>
Cc:	Rafi Rubin <rafi@...s.upenn.edu>,
	Henrik Rydberg <rydberg@...omail.se>,
	Chase Douglas <chase.douglas@...onical.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jiri Kosina <jkosina@...e.cz>,
	Stéphane Chatty <chatty@...c.fr>
Subject: Re: Wacom based devices and the mt kernel protocol.

On Mon, Jun 21, 2010 at 7:30 AM, Ping Cheng <pinglinux@...il.com> wrote:
> On Sun, Jun 20, 2010 at 6:19 PM, Rafi Rubin <rafi@...s.upenn.edu> wrote:
>>>
>>>>>> 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?
>>>>
>>>> I think normal users wanting to use linux for MT are generally frustrated and
>>>> confused at the moment.
>>>
>>> Why do the end users get frustrated and confused? Can you share some
>>> examples from an end user's (not developer's) perspective with me?

it would be no difference between users and developers behaviors, it
is just a matter of time, developers get frustrated some time before
normal users would be :)




>> Sorry, I've been too focused on the n-trig users.  They have been frustrated,
>> and I've seen from the forums that some have been playing with customized
>> versions of both the kernel and wacom x driver to get your two finger gestures.
>>
>> I'm also projecting my own frustrations, seeing the X mt interface still not
>> quite set, and very little in the way of applications that use mt at all.
>> We're still quite a ways away from seeing the full potential of a more hands on desktop.
>
> As far as I understand,  this issue is not device driver or MT support
> specific. It is universal  on Linux.

Maybe because not all of drivers are up-to-date to new changes happening.
The new protocol is a way to standardize the way all mt devices are handled.



>>>> Certainly the protocol between the wacom kernel driver
>>>> and the wacom user space driver is way below the level that most are following.
>>>
>>> By "most", do you mean most MT device drivers, or most end users, or
>>> most developers? I am eager to bring the Wacom driver to the specific
>>> level.
>>
>> End users, they don't tend to care about the internal protocols as long as their
>> programs do what they want.
>
> Then, I still don't get what you meant by "way below the level that
> most are following". I'd really like to understand it so I can work on
> it.

if 5 or 6 mt devices are supported in the new protocol and wacom is
not, this means a split in the support way. You've just told us the
point of how bad having different ways things are supported.




To summarize the discussion with you Ping, you will support the new
protocol as far as it will show a good reason for a switch yep ? But
what if this can make other devices look as they are better supported
in the near future with upcoming changes (even if wacom are better
technically) ?
This remembers me the days when ntrig was not supported in Linux (and
with no intention to be supported), then after the non-corporate
driver comes, they tried to publish their own.
http://www.ipetitions.com/petition/ntrig-on-linux/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists