public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: Touchpad problems with 2.6.11-rc2
Date: Sun, 23 Jan 2005 19:01:09 -0800	[thread overview]
Message-ID: <20050123190109.3d082021@localhost.localdomain> (raw)

Hi, Vojtech:

Since the 2.6.11-rc2, I encounter problems with touchpad and keyboard 
on my laptop, Dell Lattitude D600. The following patch appears to be
the culprit:

diff -urp -X dontdiff linux-2.6.11-rc1/drivers/input/mouse/psmouse-base.c linux-2.6.11-rc2/drivers/input/mouse/psmouse-base.c
--- linux-2.6.11-rc1/drivers/input/mouse/psmouse-base.c	2005-01-12 16:20:42.000000000 -0800
+++ linux-2.6.11-rc2/drivers/input/mouse/psmouse-base.c	2005-01-22 14:54:14.000000000 -0800
@@ -451,14 +451,16 @@ static int psmouse_extensions(struct psm
 /*
  * Try ALPS TouchPad
  */
-	if (max_proto > PSMOUSE_IMEX && alps_detect(psmouse, set_properties) == 0) {
-		if (!set_properties || alps_init(psmouse) == 0)
-			return PSMOUSE_ALPS;
-
+	if (max_proto > PSMOUSE_IMEX) {
+		ps2_command(&psmouse->ps2dev, NULL, PSMOUSE_CMD_RESET_DIS);
+		if (alps_detect(psmouse, set_properties) == 0) {
+			if (!set_properties || alps_init(psmouse) == 0)
+				return PSMOUSE_ALPS;
 /*
  * Init failed, try basic relative protocols
  */
-		max_proto = PSMOUSE_IMEX;
+			max_proto = PSMOUSE_IMEX;
+		}
 	}
 
 	if (max_proto > PSMOUSE_IMEX && genius_detect(psmouse, set_properties) == 0)

Without the patch, touchpad is not detected as such. Instead, dmesg shows:

input: PS/2 Generic Mouse on isa0060/serio1

With this patch, I see this:

ALPS Touchpad (Dualpoint) detected
  Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1

Looks like detection is correct, however either ALPS specific code doesn't work
right, or it sets wrong parameters, I cannot tell. Here's the list of problems,
from worst to least annoying:

- Very often, keyboard stops working after a click. Typing anything has no effect.
  However, any smallest pointer movement will restore keyboard, and then an
  application receives all buffered characters. This is very bad.

- Double-click sometimes fails to work. I have to wait a second and retry it.
  Retrying right away is likely not to work again.

- Slow motion of finger produces no motion, then a jump. So, it's very hard to
  target smaller UI elements and some web links.

I do not use the nipple, so I cannot tell if that one works or worked before.

Not everything is bad. For example, old input code (in 2.6.10) sometimes "warped"
mouse to the bottom of the screen, or confused motion with clicks. This problem
appears to be gone now. It would be just great if you could look into keyboard
stoppages, too.

Have a great day,
-- Pete

P.S. I hate the tap, so keep it disabled by default, please :-)

             reply	other threads:[~2005-01-24  3:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24  3:01 Pete Zaitcev [this message]
2005-01-30 11:10 ` Touchpad problems with 2.6.11-rc2 Peter Osterlund
2005-01-31 23:15   ` Pete Zaitcev
2005-02-01  3:40     ` Dmitry Torokhov
2005-02-01  5:06       ` Pete Zaitcev
2005-02-01  5:14         ` Dmitry Torokhov
2005-02-03 11:18           ` Giuseppe Bilotta
2005-02-02  7:41   ` Pete Zaitcev
2005-02-02 10:20     ` Vojtech Pavlik
2005-02-02 15:51       ` Dmitry Torokhov
2005-02-02 15:57         ` Vojtech Pavlik
2005-02-02 16:56       ` Pete Zaitcev
2005-02-02 17:07         ` Vojtech Pavlik
2005-02-02 17:58           ` Pete Zaitcev
2005-02-02 19:11             ` Vojtech Pavlik
2005-02-02 19:39               ` Pete Zaitcev
2005-02-02 19:55                 ` Vojtech Pavlik
2005-02-02 19:39             ` Dmitry Torokhov
2005-02-03  8:30             ` Alexandre Oliva
2005-02-03  8:49               ` Vojtech Pavlik
2005-02-03 15:17                 ` Alexandre Oliva
2005-02-03 15:28                   ` Dmitry Torokhov
2005-02-03 15:45                     ` Vojtech Pavlik
2005-02-02 20:57     ` Peter Osterlund
2005-02-02 21:17       ` Dmitry Torokhov
2005-02-02 21:47         ` Peter Osterlund
2005-02-02 22:06           ` Dmitry Torokhov
2005-02-02 22:27             ` Peter Osterlund
2005-02-03  7:16               ` Dmitry Torokhov
2005-02-02 21:37       ` David Ford
2005-02-02 22:11       ` Pete Zaitcev
2005-02-02 22:58         ` Peter Osterlund
2005-02-03  6:46           ` Vojtech Pavlik
2005-02-03 21:54             ` Peter Osterlund
2005-02-04  6:17               ` Vojtech Pavlik
2005-02-04  6:40                 ` Peter Osterlund
2005-02-04  6:53                   ` Vojtech Pavlik
2005-02-04  7:33                     ` Peter Osterlund
2005-02-04 13:25                   ` Vojtech Pavlik
2005-02-04 13:23               ` Vojtech Pavlik
2005-02-03  6:59           ` Pete Zaitcev
  -- strict thread matches above, loose matches on Subject: below --
2005-01-25 19:55 David Brownell
2005-01-25 21:30 ` Dmitry Torokhov
2005-01-30 11:20   ` Peter Osterlund
2005-01-30 20:59     ` David Brownell
2005-01-31 21:46   ` Pete Zaitcev
2005-01-31 22:00     ` Dmitry Torokhov
2005-02-08 10:55 Stephane Raimbault
2005-02-08 17:05 ` Peter Osterlund
2005-02-09  8:47   ` Stephane Raimbault
2005-02-09 18:09     ` Peter Osterlund
2005-02-10  8:32       ` Stephane Raimbault

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=20050123190109.3d082021@localhost.localdomain \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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