hope someone finds it helpful. The reorg'd code
kinda highlights how incomplete it is, there's lots of mouse models out there.
So if it looks good or almost-good to you and there's anything else I can do,
tell me and I'll be glad to do it.
Thanks,
Jim
>From 2681957a610191cb5
ge. No one else has tried this yet.
Signed-off-by: Jim Hill
---
This is a second version, choosier about accepting apparently-valid
start bytes, no redundant test and more concise syslog and changelog
text.
This is my first patch, I hope I got the procedures right, apologies in
advance if I g
et it to 0 to effectively disable the patch.
Tested on AMD64, full coverage - syslog is a good argument for
replacing my mouse soon, but it's quirky not intolerable.
Signed-off-by: Jim Hill
---
Hi, this is my first patch, I hope I got the procedures right, apologies in
advance if I goofed
So much for certainty. I thought rate=40 fixed the desyncs and freezing
but it's back, no more frequent, just the same as before.
The question remains what XP is doing different that the problem
doesn't occur there. I can reboot into XP and it runs fine for much
longer than it takes the proble
For my part I'm certain of it: this is a failing mouse overloading
some part of the link. The mouse now misbehaves rarely but it's
plainly my middle mouse button sizzling briefly and everything
recovers fine, no desyncs or parity errors at all after I backed off
further to rate=40.
shirish, if
I made it stop on my squeeze beta 2.6.32 with a driver parameter change
I found on the net.and played with to strip unnecessary stuff:
This-boot workaround:
$ sudo rmmod psmouse && sudo modprobe psmouse rate=80
Every-boot workaround:
$ sudo sh
# cat >> /etc/modprobe.d/psmouse.conf
6 matches
Mail list logo
