From: Diego Calleja <diegocg@gmail.com>
To: linux-input@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ping Cheng <pinglinux@gmail.com>
Subject: [PATCH] Fix touch support for wacom bamboo fun CTH-461
Date: Tue, 04 Dec 2012 00:56:50 +0100 [thread overview]
Message-ID: <3305232.JQ4fXkYdWp@diego-arch> (raw)
Commit f393ee2b814e3291c12565000210b3cf10aa5c1d forgot to add the
touch_max property for wacom bamboo fun CTH-461/S, id 056a:00d2.
This broke the touch functionality for that device. This patch,
(done with help of Ping Cheng), adds the correct value and makes
touch work again.
(Note: this problem exists since 3.5, so it may be a candidate for
-stable)
Signed-off-by: Diego Calleja <diegocg@gmail.com>
---
drivers/input/tablet/wacom_wac.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: linux/drivers/input/tablet/wacom_wac.c
===================================================================
--- linux.orig/drivers/input/tablet/wacom_wac.c
+++ linux/drivers/input/tablet/wacom_wac.c
@@ -2034,7 +2034,8 @@ static const struct wacom_features wacom
.touch_max = 2 };
static const struct wacom_features wacom_features_0xD2 =
{ "Wacom Bamboo Craft", WACOM_PKGLEN_BBFUN, 14720, 9200, 1023,
- 31, BAMBOO_PT, WACOM_INTUOS_RES, WACOM_INTUOS_RES };
+ 31, BAMBOO_PT, WACOM_INTUOS_RES, WACOM_INTUOS_RES,
+ .touch_max = 2 };
static const struct wacom_features wacom_features_0xD3 =
{ "Wacom Bamboo 2FG 6x8", WACOM_PKGLEN_BBFUN, 21648, 13700, 1023,
31, BAMBOO_PT, WACOM_INTUOS_RES, WACOM_INTUOS_RES,
next reply other threads:[~2012-12-03 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 23:56 Diego Calleja [this message]
[not found] ` <CAF8JNh+s6L1=V1ccxRSvERjgAFPekN5dP-3Y0vLBFTe+ctn52A@mail.gmail.com>
2012-12-04 5:22 ` [PATCH] Fix touch support for wacom bamboo fun CTH-461 Dmitry Torokhov
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=3305232.JQ4fXkYdWp@diego-arch \
--to=diegocg@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pinglinux@gmail.com \
/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