From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Henrik Rydberg" Subject: Re: [RFC v2 03/10] hid-multitouch: support for PixCir-based panels Date: Fri, 7 Jan 2011 18:27:07 +0100 Message-ID: <20110107172707.GA6095@polaris.bitmath.org> References: <1294248468-19979-1-git-send-email-benjamin.tissoires@enac.fr> <1294248468-19979-4-git-send-email-benjamin.tissoires@enac.fr> <20110106172528.GD1790@polaris.bitmath.org> <20110107122338.GB2312@polaris.bitmath.org> <20110107155714.GA506@polaris.bitmath.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212]:46698 "EHLO ch-smtp01.sth.basefarm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754447Ab1AGR2d (ORCPT ); Fri, 7 Jan 2011 12:28:33 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Benjamin Tissoires Cc: Stephane Chatty , Dmitry Torokhov , Jiri Kosina , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org > > But the mt_input_mapped function did not change - needs to change t= oo. >=20 > 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=E9phane took this d= river > >> 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 ca= use > > us grief further down the road. > > >=20 > 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? Thanks, Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html