All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: John Bradford <john@grabjohn.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Linus Torvalds <torvalds@osdl.org>, Matt <dirtbird@ntlworld.com>,
	herbert@gondor.apana.org.au,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [MOUSE] Alias for /dev/psaux
Date: Sun, 9 Nov 2003 11:38:53 +0100	[thread overview]
Message-ID: <20031109103853.GA13154@ucw.cz> (raw)
In-Reply-To: <200311091033.hA9AXfKT000886@81-2-122-30.bradfords.org.uk>

On Sun, Nov 09, 2003 at 10:33:41AM +0000, John Bradford wrote:
> > XFree86 also sets the mouse to 200dpi
> 
> That's odd, I have a mouse which doesn't work correctly unless I
> specifically add an Option "Resolution" "200" line to XF86Config.

This has changed between the versions of XFree86. Older versions used a
value of 100 which is the PS/2 default. Because of mice which give
trouble when they don't get a 200, like yours, this was changed in the
recent version(s).

> Either the default isn't 200, or something else must be happening
> differently when I set the resolution manually.
> 
> Without a resolution option at all, the mouse has to be moved at a
> certain speed to register movement at all.  This has nothing to do
> with accelleration, (which I don't use).  Moving the mouse slowly, for
> any length of time, never produces any movement on-screen.  Moving it
> quickly does.  With the resolution set to 200 or above, it works as
> expected.  Lower than 200, and it exhibits the strange behavior.
> 
> The same thing happens with gpm.
> 
> (This behavior is observable with 2.4.  I haven't tested this mouse
> with the in-kernel driver in 2.6 yet).

Please test, but after you apply the patch.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-11-09 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 15:17 Re:[MOUSE] Alias for /dev/psaux Matt
2003-11-05 16:27 ` Linus Torvalds
2003-11-05 17:02   ` [MOUSE] " Vojtech Pavlik
2003-11-05 17:36     ` Linus Torvalds
2003-11-05 18:00       ` Vojtech Pavlik
2003-11-05 18:39         ` Linus Torvalds
2003-11-06 10:41         ` Mikael Pettersson
2003-11-05 17:39   ` Vojtech Pavlik
2003-11-05 17:49     ` Linus Torvalds
2003-11-05 18:03       ` Vojtech Pavlik
2003-11-09 10:04         ` Vojtech Pavlik
2003-11-09 10:33           ` John Bradford
2003-11-09 10:38             ` Vojtech Pavlik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 11:03 "Andrey Borzenkov" 
2003-11-05 10:48 Herbert Xu

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=20031109103853.GA13154@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dirtbird@ntlworld.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.