linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Schütz" <r.schtz@t-online.de>
To: linux-input@vger.kernel.org
Subject: elantech touchpad issues
Date: Sun, 23 Jan 2011 15:12:54 +0100	[thread overview]
Message-ID: <4D3C3766.6040805@t-online.de> (raw)

I noticed that the elantech driver reports totally wrong axis range 
values to the xf86-input-synaptics driver for the touchpad in my Samsung 
N145 Plus netbook.

kernel output:
elantech: assuming hardware version 2, firmware version 4.2.22
elantech: Synaptics capabilities query result 0x09, 0x14, 0x0b.

As it's detected as hardware version 2 the hardcoded ranges from 
elantech.h are used:
[    16.863] (--) ETPS/2 Elantech Touchpad: x-axis range 8 - 1144
[    16.863] (--) ETPS/2 Elantech Touchpad: y-axis range 8 - 760

But with synclient's monitor mode I discovered that the correct values 
for my touchpad seem to be:
min x: 0
max x: 819
min y: 355
max y: 760
(without ETP_EDGE_FUZZ_V2)

This results in unusuable edge areas by default.

When using more then one finger on the touchpad also sometimes this 
strange thing happens and the cursor jumps:
    time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy
155.600  1020 -268  31 2  0  0 0 0 0 0  00000000
155.610  1020 -268   0 0  0  0 0 0 0 0  00000000
(the second line is optional)

I guess this would have no effect (like jumping cursor) with correct 
ranges. Can't they be queried from hardware? I have no clue if these 
ranges I figured out are valid for my netbook only or if there was a 
general change in newer firmware versions. Unfortunately, I own no other 
hardware for figuring this out. I could patch the driver for my personal 
need, but I think this should by handled somehow in the driver 
automatically. If that would not work adequate I would suggest to 
introduce driver parameters to pass the ranges at runtime without the 
need for recompiling.

-- 
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

             reply	other threads:[~2011-01-23 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 14:12 Richard Schütz [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2011-09-13  1:27       ` 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=4D3C3766.6040805@t-online.de \
    --to=r.schtz@t-online.de \
    --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).