From: "Richard Schütz" <r.schtz@t-online.de>
To: JJ Ding <jj_ding@emc.com.tw>
Cc: linux-input@vger.kernel.org, "Tom Lin" <tom_lin@emc.com.tw>,
"Aaron Huang" <aaron_huang@emc.com.tw>,
"Éric Piel" <E.A.B.Piel@tudelft.nl>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 1/2] Input: elantech - better support all those v2 variants
Date: Tue, 13 Sep 2011 12:24:50 +0200 [thread overview]
Message-ID: <4E6F2F72.6080403@t-online.de> (raw)
In-Reply-To: <1315894549-24504-2-git-send-email-jj_ding@emc.com.tw>
Am 13.09.2011 08:15, schrieb JJ Ding:
> V2 hardware has many variants. This patch adddresses two issues:
>
> - some model also has debounce packets, but with a different signature
> than v3. Now we just check debounce for all v2 hardware.
>
> - due to different scanning methods the hardware uses, x and y ranges have
> to be calculated differently. And for some specific versions, we can just
> see them as custom-made, so set {x, y} the same values as Windows driver
> does.
>
> Signed-off-by: JJ Ding<jj_ding@emc.com.tw>
Tested-by: Richard Schütz <r.schtz@t-online.de>
Works like a charm now, thanks!
--
Regards,
Richard Schütz
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-13 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 6:15 [PATCH 0/2] Better support old elantech v2 hardware JJ Ding
2011-09-13 6:15 ` [PATCH 1/2] Input: elantech - better support all those v2 variants JJ Ding
2011-09-13 10:24 ` Richard Schütz [this message]
2011-09-13 11:28 ` JJ Ding
2011-09-13 6:15 ` [PATCH 2/2] Input: elantech - remove module parameter force_elantech JJ Ding
2011-09-13 11:02 ` [PATCH 0/2] Better support old elantech v2 hardware Éric Piel
2011-09-13 11:32 ` JJ Ding
2011-09-13 21:33 ` Chase Douglas
2011-09-14 3:43 ` JJ Ding
2011-09-14 4:32 ` M. Edward (Ed) Borasky
2011-09-16 8:56 ` JJ Ding
2011-09-16 14:21 ` Éric Piel
2011-09-19 4:54 ` JJ Ding
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=4E6F2F72.6080403@t-online.de \
--to=r.schtz@t-online.de \
--cc=E.A.B.Piel@tudelft.nl \
--cc=aaron_huang@emc.com.tw \
--cc=dmitry.torokhov@gmail.com \
--cc=jj_ding@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=tom_lin@emc.com.tw \
/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.