From: "Alexander E. Patrakov" <[email protected]>
---
src/evdev-touchpad.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/src/evdev-touchpad.c b/src/evdev-touchpad.c
index 53de1e7..e36c2aa 100644
--- a/src/evdev-touchpad.c
+++ b/src/evdev-touchpad.c
@@ -193,7 +193,31 @@ configure_interaction_model(struct touchpad_dispatch
*touchpad)
case TOUCHPAD_MODEL_APPLETOUCH:
touchpad->interaction_model = INTERACTION_MODEL_APPLE;
break;
+ case TOUCHPAD_MODEL_SYNAPTICS:
+ case TOUCHPAD_MODEL_ELANTECH:
+ case TOUCHPAD_MODEL_ALPS:
+ /*
+ * FIXME: fallback to INTERACTION_MODEL_SIMPLE if out
+ * requirements such as multitouch support or pressure
+ * readings are not met.
+ */
+ touchpad->interaction_model = INTERACTION_MODEL_SONY;
+ break;
default:
+ /* Note: Chromebook Pixel also gets here because of the
following:
+ * I: Bus=0018 Vendor=0000 Product=0000 Version=0000
+ * N: Name="Atmel maXTouch Touchpad"
+ * P: Phys=i2c-1-004b/input0
+ * S:
Sysfs=/devices/pci0000:00/0000:00:02.0/i2c-1/1-004b/input/input9
+ * U: Uniq=
+ * H: Handlers=mouse1 event9
+ * B: PROP=5
+ * B: EV=b
+ * B: KEY=e520 10000 0 0 0 0
+ * B: ABS=661800001000003
+ *
+ * Actually, Apple-style interaction is appropriate for
Chromebooks.
+ */
weston_log("Found a buttonpad of unknown type, assuming
Apple-style\n");
touchpad->interaction_model = INTERACTION_MODEL_APPLE;
break;
--
1.8.3.2
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
