Hi, thank you for your feedback.
I add my device config file under /etc/X11/Xorg.d.conf, then mulit-touch can work on 1.1.90.4.
And I also want multi-touch can work on 1.1.80.14, I build the handset 1.1.80.14 image with the modified qt from http://download.meego.com/live/home:/jketreno/Trunk/, which described in https://bugs.meego.com/show_bug.cgi?id=11625, not only multi-touch but also single touch can't work. Before the modification, at least single touch can work. It is so puzzled, is it?
Best Regards.
Lily Zuo 左慧莉
-----Original Message-----
From: ***@nokia.com [mailto:***@nokia.com]
Sent: Tuesday, March 08, 2011 1:43 AM
To: ***@linux.intel.com; Zuo, Huili
Cc: meego-touch-***@meego.com
Subject: RE: [MeeGo-touch-dev] touch and mulit-touch on meego
Afaik it is/was a bug in the current meego kernel (and/or mtev/evtouch-driver), dont know if its fixed yet:
https://bugs.meego.com/show_bug.cgi?id=12829
https://bugs.meego.com/show_bug.cgi?id=12777
re, Jonni
________________________________________
From: meego-touch-dev-***@meego.com [meego-touch-dev-***@meego.com] on behalf of ext James [***@linux.intel.com]
Sent: Monday, March 07, 2011 6:46 PM
To: Zuo, Huili
Cc: meego-touch-***@meego.com
Subject: Re: [MeeGo-touch-dev] touch and mulit-touch on meego
On 03/03/2011 01:52 AM, Zuo, Huili wrote:
> Hi, all
> I have a CZC tablet device. I have already port the device touch
> driver to kernel2.6.38-6.5. When this kernel working in the meego
> verison 1.1.80.14, single touch can work but multi-touch can’t
> work(someone told me there is bug in the qt, so multi-touch can’t
> work. But this bug is fixed in the 1.1.90.4). When this kernel working
> in the meego version 1.1.90.4, single touch can’t work, the only what
> I can do is to move the X cursor across the screen. There is not any
> response when click any icon.
Assuming your device correctly follows the kernel's multi-touch-protocol
(A or B) you should be able to use the xorg-x11-input-mtev driver in X
and it will work.
Problems we have seen:
1) Drivers not correctly following the kernel's protocol, especially in
regard to SYN_REPORT events (either leaving out a final SYN_MT_REPORT or
injecting SYN_REPORT between each contact point)
2) Platforms using the evdev input driver, which advertises that it
support button labels but then doesn't actually provide the labels,
which makes applications unable to map input events to appropriate
button handlers
James
> Does anyone know how to resolve this problem?
>
>
> _______________________________________________
> MeeGo-touch-dev mailing list
> MeeGo-touch-***@meego.com
> http://lists.meego.com/listinfo/meego-touch-dev
_______________________________________________
MeeGo-touch-dev mailing list
MeeGo-touch-***@meego.com
http://lists.meego.com/listinfo/meego-touch-dev