linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>, 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: Wed, 5 Nov 2003 19:03:21 +0100	[thread overview]
Message-ID: <20031105180321.GC27922@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0311050942461.11208-100000@home.osdl.org>

On Wed, Nov 05, 2003 at 09:49:42AM -0800, Linus Torvalds wrote:

> On Wed, 5 Nov 2003, Vojtech Pavlik wrote:
> > 
> > We could save the bootup mouse settings (the mouse will tell us) and
> > restore them after we go trough all the probing if desired.
> 
> That sounds like a good idea. At least for the mice that we didn't 
> recognize, that otherwise get basically "random" commands.
> 
> How about something like this:
> 
>  - if "mouse_noext" is set (which implies that we won't be doing any 
>    probing), we also don't set rate/precision unless the user asked us.
> 
>    Thus "psmouse_noext" becomes the "ultra-safe" setting. We still want to 
>    have some way to set things like wheel etc info by hand later on (ie as
>    a response to the user _telling_ us what mouse it is), but that's a
>    more long-range plan.
> 
>  - if we do probing, we first ask the mouse for its current details, and 
>    we restore the thing by default afterwards. That at least should give 
>    us 2.4.x behaviour unless the mouse is broken (and for broken mice 
>    you'd just have to have "mouse_noext").
> 
>    Again, long-term we'd want to have the possibility of tweaking the 
>    results later even with the autodetection.
> 
> Does that sound like a reasonable plan?

Yes, it does.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-11-05 18:04 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 [this message]
2003-11-09 10:04         ` Vojtech Pavlik
2003-11-09 10:33           ` John Bradford
2003-11-09 10:38             ` Vojtech Pavlik
  -- 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=20031105180321.GC27922@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dirtbird@ntlworld.com \
    --cc=herbert@gondor.apana.org.au \
    --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 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).