https://bugs.freedesktop.org/show_bug.cgi?id=102100
Peter Hutterer changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #10 from Peter Hutterer ---
what's the new range? that commit doesn't give me any info here - still 0..71?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #9 from Jason Gerecke ---
Ah, indeed. I'd recently fixed the X issue and for some reason was thinking
about it instead of the similar kernel issue. The fix for the kernel bug was
accepted by Jiri it into his
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #8 from Peter Hutterer ---
but the evemu record above shows the kernel device - and that's 0-1. So
regardless what xf86-input-wacom does, this looks like a kernel bug?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #7 from Jason Gerecke ---
The xf86-input-wacom driver isn't so good at using the kernel for feature/range
detection. The first patch I linked ensures the "WCM_RING" flag is set for this
device. Without that
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #6 from Peter Hutterer ---
that looks like a different issue, what I'm referring to here is that the
*range* of the wheel is 0 to 1 - that's not a wheel? or am I missing something
here?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #5 from Jason Gerecke ---
(In reply to Peter Hutterer from comment #4)
> (In reply to Jason Gerecke from comment #0)
> > # Event code 8 (ABS_WHEEL)
> > # Value0
> > # Min 0
> >
https://bugs.freedesktop.org/show_bug.cgi?id=102100
--- Comment #4 from Peter Hutterer ---
(In reply to Jason Gerecke from comment #0)
> # Event code 8 (ABS_WHEEL)
> # Value0
> # Min 0
> # Max 1
^ is this really correct?
https://bugs.freedesktop.org/show_bug.cgi?id=102100
Peter Hutterer changed:
What|Removed |Added
Status|NEW |NEEDINFO