From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: "Ian E. Morgan" <imorgan@webcon.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ALPS tapping disabled. WHY?
Date: Sun, 27 Feb 2005 08:50:41 +0100 [thread overview]
Message-ID: <20050227075041.GA1722@ucw.cz> (raw)
In-Reply-To: <200502242208.16065.dtor_core@ameritech.net>
On Thu, Feb 24, 2005 at 10:08:15PM -0500, Dmitry Torokhov wrote:
> > So now, can anyone explain what bit 3 of param[0] does, and why you would
> > want to disable hardware tapping support when it's set? My pad (ALPS
> > 56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
> > plain PS/2 mouse, no special ALPS support req'd.
> >
> > Can this disabling of hardware tapping support be made optional (boot time
> > param or other)? I don't want to have to patch every kernel from here on
> > out.
> >
>
> It still should do software tap emulation (although support is a bit flakey
> with ALPS I must admit, but there are patches that should improve it) - so
> people who don't like tapping can deactivate it.
>
> Anyway, "psmouse.proto=exps" boot option should disable ALPS native mode and
> restore previous behavior.
Also, in my tree currently (and planned for 2.6.12) hardware tapping is
enabled again, because double taps don't work otherwise (hardware
limitation).
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-02-27 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:29 ALPS tapping disabled. WHY? Ian E. Morgan
2005-02-25 3:08 ` Dmitry Torokhov
2005-02-27 7:50 ` Vojtech Pavlik [this message]
2005-02-28 22:23 ` Ian E. Morgan
2005-03-01 11:40 ` David Ford
2005-03-01 11:54 ` Vojtech Pavlik
2005-03-04 21:02 ` New ALPS code in -mm Benoit Boissinot
2005-03-04 21:13 ` Vojtech Pavlik
2005-03-07 7:14 ` Daniel Barkalow
2005-03-07 7:30 ` Vojtech Pavlik
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=20050227075041.GA1722@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=imorgan@webcon.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox