<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - libinput ignores "pad" device on Wacom MobileStudio Pro" href="https://bugs.freedesktop.org/show_bug.cgi?id=102100#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - libinput ignores "pad" device on Wacom MobileStudio Pro" href="https://bugs.freedesktop.org/show_bug.cgi?id=102100">bug 102100</a> from <a class="email" href="mailto:killertofu@gmail.com" title="Jason Gerecke <killertofu@gmail.com>"> Jason Gerecke</a> <pre>IIRC, the accelerometer discussions came about in response to the 27QHD which was the first Wacom device to have one. Ping introduced INPUT_PROP_ACCELEROMETER [1] for it and you later [2] documented the meaning of the property: > Directional axes on this device (absolute and/or relative x, y, z) represent > accelerometer data. All other axes retain their meaning. A device must not mix > regular directional axes and accelerometer axes on the same event node. I imagine this issue wasn't noticed with the 27QHD because it only has the soft KEY_* buttons (which aren't yet handled in userspace) -- no ExpressKeys, rings, or other controls. ... Unless I'm forgetting a more recent discussion of accelerometer data? [1]: <a href="https://patchwork.kernel.org/patch/5720721/">https://patchwork.kernel.org/patch/5720721/</a> [2]: <a href="https://patchwork.kernel.org/patch/6102851/">https://patchwork.kernel.org/patch/6102851/</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>