From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Gunter Königsmann" <gunter.koenigsmann@gmx.de>,
"Gunter Königsmann" <gunter@peterpall.de>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch).
Date: Sat, 10 Jan 2004 03:44:03 -0500 [thread overview]
Message-ID: <200401100344.03758.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0401091101170.1050@calcula.uni-erlangen.de>
On Friday 09 January 2004 05:17 am, Gunter Königsmann wrote:
> Don't know if I'm supposed to the list or to the maintainer, mailing
> tho both.
>
> PROBLEM: My Touchpad generates rapid movements, random clicks and even
> keypress events on the keyboard connected to the same BUS. Resetting
> the Touchpad after bad syncs doesn't help.
>
> Throwing away two packets after a bad sync loss fixed the whole
> problem. One packet is not sufficient.
>
Hi,
As I wrote in my other email the patch as it written does not discard
2 first packets after restoring synchronization, instead it ignores every
2nd packet.
It seems that your laptop can't keep up with 480 bytes/sec data stream that
Synaptics generates in 'high' report rate mode (80 packets/sec, 6 bytes per
packet). Luckily Synaptics offers low rate mode, 40 packets/sec, and I think
you should get the same result as by your patch switching your touchpad in
that mode.
I am going to send 2 patches, one that allows switching high and low rate
for Synaptics using psmouse.rate option (>=80 sets high rate and its default
state). You should try psmouse.rate=40 (or just rate=40 if psmouse is compiled
as a module). The second patch makes psmouse check status of received byte and
drop it early if i8042 reports timeout or parity error.
The patches are on top of my other input patches, you can find all of them at
http://www.geocities.com/dt_or/input/2_6_1/
Or you can grab 2.6.1-mm1 and apply just the 2 I am sending...
I am very interested in results.
Thank you in advance,
Dmitry
next prev parent reply other threads:[~2004-01-10 8:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 10:17 Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch) Gunter Königsmann
2004-01-09 10:58 ` Vojtech Pavlik
2004-01-10 22:50 ` Peter Berg Larsen
2004-01-11 2:39 ` Peter Berg Larsen
2004-01-11 3:33 ` Dmitry Torokhov
2004-01-11 8:37 ` Gunter Königsmann
2004-01-11 12:52 ` Peter Berg Larsen
2004-01-11 14:22 ` Vojtech Pavlik
2004-01-11 15:34 ` Dmitry Torokhov
2004-01-11 15:06 ` Gunter Königsmann
2004-01-11 8:10 ` Vojtech Pavlik
2004-01-11 12:46 ` Peter Berg Larsen
2004-01-11 14:21 ` Vojtech Pavlik
2004-01-19 22:25 ` Vojtech Pavlik
2004-01-10 8:44 ` Dmitry Torokhov [this message]
2004-01-10 8:45 ` [PATCH 1/2] Synaptics rate switching Dmitry Torokhov
2004-01-10 8:46 ` [PATCH 2/2] Psmouse log and discard timed out bytes Dmitry Torokhov
2004-01-10 13:05 ` Gunter Königsmann
2004-01-10 13:23 ` Gunter Königsmann
2004-01-11 4:57 ` [PATCH 3/2] Psmouse log and discard timed out bytes - addition Dmitry Torokhov
2004-01-11 8:11 ` Gunter Königsmann
2004-01-10 9:56 ` [PATCH 1/2] Synaptics rate switching Vojtech Pavlik
2004-01-10 22:05 ` Gunter Königsmann
2004-01-10 23:37 ` Vojtech Pavlik
2004-01-11 2:20 ` Dmitry Torokhov
2004-01-11 8:00 ` Gunter Königsmann
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=200401100344.03758.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=gunter.koenigsmann@gmx.de \
--cc=gunter@peterpall.de \
--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