Android marks found axes as 'valid' only if they have a minimum
and maximum value that aren't equal. Since we don't actually
assign any range information for ABS_MISC, Android doesn't bother
to mark it such. This prevents userspace from being able to make
use of tool serial information.
Signed-off-by: Jason Gerecke <killert...@gmail.com>
---
2.6.38/wacom_wac.c | 2 +-
3.7/wacom_wac.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/2.6.38/wacom_wac.c b/2.6.38/wacom_wac.c
index 02d45a4..b329eb5 100644
--- a/2.6.38/wacom_wac.c
+++ b/2.6.38/wacom_wac.c
@@ -1535,7 +1535,7 @@ int wacom_setup_input_capabilities(struct input_dev
*input_dev,
input_dev->evbit[0] |= BIT_MASK(EV_KEY) | BIT_MASK(EV_ABS);
__set_bit(BTN_TOUCH, input_dev->keybit);
- __set_bit(ABS_MISC, input_dev->absbit);
+ input_set_abs_params(input_dev, ABS_MISC, INT_MIN, INT_MAX, 0, 0);
wacom_abs_set_axis(input_dev, wacom_wac);
diff --git a/3.7/wacom_wac.c b/3.7/wacom_wac.c
index 17ba835..cd6b2af 100644
--- a/3.7/wacom_wac.c
+++ b/3.7/wacom_wac.c
@@ -1467,6 +1467,8 @@ static void wacom_abs_set_axis(struct input_dev
*input_dev,
{
struct wacom_features *features = &wacom_wac->features;
+ input_set_abs_params(input_dev, ABS_MISC, INT_MIN, INT_MAX, 0, 0);
+
if (features->device_type == BTN_TOOL_PEN) {
input_set_abs_params(input_dev, ABS_X, 0, features->x_max,
features->x_fuzz, 0);
--
1.8.4
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
