Comment 8 for bug 625511

Madbiologist, no, the fix you mentioned is for a different eGalax controler. The fix for this bug here is currently being reviewed on the linux-input mailing list (it's almost accepted, Stéphane Chatty is only waiting for some feedback whether the fix is also valid for another screen handled by the same driver).