The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Ian E. Morgan" <imorgan@webcon.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ALPS tapping disabled. WHY?
Date: Thu, 24 Feb 2005 22:08:15 -0500	[thread overview]
Message-ID: <200502242208.16065.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0502241822310.8449@light.int.webcon.net>

On Thursday 24 February 2005 18:29, Ian E. Morgan wrote:
> Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
> reading several threads related to the topic, noe seemed to resolve my
> issue.
> 
> The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
> 2.6.10.
> 
> This change fixes the problem by NOT disabling hardware tapping:
> 
> --- linux-2.6.11-rc5/drivers/input/mouse/alps.c~	2005-02-24 18:16:03.000000000 -0500
> +++ linux-2.6.11-rc5/drivers/input/mouse/alps.c	2005-02-24 18:16:03.000000000 -0500
> @@ -334,8 +334,8 @@
>   	if (alps_get_status(psmouse, param))
>   		return -1;
> 
> -	if (param[0] & 0x04)
> -		alps_tap_mode(psmouse, 0);
> +//	if (param[0] & 0x04)
> +//		alps_tap_mode(psmouse, 0);
> 
>   	if (alps_absolute_mode(psmouse)) {
>   		printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
> @@ -372,11 +372,11 @@
>   		return -1;
>   	}
> 
> -	if (param[0] & 0x04) {
> -		printk(KERN_INFO "  Disabling hardware tapping\n");
> -		if (alps_tap_mode(psmouse, 0))
> -			printk(KERN_WARNING "alps.c: Failed to disable hardware tapping\n");
> -	}
> +//	if (param[0] & 0x04) {
> +//		printk(KERN_INFO "  Disabling hardware tapping\n");
> +//		if (alps_tap_mode(psmouse, 0))
> +//			printk(KERN_WARNING "alps.c: Failed to disable hardware tapping\n");
> +//	}
> 
>   	if (alps_absolute_mode(psmouse)) {
>   		printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
> 
> 
> 
> 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.

-- 
Dmitry

  reply	other threads:[~2005-02-25  3:08 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 [this message]
2005-02-27  7:50   ` Vojtech Pavlik
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=200502242208.16065.dtor_core@ameritech.net \
    --to=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