From: Peter Osterlund <petero2@telia.com>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 and mice
Date: 28 Dec 2003 12:49:41 +0100 [thread overview]
Message-ID: <m2pte9cgbu.fsf@telia.com> (raw)
In-Reply-To: <173901c3cceb$02d68560$43ee4ca5@DIAMONDLX60>
"Norman Diamond" <ndiamond@wta.att.ne.jp> writes:
> On a machine with an Alps touchpad, I have built 2.6.0 several times.
...
> 2. Also in Input device support, there is a section on Mice, PS/2 mouse,
> and Synaptics TouchPad. These I compiled in and they don't seem to be
> causing any problems. It seems that the Alps TouchPad is being recognized
> as an Intelli/Wheel mouse instead of being recognized as a Synaptics
> TouchPad, which is unfortunate but not really causing any problems. I've
> read that Synaptics is most common in foreign countries but Alps is most
> common in Japan.
The synaptics kernel driver doesn't try to recognize alps touchpads.
However, in the XFree86 driver
http://w1.894.telia.com/~u89404340/touchpad/index.html
there is a kernel patch (alps.patch) that makes the kernel recognize
alps touchpads and generate data compatible with the XFree86 synaptics
driver.
It doesn't work perfectly though, at least not for some hardware. The
problem seems to be how to interpret the gesture bit in the alps mouse
packets. Unfortunately I can't debug this problem myself, because I
don't have the hardware and there doesn't seem to be any public
documentation available for alps touchpads.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2003-12-28 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 2:31 2.6.0 and mice Norman Diamond
2003-12-28 11:49 ` Peter Osterlund [this message]
2003-12-29 2:04 ` Norman Diamond
2003-12-29 15:17 ` Larry Sendlosky
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=m2pte9cgbu.fsf@telia.com \
--to=petero2@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/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