>> I think your patch is a good reduction, all in accord with what we talked about, >> but I have doubts that it will not create regressions. From what I have seen so >> far, patch-wise, the best solution is to leave the code as it is. > > So you believe that the current (in-tree) behavior is superior to either of my attempts thus far to fix it? That is not at all what I said. I like the result of your patch set. The question is how it works with linux in general. >> I understand that the constraints now seem to depict the empty set, but maybe >> there is a third solution. > > Can you characterize what an acceptable solution would look like? The behavior of the code as it stands is really not acceptable; the MacBook Pro touchpad's buggy behavior in Linux is extremely frustrating, relative to its flawless behavior in OS X. My patchset has not introduced any regressions that I can observe, and in fact it has nearly eliminated the spurious drags. (I still get one occasionally, but maybe at a rate of ~1% as often as I was seeing them before.) The constraints so far are: 1. Make the situation on the problematic devices better 2. Do not invent sensor data 3. Do not create regressions Taken together, it suggests that the patch should be similar, but not equal to, the original patch. Thanks, Henrik -- 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
