multi-touch-dev team mailing list archive

[Rafi Rubin <rafi@xxxxxxxxxxxxxx>]

> I think I have a working solution. It has to do with a message starting 
> with 0x0a that I had observed the PC sending to the device without being 
> able to reproduce it correctly. Considering it as a feature report and 
> sending it as such with usbhid_submit_report seems to do the trick.
>
> I'll make a few more tests and send a patch to Rafi for further testing.

That would be consistent with one of the proposed changes Micki from ntrig 
sent in.  Though I think he described it as "enabling multi-touch" and 
"harmless" when multi-touch is already active.

Oh well.