[Wayland-bugs] [Bug 54428] New: Multitouch touch screen is detected as a pointer device by evdev_configure_device()
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Sep 3 02:59:54 PDT 2012
https://bugs.freedesktop.org/show_bug.cgi?id=54428
Bug #: 54428
Summary: Multitouch touch screen is detected as a pointer
device by evdev_configure_device()
Classification: Unclassified
Product: Wayland
Version: unspecified
Platform: ARM
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: weston
AssignedTo: wayland-bugs at lists.freedesktop.org
ReportedBy: abhijitpotnis at gmail.com
CC: ppaalanen at gmail.com
Created attachment 66535
--> https://bugs.freedesktop.org/attachment.cgi?id=66535
evtest run dump.
Hello,
I use a eGalax Multitouch Screen. When running weston, the screen is detected
as a pointer device. The ABS_MT event packets are hence ignored as
evdev_process_absolute_motion() as it only listens to ABS_ event packets. When
eGalax is forcefully set to be a MT touch device by overriding the "if" loop in
evdev.c (ref, below), the touch works fine. In my case that ABS_MT_SLOT is not
set, is that a device driver issue ? or are we doing something different in
evdev.c ?
Should we be checking for SYN_MT_REPORT bit for devices handling anonymous
contacts and not just ABS_MT_SLOT?
static int
evdev_configure_device(struct evdev_device *device){
...
if (TEST_BIT(abs_bits, ABS_MT_SLOT)) {
..
}
wayland: commit c855d6eec4c5e63489da5bc08451a2376e6d2aea
weston : commit 5418a904ca007a109f6af8c0c75ca97a134986d9
Weston Log
[01:04:32.578] input device eGalax Touch Screen, /dev/input/event1 is a pointer
[01:04:32.578] Creating evdev device on '/dev/input/event1'.
Attached along is the evtest dump for eGalax touch screen
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Wayland-bugs
mailing list