From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: vojtech@suse.cz, alan@lxorguk.ukuu.org.uk, axboe@suse.de,
davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: PS2 mouse going nuts during cdparanoia session.
Date: Thu, 17 Jul 2003 04:03:24 +0200 [thread overview]
Message-ID: <20030717020324.GA1685@finwe.eu.org> (raw)
In-Reply-To: <200307162343.h6GNh5iu016584@harpo.it.uu.se>
Mikael Pettersson wrote:
> >This is basically because the check for lost bytes wasn't present in
> >2.4. Now that it is there, it works well with real lost bytes, but will
> >fire also in case when the mouse interrupt was delayed for more than
> >half a second, or if indeed a mouse interrupt gets lost. The 2.5 kernel
> >by default programs the mouse to high speed reporting (up to 200 updates
> >per second). This may, possibly make the problem show up easier.
> This was interesting: 2.5 programs the mouse differently than 2.4.
> I've been having ps2 mouse problems with the 2.5 input layer,
> including having to move the mouse much further for a given
> cursor movement, and a general jerky/unstable feeling of the mouse.
Strange. Here I've got problems with my mouse being actually 'to fast'
(when working with X-Window; I had to slow it down about 2 times via
xset to be able to work 'normally'; Actually -since I could not find
any related bugreports or complains - I thought it was something with
how my version of X works with new layer)
> 2.4's pc_keyb.c has (disabled by default) init code which puts the
> mouse in 100 samples/s and 2:1 scaling, whereas 2.5 puts it into
> 200 samples/s and 1:1 scaling. So I hacked psmouse-base.c to mimic
> 2.4, and VOILA! now my mouse feels A LOT better.
And here it goes even faster than before.
Live is indeed full of suprises :)
[cut]
jk
--
Jacek Kawa
next prev parent reply other threads:[~2003-07-17 1:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 23:43 PS2 mouse going nuts during cdparanoia session Mikael Pettersson
2003-07-17 2:03 ` Jacek Kawa [this message]
2003-07-17 21:44 ` Jacek Kawa
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 16:57 Dave Jones
2003-07-16 17:03 ` Jens Axboe
2003-07-16 17:09 ` Dave Jones
2003-07-16 17:13 ` Jens Axboe
2003-07-16 17:20 ` Dave Jones
2003-07-16 17:24 ` Jens Axboe
2003-07-16 17:21 ` Markus Plail
2003-07-16 17:10 ` Alan Cox
2003-07-16 17:16 ` Jens Axboe
2003-07-16 17:23 ` Dave Jones
2003-07-16 17:25 ` Jens Axboe
2003-07-16 17:28 ` Dave Jones
2003-07-16 17:31 ` Jens Axboe
2003-07-16 18:22 ` Alan Cox
2003-07-16 19:03 ` Kristofer T. Karas
2003-07-16 19:13 ` Valdis.Kletnieks
2003-07-16 19:00 ` Vojtech Pavlik
2003-07-16 19:30 ` Dave Jones
2003-07-16 20:53 ` Vojtech Pavlik
2003-07-16 23:31 ` Dave Jones
2003-07-16 23:47 ` Vojtech Pavlik
2003-07-17 11:15 ` Alan Cox
2003-07-17 17:08 ` Dave Jones
2003-07-16 18:00 ` Andrew Morton
2003-07-16 18:56 ` Vojtech Pavlik
2003-07-16 21:05 ` Andries Brouwer
2003-07-16 17:10 ` Valdis.Kletnieks
2003-07-16 17:17 ` Jens Axboe
2003-07-16 17:55 ` Dave Jones
2003-07-16 17:57 ` Jens Axboe
[not found] ` <1058422511.1164.1440.camel@workshop.saharacpt.lan>
2003-07-17 12:39 ` Dave Jones
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=20030717020324.GA1685@finwe.eu.org \
--to=jfk@zeus.polsl.gliwice.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).