public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: Broken synaptics mouse..
Date: Sun, 21 Sep 2003 22:42:37 +0200	[thread overview]
Message-ID: <20030921204237.GA25441@ucw.cz> (raw)
In-Reply-To: <m2pthtriqe.fsf@p4.localdomain>

On Sun, Sep 21, 2003 at 10:26:17PM +0200, Peter Osterlund wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
> 
> > On Sun, Sep 21, 2003 at 09:29:10PM +0200, Peter Osterlund wrote:
> > 
> > > One thing that it doesn't get right is the handling of invalid ABS_*
> > > values. How is this supposed to be handled? The driver doesn't know
> > > the exact limits for the X/Y values, and discarding values outside
> > > some guessed limits will only have the effect that some parts of the
> > > touchpad area becomes dead.
> > 
> > I think something like 'if the finger is lifted so much above surface
> > that X and Y are unreliable, don't report X and Y'. Is that doable?
> 
> Yes, it should be sufficient to only report X/Y when Z>0. (I thought
> invalid values referred to all values outside the limits defined by
> dev->absmin and absmax, hence my previous comment.)
> 
> Here is a new patch:
> 
>  linux-petero/drivers/input/mouse/synaptics.c |   68 +++++++++++-------
>  linux-petero/drivers/input/mousedev.c        |  100 +++++++++++++++++++--------
>  linux-petero/include/linux/input.h           |    3 
>  3 files changed, 118 insertions(+), 53 deletions(-)

Yes, this now looks very nice. Applied.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-09-21 20:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0309110744030.28410-100000@home.osdl.org>
2003-09-18 23:43 ` Broken synaptics mouse Peter Osterlund
2003-09-19  5:05   ` Dmitry Torokhov
2003-09-19 11:48   ` Vojtech Pavlik
2003-09-21 17:20     ` Peter Osterlund
2003-09-21 17:27       ` Vojtech Pavlik
2003-09-21 19:29         ` Peter Osterlund
2003-09-21 19:34           ` Vojtech Pavlik
2003-09-21 20:26             ` Peter Osterlund
2003-09-21 20:42               ` Vojtech Pavlik [this message]
2003-09-21 23:16         ` Dmitry Torokhov
2003-09-22  5:31           ` Vojtech Pavlik
2003-09-22  5:58             ` Dmitry Torokhov
2003-09-22  6:09               ` Vojtech Pavlik
2003-10-01 10:03   ` Pavel Machek
2003-10-01 15:38     ` Peter Osterlund
     [not found] <xgHm.3mL.27@gated-at.bofh.it>
     [not found] ` <xlGW.2qw.15@gated-at.bofh.it>
2003-09-19 15:39   ` Ruben Puettmann
2003-09-21 21:17 Ricardo Galli
2003-09-21 21:41 ` Peter Osterlund
  -- strict thread matches above, loose matches on Subject: below --
2003-09-21 22:15 Ricardo Galli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030921204237.GA25441@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox