Hi, Oops, I think I assumed that the features that will come in 3.4 are already in 3.3... sorry. Once hid-multitouch is loaded, you have to manually tell him to handle your device: # echo 3 2453 0100 0 > /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id That should do the trick. If it's not working, then we may need the full report descriptors (without the ** UNAVAILABLE **). You can do that by using the script there: http://lii-enac.fr/en/architecture/linux-input/multitouch-howto.html#report Cheers, Benjamin On Fri, Apr 13, 2012 at 10:02, Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxxxxx> wrote: > On Thursday 12 Apr 2012 17:05:34 Benjamin Tissoires wrote: >> Hi Tvrtko, >> >> I misread your first mail, sorry for that. I did not saw that your >> device was a Hid one detected as a multitouch one. Under 3.3, just do: >> $ sudo modprobe hid-multitouch >> >> And the device should be handled by hid-multitouch. >> >> The 3.3 kernel, detects that your device should be handled by >> hid-multitouch, but it does not load it automatically. You may add >> this module in the configuration file. > > Unfortunately nothing interesting happened with hid-multitouch loaded. Nonew > kernel messages, no devices claimed/created. > > Are there any tools (couldn't find any) which can probe/analyze this device > from userspace? Or something that would explain why it works better with > earlier kernels? > > Tvrtko -- 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
