On Fri, Mar 27, 2015 at 02:52:15PM -0700, Jason Gerecke wrote:
Did some practical testing of these patches and noticed two issues with the
touchstrips:
On 3/17/2015 11:58 PM, Peter Hutterer wrote:
From: Benjamin Tissoires benjamin.tissoi...@gmail.com
Same approach as evdev-tablet (started
Did some practical testing of these patches and noticed two issues with
the touchstrips:
On 3/17/2015 11:58 PM, Peter Hutterer wrote:
From: Benjamin Tissoires benjamin.tissoi...@gmail.com
Same approach as evdev-tablet (started as copy/paste), with axis and buttons
adjusted. Wacom's handling
On Thu, Mar 19, 2015 at 02:01:29PM -0700, Jason Gerecke wrote:
David's already asked the API questions that popped in my head, so I'll just
wait for feedback on his thread. As far as this patch goes, things look
pretty good though there are two comments:
On 3/17/2015 11:58 PM, Peter Hutterer
David's already asked the API questions that popped in my head, so I'll
just wait for feedback on his thread. As far as this patch goes, things
look pretty good though there are two comments:
On 3/17/2015 11:58 PM, Peter Hutterer wrote:
From: Benjamin Tissoires benjamin.tissoi...@gmail.com
From: Benjamin Tissoires benjamin.tissoi...@gmail.com
Same approach as evdev-tablet (started as copy/paste), with axis and buttons
adjusted. Wacom's handling of pad devices requires a lot of non-obvious
handling, e.g. ABS_THROTTLE is the second ring, ABS_RX is the strip, etc.
This is not generic
