From: Sebastian Kapfer <sebastian_kapfer@gmx.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Input ML <linux-input@vger.kernel.org>
Subject: Re: [alps] Timing patch, revised again :-)
Date: Mon, 07 Dec 2009 01:27:49 +0100 [thread overview]
Message-ID: <1260145669.21632.15.camel@sardelle.necksus.de> (raw)
In-Reply-To: <20091206200957.GA18820@core.coreip.homeip.net>
On So, 2009-12-06 at 12:09 -0800, Dmitry Torokhov wrote:
> On Sun, Dec 06, 2009 at 08:53:57PM +0100, Sebastian Kapfer wrote:
> > >
> >[...]
> > Hmm I guess we could do something like this, but IMHO it makes the code
> > needlessly arcane. What would be the point? Save 3 bytes of buffer?
> > Deliver the mouse movement a microsecond earlier?
>
> No, this allows us validate the data bytes as tehy come in and probably
> detect desync right away and resync earlier.
Hi Dmitry,
note that the resync code is disabled anyway, and the hardware gets
reset in that case, which means losing tens of milliseconds. (I don't
think we have desync problems left, at least for this particular hw.)
--
Best Regards, | Hi! I'm a .signature virus. Copy me into
Sebastian | your ~/.signature to help me spread!
next prev parent reply other threads:[~2009-12-07 0:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 16:54 [alps] Timing patch, revised again :-) Sebastian Kapfer
2009-12-04 8:49 ` Dmitry Torokhov
2009-12-04 21:47 ` Sebastian Kapfer
2009-12-04 23:49 ` Dmitry Torokhov
2009-12-04 23:52 ` Dmitry Torokhov
2009-12-06 19:53 ` Sebastian Kapfer
2009-12-06 20:09 ` Dmitry Torokhov
2009-12-07 0:27 ` Sebastian Kapfer [this message]
2009-12-13 22:01 ` [PATCH 1/2] Sebastian Kapfer
2009-12-13 22:09 ` [PATCH 2/2] Alps Dualpoint, Interleaved packets Sebastian Kapfer
2009-12-15 6:42 ` Dmitry Torokhov
2009-12-15 21:01 ` Sebastian Kapfer
2009-12-15 22:49 ` Dmitry Torokhov
2009-12-16 0:01 ` Sebastian Kapfer
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=1260145669.21632.15.camel@sardelle.necksus.de \
--to=sebastian_kapfer@gmx.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).