From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Micha Feigin <michf@post.tau.ac.il>
Subject: Re: 2.6.9-rc2-mm4 + alps locks input in X (alps not identifying correctly)
Date: Tue, 28 Sep 2004 01:23:50 -0500 [thread overview]
Message-ID: <200409280123.50804.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040928034622.GA3158@luna.mooo.com>
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
prev parent reply other threads:[~2004-09-28 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 19:27 2.6.9-rc2-mm4 + alps locks input in X Micha Feigin
2004-09-27 19:04 ` James Oakley
2004-09-27 20:25 ` Peter Osterlund
2004-09-28 3:46 ` 2.6.9-rc2-mm4 + alps locks input in X (alps not identifying correctly) Micha Feigin
2004-09-28 6:23 ` Dmitry Torokhov [this message]
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=200409280123.50804.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michf@post.tau.ac.il \
/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.