From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.de>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, zhilla <zhilla@spymac.com>,
Victor Hahn <victorhahn@web.de>
Subject: Re: [RFC/RFT] Better handling of bad xfers/interrupt delays in psmouse
Date: Sun, 6 Feb 2005 00:29:20 -0500 [thread overview]
Message-ID: <200502060029.21068.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050205211136.GB8451@ucw.cz>
On Saturday 05 February 2005 16:11, Vojtech Pavlik wrote:
> On Sat, Feb 05, 2005 at 02:48:56PM -0500, Dmitry Torokhov wrote:
> > Hi,
> >
> > The patch below attempts to better handle situation when psmouse interrupt
> > is delayed for more than 0.5 sec by requesting a resend. This will allow
> > properly synchronize with the beginning of the packet as mouse is supposed
> > to resend entire package.
>
> Have you actually tested the mouse is really sending the whole packet?
> I'd suspect it could just resend the last byte. :I Maybe using the
Well, I did test and my touchpad behaved properly. But then I tried 2 external
mice and they are both sending ACK (and they should not) and then the last byte
only. So I guess we'll have to scrap using 0xfe idea...
> GET_PACKET command would be more useful in this case.
>
Are you talking about 0xeb? We could also try sending "set stream" mode as a
sync marker...
--
Dmitry
next prev parent reply other threads:[~2005-02-06 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 19:48 [RFC/RFT] Better handling of bad xfers/interrupt delays in psmouse Dmitry Torokhov
2005-02-05 21:11 ` Vojtech Pavlik
2005-02-06 5:29 ` Dmitry Torokhov [this message]
2005-02-06 7:23 ` Dmitry Torokhov
2005-02-06 8:37 ` Vojtech Pavlik
2005-02-06 17:52 ` Dmitry Torokhov
2005-02-06 8:29 ` Vojtech Pavlik
2005-02-06 9:27 ` Pavel Machek
2005-02-06 17:55 ` Dmitry Torokhov
2005-02-07 5:31 ` Ryan Anderson
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=200502060029.21068.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=victorhahn@web.de \
--cc=vojtech@suse.de \
--cc=zhilla@spymac.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.