public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: walt <wa1ter@myrealbox.com>, linux-kernel@vger.kernel.org
Subject: Re: PS2 mouse changes for 2.6
Date: Mon, 29 Dec 2003 18:43:44 -0500	[thread overview]
Message-ID: <200312291843.44656.dtor_core@ameritech.net> (raw)
In-Reply-To: <3FF033AF.2080905@myrealbox.com>

On Monday 29 December 2003 09:01 am, walt wrote:
> I get good results from last night's PS2 mouse patches.  My one
> problem machine now works perfectly again without the psmouse_noext
> parameter I've been using for several months.
>
> Two observations:
>
> I see no deprecation warnings when starting the kernel with
> psmouse_noext, which I was expecting to see.

It is emitted with KERN_WARNING severity and is not necessary seen on
the console. Check you dmesg.
>
> The mouse is announced as a 'generic wheel mouse', but it is
> really a Kensington Orbit trackball.  Unfortunately I don't
> have a wheel mouse to test with, so I can't comment there.
>

The kernel does not really distinguish between different hardware
manufacturers. It tries to recognize Synaptics, Logitech and Genius, but
it relies on mouse responses to various PS/2 protocol probes. Anything
that responds to IntelliMouse (imps) protocol probes but does not respond
to ImtelliMouse Explorer (exps) probes gets labelled as "Generic Wheel
Mouse".

Dmitry

  reply	other threads:[~2003-12-29 23:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 14:01 PS2 mouse changes for 2.6 walt
2003-12-29 23:43 ` Dmitry Torokhov [this message]
     [not found] <fa.fl0st45.t3auq7@ifi.uio.no>
     [not found] ` <fa.jm00pl0.5nsn3g@ifi.uio.no>
2003-12-30  0:51   ` walt
2003-12-30  4:21     ` Dmitry Torokhov

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=200312291843.44656.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1ter@myrealbox.com \
    /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