Le 10 févr. 10 à 12:08, Jiri Kosina a écrit :
On Sat, 6 Feb 2010, Stephane Chatty wrote:
+ /* currently, it's better to have one evdev device only */
+#if 0
+ hdev->quirks |= HID_QUIRK_MULTI_INPUT;
+#endif
Could you please explain what is this about?
The device emits three kinds of reports. One is for multitouch
events, one is for a mouse emulation, and one is (as far as I can
remember) for a couple of buttons.
Originally I experimented using MULTI_INPUT, so that three devices
are created. It made things easier for debug, or so I thought. But
over time it appeared that people kept confusing the mouse device and
the mutitouch device and I lost three weeks trying to debug a driver
that worked perfectly well. More recently, it appeared that it also
creates confusion with hal and X.org.
Since all other mt devices have their own single touch emulation on
the same device (as discussed in a previous thread), I thought it
better to do the same here and ignore the mouse reports (through not
using MULTI_INPUT). I left it between #ifdefs in case things need to
change in the future.
St.
--
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
