On Wed, Nov 16, 2011 at 9:40 AM, Cedric Sodhi <manday@xxxxxxx> wrote: > Thanks to Benjamin's help and his neat patch which allows tempering with > quirks through sysfs, I got the device > > eGalax 0eef:a001 > > to work. It works with the quirks > > MT_QUIRK_SLOT_IS_CONTACTID | MT_QUIRK_ALWAYS_VALID ( = 18 ) > > so, using Benjamin's interface: > > (1) Adding the device with > $ cd '/sys/modules/hid_multitouch/driver/hid:hid-multitouch' > $ echo "3 0eef a001 1" > new_id > > (2) Setting the quirks with > $ echo 18 > '0003:0EEF:A001.0001/quirks' > > That's it. The device works! Benjamin, do you have a take away from this? We are setting quirks to 0x62 which should same as 0x12 for most purposes. Combine this with the Acer eGalax patch and my guess is its .maxcontacts = 2 thats hurting things? If so, do you have enough report descriptors to know if we can remove it for all or if we need to create an MT_CLS_EGALAX_HAS_MAXCONTACTS? My guess is for the ones that have correct MAXCONTACTS, they also have valid logical X/Y sizes and so we can remote that quirk as well. At least this one does. Chris > > regards, > Cedric > -- 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
