mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Waeckerlin <Marc.Waeckerlin@siemens.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: laflipas@telefonica.net, linux-kernel@vger.kernel.org,
	t.hirsch@web.de, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Continue: psmouse.c - synaptics touchpad driver sync problem
Date: Tue, 6 Jul 2004 09:27:43 +0200	[thread overview]
Message-ID: <200407060927.43588.Marc.Waeckerlin@siemens.com> (raw)
In-Reply-To: <200407010804.00438.dtor_core@ameritech.net>

Am Donnerstag, 1. Juli 2004 15.03 schrieb Dmitry Torokhov unter "Re: Continue: 
psmouse.c - synaptics touchpad driver sync problem":
> Just out of curiosity, what happens when you pass psmouse.proto=bare to the
> kernel as a boot option (or put "options psmouse proto=bare" in your
> /etc/modprobe.conf file if psmouse is compiled as a module)?    

I tested again with psmouse.proto=bare and psmouse.resetafter=3 and *internal* 
touchpad/keyboard *only*. Last time, I told you, there's no ovious effect and 
it still does not work. That might be correct for the external equipment, but 
with internal mouse, the effects are much more subtile:


psmouse.proto=bare

 -> Now the internal mouse behaves as bad as the external one! It jumps around 
like crazy and clicks everywhere. That means, problems No. 3 and No.4 now 
also apply to the internal mouse!

 -> But problem No. 5 is resolved! Clicking on the touchpad does a button-1 
click.


psmouse.resetafter=3

 -> Problems No. 1 and No. 2 now become much worse! That means when moving the 
mouse cursor, cursor often stops/blocks. Then I have to keep the fingers off 
the touchpad for several seconds, before I can continue to move the mouse. 
Either regardless of the system load, or the lowest system load can start 
this effect, that's not so clear.

 -> Also the cursor now jumps much more than ever before.

So, that might be a way for a workaround: Can "reset" be disabled, e.g. 
secifying "psmouse.resetafter=0"?


Regards
Marc

  parent reply	other threads:[~2004-07-06  7:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 13:23 Dmitry Torokhov
2004-07-01 12:34 ` Marc Waeckerlin
2004-07-01 13:03   ` Dmitry Torokhov
2004-07-01 15:38     ` Marc Waeckerlin
2004-07-06  7:27     ` Marc Waeckerlin [this message]
2004-07-01 12:55 ` Marc Waeckerlin
  -- strict thread matches above, loose matches on Subject: below --
2004-07-01 13:54 Dmitry Torokhov
2004-07-02 15:10 ` Marc Waeckerlin
2004-06-29 14:32 Dmitry Torokhov
     [not found] ` <200406291808.08186.Marc.Waeckerlin@siemens.com>
2004-06-29 17:53   ` Dmitry Torokhov
2004-06-30  6:02     ` Dmitry Torokhov
2004-06-30  8:25       ` Vojtech Pavlik
2004-06-30  8:45       ` Vojtech Pavlik
2004-06-30 12:58       ` Marc Waeckerlin
2004-06-25 14:02 Dmitry Torokhov
2004-06-29 14:23 ` Marc Waeckerlin
2004-06-24 16:11 Dmitry Torokhov
2004-06-23 15:59 Dmitry Torokhov
2004-06-24  9:35 ` Marc Waeckerlin
2004-06-24 15:19 ` Marc Waeckerlin
2004-06-22  7:52 Marc Waeckerlin
2004-06-22 13:07 ` Dmitry Torokhov
2004-06-23  9:34   ` Marc Waeckerlin

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=200407060927.43588.Marc.Waeckerlin@siemens.com \
    --to=marc.waeckerlin@siemens.com \
    --cc=dtor_core@ameritech.net \
    --cc=laflipas@telefonica.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.hirsch@web.de \
    --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

Powered by JetHome