From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Arjan Opmeer <arjan@opmeer.net>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: elantech.c provide a workaround for jumpy cursor on firmware 2.34
Date: Fri, 20 Mar 2009 22:46:37 -0700 [thread overview]
Message-ID: <200903202246.37383.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20090320053509.GA3633@adopmeer.homeip.net>
Hi Arjan,
On Thursday 19 March 2009 22:35:09 Arjan Opmeer wrote:
>
> + if (etd->jumpy_cursor) {
> + /* Discard packets that are likely to have bogus coordinates */
> + if (fingers > old_fingers) {
> + elantech_debug("elantech.c: discarding packet\n");
> + goto discard_packet_v1;
Can we do this unconditionally for the v1 protocol and not have an
extra konb? Do you have access to boxes with unbroken V1 to test?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2009-03-21 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 5:35 [PATCH] input: elantech.c provide a workaround for jumpy cursor on firmware 2.34 Arjan Opmeer
2009-03-21 5:46 ` Dmitry Torokhov [this message]
2009-03-21 12:17 ` Arjan Opmeer
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=200903202246.37383.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arjan@opmeer.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).