Pete Zaitcev <[EMAIL PROTECTED]> writes:
> 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:
[alps touchpad detection fix patch]
> 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:
I have posted 4 patches to LKML earlier today. Some of them might fix
some of your problems.
> - 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.
It would be interesting to know at which level the problem appears.
Can you reproduce the problem using "xev"? If xev works as expected,
the problem is possibly that the left mouse button gets stuck and
stops your application from accepting keyboard input. This patch fixes
the button stuck problem:
[PATCH 1/4] Make mousedev.c report all events to user space immediately
If the keyboard gets stuck also using "xev", the problem is at a lower
level. Enable i8042_debug in drivers/input/serio/i8042.c to see if the
keyboards produces any data in the stuck state.
> - Double-click sometimes fails to work. I have to wait a second and retry it.
> Retrying right away is likely not to work again.
Probably fixed by this patch:
[PATCH 2/4] Enable hardware tapping for ALPS touchpads
> - 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 see this too when I don't use the X touchpad driver. With the X
driver there is no problem. I think the problem is that mousedev.c in
the kernel has to use integer arithmetic, so probably small movements
are rounded off to 0. I'll try to come up with a fix for this.
> P.S. I hate the tap, so keep it disabled by default, please :-)
You can disable tapping by setting the tap_time parameter for
mousedev.c to 0. The default value is 200ms.
--
Peter Osterlund - [EMAIL PROTECTED]
http://web.telia.com/~u89404340
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
