Hi anonymous (am I the only one who has a hard time finding who has written messages sent to this list?)
A few of these fields are necessary only. We have working code (but not clean enough yet to be submitted) that detects multitouch devices so as to use hid-multitouch automatically, and we rely on a sentence in a Win7 document that says in essence that '0x51 means multitouch'. Of course, to be any useful at all the device needs to report X and Y too :-) We also usually rely on TipSwitch. You can get the information from the device by using 'lsusb -v', but only after telling usbhid to stop grabbing the device (otherwise you are not allowed to query the report descriptors and you get an *UNAVAILABLE* message). There's a script for this in a howto on our web site (http://lii-enac.fr/en/architecture/linux-input/multitouch-howto.html). (Benjamin, correct me if I'm any wrong, I'm talking from my memories). Cheers, St. Le 29 avr. 2011 à 13:08, multi-touch-dev-bounces+chatty=enac...@lists.launchpad.net a écrit : > Hi, list, > > From archive of this ML, I found Henrik Rydberg had mentioned (as answer to > someone's question): > > ===quote=== > > Where is the correct place in kernel for the multi-touch input support? > > It depends on your device. If it supports win7 HID extensions for > digitizers, adding it to hid-multitouch makes sense. If it is a HID > device but it does not quite fit, then it is a new hid driver (which > is really discouraged at this point). If it is general usb, > then somewhere under drivers/input - there are MT drivers in touchscreen, > tablet and mouse. > > ===end of quote === > > 1 So here for multitouch, "win 7 HID extensions" is exactly pointing to the > below 8 usages supporting? > 0x47 Touch valid > 0x48 Width > 0x49 Height > 0x51 Contact identifier > 0x52 Device mode > 0x53 Device identifier > 0x54 Contact count > 0x55 Contact count maximum > > 2 For letting hid-mutitouch.c support one device, this device must support > all above 8 usages or just few of them, say 0x47/0x51/0x54 are enough? > 3 And how can one know if his device is "win 7 HID extensions" by simple way, > say 'lsusb -v'? > > Thanks for your time and feedback. > _______________________________________________ > Mailing list: https://launchpad.net/~multi-touch-dev > Post to : multi-touch-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~multi-touch-dev > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~multi-touch-dev Post to : multi-touch-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~multi-touch-dev More help : https://help.launchpad.net/ListHelp
