public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: 4Front Technologies <dev@opensound.com>,
	linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: mouse driver bug in 2.6.0-test7?
Date: Tue, 14 Oct 2003 21:38:47 +0200	[thread overview]
Message-ID: <20031014193847.GA9112@ucw.cz> (raw)
In-Reply-To: <1066159113.12171.4.camel@tux.rsn.bth.se>

On Tue, Oct 14, 2003 at 09:18:34PM +0200, Martin Josefsson wrote:
> On Tue, 2003-10-14 at 20:04, 4Front Technologies wrote:
> > Why is the PS2 mouse tracking about 2x faster in 2.6.0-test7 compared
> > to 2.4.xx?. Has anybody else seen this problem?.
> > 
> > If I move the mouse 1 inch horizontally left-to-right on the mouse
> > pad, the cursor on the screen moves almost twice the distance on the
> > screen compared to Linux 2.4.xx
> 
> It's probably mostly because Vojtech changed the samplerate from 200 to
> 60. Here's a patch to change it back. I've sent it to Vojtech but he's
> completely ignored it so far. This patch also readds the fallback logic
> that was used before his change, although it uses the new
> samplerate-table.
> 
> Without this patch my mouse is awful to use.
> Vojtech, please consider this patch, at least say yay or nay.

Patch considered. I'll up the samplerate default to 80, but not more,
since samplerates above that cause trouble for a lot of people (keyboard
doesn't work when you're moving the mouse).

The "set lower rate in case ..." part of the patch doesn't make sense.
If the user gives a too low (less than 10) samples per second, then the
original code will try to set 0, which is stupid, but harmless. The
added code will try to access beyond the bounds of the rates[] array.

> --- linux-2.6.0-test6-mm4/drivers/input/mouse/psmouse-base.c.orig	2003-10-05 17:02:23.000000000 +0200
> +++ linux-2.6.0-test6-mm4/drivers/input/mouse/psmouse-base.c	2003-10-05 17:06:55.000000000 +0200
> @@ -40,7 +40,7 @@
>  
>  static int psmouse_noext;
>  int psmouse_resolution;
> -unsigned int psmouse_rate = 60;
> +unsigned int psmouse_rate = 200;
>  int psmouse_smartscroll = PSMOUSE_LOGITECH_SMARTSCROLL;
>  unsigned int psmouse_resetafter;
>  
> @@ -450,6 +450,11 @@
>  	int i = 0;
>  
>  	while (rates[i] > psmouse_rate) i++;
> +
> +	/* set lower rate in case requested rate fails */
> +	if (rates[i])
> +		psmouse_command(psmouse, rates + i + 1, PSMOUSE_CMD_SETRATE);
> +
>  	psmouse_command(psmouse, rates + i, PSMOUSE_CMD_SETRATE);
>  }
>  
> 
> -- 
> /Martin



-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-10-14 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 18:04 mouse driver bug in 2.6.0-test7? 4Front Technologies
2003-10-14 19:18 ` Martin Josefsson
2003-10-14 19:38   ` Vojtech Pavlik [this message]
2003-10-14 20:04     ` 4Front Technologies
2003-10-14 20:13       ` Vojtech Pavlik
2003-10-14 20:27         ` Martin Josefsson
2003-10-14 20:47           ` Mika Penttilä
2003-10-14 20:59         ` 4Front Technologies
2003-10-15  0:48         ` Eric Wong
2003-10-15  6:45           ` Vojtech Pavlik

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=20031014193847.GA9112@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dev@opensound.com \
    --cc=gandalf@wlug.westbo.se \
    --cc=linux-kernel@vger.kernel.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