From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matteo Delfino <kendatsuba@gmail.com>
Cc: linux-input@vger.kernel.org, Alessandro Rubini <rubini@ipvvis.unipv.it>
Subject: Re: [PATCH] elantech: fix for newer hardware versions (v7)
Date: Fri, 5 Jul 2013 21:30:29 -0700 [thread overview]
Message-ID: <20130706043029.GA8212@core.coreip.homeip.net> (raw)
In-Reply-To: <51D74638.1020305@gmail.com>
Hi Matteo,
On Sat, Jul 06, 2013 at 12:18:32AM +0200, Matteo Delfino wrote:
> * Fix version recognition in elantech_set_properties
>
> The new hardware reports itself as v7 but the packets'
> structure is unaltered.
>
> * Fix packet type recognition in elantech_packet_check_v4
>
> The bitmask used for v6 is too wide, only the last three bits of
> the third byte in a packet (packet[3] & 0x03) are actually used to
> distinguish between packet types.
> Starting from v7, additional information (to be interpreted) is
> stored in the remaining bits (packets[3] & 0x1c).
> In addition, the value stored in (packet[0] & 0x0c) is no longer
> a constant but contains additional information yet to be deciphered.
> This change should be backwards compatible with v6 hardware.
>
> Additional-author: Giovanni Frigione <gio.frigione@gmail.com>
> Signed-off-by: Matteo Delfino <kendatsuba@gmail.com>
Thank you for the patch, unfortunately your mailer line-wrapped it and
it can't be applied. Could you please resend it using MUA that does not
perform line-wrapping?
Also, now that you only use (packet[3] & 0x03) to determine packet type,
could you turn series of 'if' statements in elantech_packet_check_v4()
into a 'switch'?
Thanks!
--
Dmitry
next prev parent reply other threads:[~2013-07-06 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 22:18 [PATCH] elantech: fix for newer hardware versions (v7) Matteo Delfino
2013-07-06 4:30 ` Dmitry Torokhov [this message]
2013-07-06 7:20 ` Matteo Delfino
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=20130706043029.GA8212@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=kendatsuba@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rubini@ipvvis.unipv.it \
/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).