From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [PATCH] input: mt: Interface and MT_TOOL documentation updates Date: Fri, 10 Dec 2010 10:50:42 -0800 Message-ID: <20101210185041.GC1630@core.coreip.homeip.net> References: <1291929732-5989-1-git-send-email-rydberg@euromail.se> <20101210181306.GB1630@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20101210181306.GB1630@core.coreip.homeip.net> Sender: linux-kernel-owner@vger.kernel.org To: Ping Cheng Cc: Henrik Rydberg , Jiri Kosina , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-input@vger.kernel.org On Fri, Dec 10, 2010 at 10:13:06AM -0800, Dmitry Torokhov wrote: > On Fri, Dec 10, 2010 at 09:55:12AM -0800, Ping Cheng wrote: > > On Thu, Dec 9, 2010 at 1:22 PM, Henrik Rydberg wrote: > > > + > > > +- The MT_TOOL_ENVELOPE type is used to indicate that the contact position > > > +is not well-defined, and is only used for legacy hardware. The real contact > > > +positions are to be found within the bounding rectangle formed by the > > > +envelope contact positions. > > > > Can we make MT_TOOL_ENVELOPE cover a bit more cases by: > > > > 1. Removing ", and is only used for legacy hardware"; > > 2. Adding "Or the number of contacts inside the bounding rectangle is > > reported if hardware provides the number but not the real contact > > positions" to the end of the paragraph. > > Are you saying that there is upcoming hardware models that do not report > individual contacts? > Anyway, if we plot the evolution of hardware: ST -> ST + #fingers -> Envelope -> Full MT I think we can rigthfully say that at this time all hardware that is not full MT is legacy technology... -- Dmitry