From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Kim Holviala <kim@holviala.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] psmouse fixes for 2.6.5
Date: Tue, 20 Apr 2004 21:17:35 -0500 [thread overview]
Message-ID: <200404202117.37104.dtor_core@ameritech.net> (raw)
In-Reply-To: <200404202338.53773.kim@holviala.com>
On Tuesday 20 April 2004 03:38 pm, Kim Holviala wrote:
> On Tuesday 20 April 2004 15:59, Dmitry Torokhov wrote:
> > On Tuesday 20 April 2004 02:38 am, Kim Holviala wrote:
> > > Some fixes for PS/2 mice:
> > >
> > > - fixed hotplugging (real reset of device instead of softreset)
> > > - support for Targus Scroller mice (from my last weeks patch)
> > > - extended protocol probing fixed
> >
> > Why do you have Tragus as a config option - just set the protocol mask
> > correctly by default...
>
> Targus mice misuse the normal PS/2 protocol so that they can sneak through
> command-filtering PS/2 ports (like on my Digital HiNote 2000). Basically they
> output very strange but valid traffic when the wheel is moved. Anyway, this
> is Linux, and I'd rather force people to turn it on explicitly rather than
> take the risk of breaking some valid PS/2 device which might theoretically
> output the same stuff.
>
And I think you will achieve the desired result by just doing:
-static unsigned int psmouse_max_proto = -1U;
+static unsigned int psmouse_probe_proto = PSMOUSE_ANY & ~PSMOUSE_TARGUS;
Think about distributions, they will just have turn this option on anyway.
--
Dmitry
next prev parent reply other threads:[~2004-04-21 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 7:38 [PATCH] psmouse fixes for 2.6.5 Kim Holviala
2004-04-20 12:59 ` Dmitry Torokhov
2004-04-20 20:38 ` Kim Holviala
2004-04-21 2:17 ` Dmitry Torokhov [this message]
2004-04-21 6:48 ` Kim Holviala
2004-04-21 7:10 ` Dmitry Torokhov
2004-04-21 7:13 ` 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=200404202117.37104.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=kim@holviala.com \
--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 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.