diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2014-05-05 09:36:43 -0700 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2014-06-09 13:29:08 +0100 |
| commit | e058d7cd3fb7328c3d768686e416e873a1bf2e3f (patch) | |
| tree | cd5ea41a7a13680a94a4292401c4ec550c31dbdb /Documentation/oops-tracing.txt | |
| parent | 41023bc32be31ec611c014dc26c8412850a6a6da (diff) | |
| download | lwn-e058d7cd3fb7328c3d768686e416e873a1bf2e3f.tar.gz lwn-e058d7cd3fb7328c3d768686e416e873a1bf2e3f.zip | |
Input: elantech - fix touchpad initialization on Gigabyte U2442
commit 36189cc3cd57ab0f1cd75241f93fe01de928ac06 upstream.
The hw_version 3 Elantech touchpad on the Gigabyte U2442 does not accept
0x0b as initialization value for r10, this stand-alone version of the
driver: http://planet76.com/drivers/elantech/psmouse-elantech-v6.tar.bz2
Uses 0x03 which does work, so this means not setting bit 3 of r10 which
sets: "Enable Real H/W Resolution In Absolute mode"
Which will result in half the x and y resolution we get with that bit set,
so simply not setting it everywhere is not a solution. We've been unable to
find a way to identify touchpads where setting the bit will fail, so this
patch uses a dmi based blacklist for this.
https://bugzilla.kernel.org/show_bug.cgi?id=61151
Reported-by: Philipp Wolfer <ph.wolfer@gmail.com>
Tested-by: Philipp Wolfer <ph.wolfer@gmail.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'Documentation/oops-tracing.txt')
0 files changed, 0 insertions, 0 deletions