On Wed, Nov 16, 2011 at 07:41:04AM -0600, Chris Bagwell wrote: > And a little extra info. Cedric tested the patch that is now in > Jiri's upstream-fixes branch for this new 0xa0001 and got success so I > sent in patch. After several days, he tested closer and realized it > was getting X/Y movement and what I'll call unpredictable Touch > behaviour. It would either act like a stylus hovering but never > touching or it would always act like touching and never release. > > Events are working and you can test with evtest. I've verified at > least one test stream he emailed that it is not correctly sending > BTN_TOUCH but it is sending good X/Y using MT and pointer emulation > events. > > It would probably be easy to see the issue if debug/hid/*/events were > being displayed but for some reason "cat rdesc" outputs stuff but "cat > events" does not. I couldn't come up with more ideas remotely. > > The redesc shows it reports ContactID's range of 0-16 and features > says only 10 touches max (seen in above paste link). So my last guess > is that we may be using the wrong quirk for this one since it sounds > like ContactID is not 1-to-1 with touches. Hard to tell without > sample events though. > > Chris Chris, it might interest you that the event node now fires and outputs events, when letting hid-multitouch handle the device through Benjamin's patch (Writing "3 0eef a001 1" to new_id). I think when adding the MULTITOUCH5 in the source in the exact same manner MULTITOUCH[1-4] are added I must have copied some quirks which interfere with the event node. Now, adding the device by Benjamin's way does not load any quirks by default, so the event node works. Either Benjamin or I will tell you more once we discovered something definite. 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
