From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: [RFC/RFT] PS/2 mouse resync for KVM users
Date: Wed, 23 Jun 2004 09:07:42 -0700 (PDT) [thread overview]
Message-ID: <20040623160742.13669.qmail@web81308.mail.yahoo.com> (raw)
linux@horzon.com wrote:
> > - flag "suspect" packets - 1st bytes with overflow bits set and bytes
> that
> > indicate that Left + Middle or Right + Middle buttons are pressed at
> the
> > same time which is unusial combination. Suspect packets, together with
> > timeouts, are treated as "soft" errors.
>
> I'm a little unhappy with this. They are *currently* unusual, but
> I hate to preclude anyone from using them.
I also had some concerns, it's not the final patch version by any
means... Your suggestions are very interesting and I will try to
implement some of them (acceleration and "suspicion scoring" is a
bit of overkill I think), but I like the "unusial combination" idea
because you can trigger reconnect _at will_. Although with my sysfs
patches one could do it by echoing reconnect to driver attribute of
corresponding serio port ability just hold couple of buttons and
wiggle mouse and have it restore connection seems to be nice.
What if we trigger packets with all 3 buttons pressed as suspect?
--
Dmitry
next reply other threads:[~2004-06-23 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 16:07 Dmitry Torokhov [this message]
2004-06-28 18:58 ` [RFC/RFT] PS/2 mouse resync for KVM users Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 9:36 linux
2004-06-23 6:40 Dmitry Torokhov
2004-06-23 7:39 ` Vojtech Pavlik
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=20040623160742.13669.qmail@web81308.mail.yahoo.com \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.