From: "Richard Schütz" <r.schtz@t-online.de>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: JJ Ding <jj_ding@emc.com.tw>,
linux-input@vger.kernel.org, Aaron Huang <aaron_huang@emc.com.tw>,
Tom Lin <tom_lin@emc.com.tw>
Subject: Re: elantech touchpad issues
Date: Mon, 12 Sep 2011 11:57:06 +0200 [thread overview]
Message-ID: <4E6DD772.20004@t-online.de> (raw)
In-Reply-To: <4E6DC5F6.7090008@tudelft.nl>
Am 12.09.2011 10:42, schrieb Éric Piel:
> Op 08-09-11 20:17, Richard Schütz schreef:
>> Am 08.09.2011 06:18, schrieb JJ Ding:
>>
>> Yeah, this fixes the annoying issue with multiple fingers.
>>
>> Now only the problem with the wrong axis ranges is remaining.
>>
>
> I've tried with my version of the hardware (a old v2) and it doesn't
> seem to have the problem you describe.
>
> Basically your problem is that the driver reports ranges as 0-1152 and
> 0-576, but in reality, when you move your finger, the coordinates stay
> in the ranges 0-819, 171-576. So in practice the cursor moves as
> expected but the borders to allow the scrolling don't work. Is that right?
Exactly.
> I wonder if it's normal that the device has a range even smaller than
> what it reports, and whether something can be done. JJ Ding?
>
> Cheers,
> Éric
--
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-12 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 14:53 elantech touchpad issues Richard Schütz
2011-09-07 1:46 ` JJ Ding
2011-09-08 4:18 ` JJ Ding
2011-09-08 18:17 ` Richard Schütz
2011-09-12 8:42 ` Éric Piel
2011-09-12 9:57 ` Richard Schütz [this message]
2011-09-13 1:27 ` JJ Ding
-- strict thread matches above, loose matches on Subject: below --
2011-01-23 14:12 Richard Schütz
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=4E6DD772.20004@t-online.de \
--to=r.schtz@t-online.de \
--cc=E.A.B.Piel@tudelft.nl \
--cc=aaron_huang@emc.com.tw \
--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 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).