On Fri, Jan 7, 2011 at 6:27 PM, Henrik Rydberg <rydberg@xxxxxxxxxxx> wrote: >> > But the mt_input_mapped function did not change - needs to change too. >> >> I can not see any differences between mt_input_mapped and those found >> in 3m and egalax. Can you point me exactly what I should add please? > > My bad - it seems your tree does contain the right function. Another > reason to have the patches in mail. :-) > >> >> - The Egalax problem: I am pretty sure that Stéphane took this driver >> >> into account when writing the original patch. BTW I propose to >> >> postpone the problem for 2.6.39. >> > >> > This driver is aiming at engulfing a larger set of drivers, and as >> > such, should be prepared sensibly, IMO. Rushing things will only cause >> > us grief further down the road. >> > >> >> So, have you got any clue (or even better, can you test a solution) >> for those devices? > > Yes I can, but I will not be available the coming couple of days, so > the timing is a bit off. I agree with you that we do not need to solve > every issue right now, but I know for a fact that the newer DWAV > firmware has no touch frame indication, and does not assume the > not-seen-means-up behavior. Perhaps it is enough to just add the > quirks field to the class, define one or two quirks currently in use, > and leave the rest for later. Sounds reasonable? > Sounds reasonable Cheers, Benjamin -- 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
