From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Peter Osterlund" <petero2@telia.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 and mice
Date: Mon, 29 Dec 2003 11:04:14 +0900 [thread overview]
Message-ID: <18cf01c3cdb0$2ab1cf20$43ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: m2pte9cgbu.fsf@telia.com
Peter Osterlund replied to me:
> > 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.
I guess that explains why the Synaptics driver didn't cause any problems
:-)
> 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.
Looking at that page, I'll guess that SuSE 8.2's version of XFree86 probably
already has that patch, because under X the touchpad is performing more than
half of those operations correctly already.
> 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.
That's OK, Alps supplies notebook vendors with drivers for Monopolysoft
OSes, and it seems that Alps hasn't completely got this working correctly
either.
next prev parent reply other threads:[~2003-12-29 2:05 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
2003-12-29 2:04 ` Norman Diamond [this message]
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='18cf01c3cdb0$2ab1cf20$43ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.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