From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Micha Feigin <michf@post.tau.ac.il>,
Peter Osterlund <petero2@telia.com>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [BUG: 2.6.9-rc2-bk11] input completely dead in X
Date: Tue, 28 Sep 2004 01:26:19 -0500 [thread overview]
Message-ID: <200409280126.19919.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040927145223.GA3117@luna.mooo.com>
Resending as I forgot to CC Vojtech and Peter first time around...
On Monday 27 September 2004 10:46 pm, Micha Feigin wrote:
> > Or better yet, use the auto-dev feature, which should work if you have
> > a new enough X driver and kernel patch.
> >
>
> auto-dev doesn't work for me and I don't have time to check it
> out.
Addition of Kensington ThinkingMouse / ExpertMouse support caused Synaptics
and ALPS protocol numbers to move to 8 and 9 respectively which broke Peter's
auto-dev detection.
Vojtech, we need to keep protcol numbers stable, I propose something like this:
enum psmouse_type {
PSMOUSE_PS2 = 0,
PSMOUSE_PS2PP,
PSMOUSE_THINKPS,
PSMOUSE_GENPS = 64, /* 4 byte protocol start */
PSMOUSE_IMPS,
PSMOUSE_IMEX,
PSMOUSE_SYNAPTICS = 128, /* 5+ byte protocols start */
PSMOUSE_ALPS,
};
Peter, if we adopt the scheme above you will have to check both for old and
new protocol numbers; in addition you need to BTN_TOOL_FINGER device bit to
make sure you are dealing with a touchpad.
Any holes here?
--
Dmitry
next prev parent reply other threads:[~2004-09-28 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 21:04 [BUG: 2.6.9-rc2-bk11] input completely dead in X Micha Feigin
2004-09-26 21:00 ` Tonnerre
2004-09-27 12:43 ` Micha Feigin
2004-09-27 12:48 ` Alan Cox
2004-09-27 14:52 ` Micha Feigin
2004-09-28 6:26 ` Dmitry Torokhov [this message]
2004-09-28 7:01 ` Vojtech Pavlik
2004-09-28 7:19 ` Dmitry Torokhov
2004-09-28 11:06 ` Vojtech Pavlik
2004-09-28 13:08 ` 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=200409280126.19919.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michf@post.tau.ac.il \
--cc=petero2@telia.com \
--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