Le 28 sept. 10 à 20:24, Henrik Rydberg a écrit :
+ return 1;
+ case HID_DG_CONTACTID:
+ hid_map_usage(hi, usage, bit, max,
+ EV_ABS, ABS_MT_TRACKING_ID);
This usage of ABS_MT_TRACKING_ID is not ideal. The HID contact id
normally maps
to a slot number, which suggests the MT slots protocol be used
instead.
I'm working on a slot-based version of the Stantum driver, and have
had a look into this. The Stantum firmware actually cycles over 8-bit
values for its ContactID. In this, it conforms more to the definition
you gave for ABS_MT_TRACKING_ID ("The slot protocol requires the use
of the ABS_MT_TRACKING_ID, either provided by the hardware or
computed from the raw data [5]") than to a slot number, doesn't it?
Nevertheless, given our recent exchanges about the 3M driver, I
planned to use the driver's own tracking ID.
Your thoughts?
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
