Thanks Hendrik for your help. I will use this application as a testbed for verifying events for multi-touch kernel modules. Would you happen to know the appropriate way to download the source for this? I tried both cloning it's git repository and also tried clicking on the URL but unfortunately I was unable to gain access. >If you do find an error higher up the stack, providing a test case using the utouch-evemu project is very valuable, since it allows the hardware and the exact situation to be emulated and explicitly tested on any machine. That sounds like a nice tool. If I can reproduce using this issue using emulated events, I'll submit a case. Best regards, Steve Grahovac Sr. Software Engineer Microchip Technology, Inc. 9055 N. 51st Street Suite H Brown Deer, WI 53223 USA Steve.Grahovac@xxxxxxxxxxxxx Ph: 414.355.4675 FX: 414.355.4775 -----Original Message----- From: Henrik Rydberg [mailto:rydberg@xxxxxxxxxxx] Sent: Thursday, December 02, 2010 3:55 AM To: Dmitry Torokhov Cc: Steve Grahovac - C13916; Linux Input Subject: Re: Microchip Touchscreen Driver Submissions > >> I verified the multi-touch was being reported >> correctly by use of the pymt python multi-touch draw application. For >> touchscreen emulation, I did notice an issue where touch events seemed >> to be properly sent as evdev packets by the mchppcapmt kernel module, >> however Xorg 7.5 did not process these touch events correctly since the >> cursor moved but there were no click events (I'm guessing this is an >> Xorg issue, but not 100 percent sure). Are you familiar with any >> multi-touch touchscreen emulation issues with Xorg? > > Multitouch support is work in progress on all levels of our stack, I > think Henrik is in a better position to answer this question. There are a number of things that can go wrong, anywhere from the kernel driver, whether mtdev is used or not (latest pymt has mtdev support), which X driver is in use, and what distro is being used. For driver tests, the mtview program (http://bitmath.org/code/mtview/) has been used successfully during development of some drivers, since it does not depend on the higher levels of the stack. Combined with evtest, it is usually possible to find the point-and-click problems. If you do find an error higher up the stack, providing a test case using the utouch-evemu project is very valuable, since it allows the hardware and the exact situation to be emulated and explicitly tested on any machine. Thanks, Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
