<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> changed <a class="bz_bug_link bz_status_NEW " title="NEW - Combined Keyboard+Mouse+Touchpad device problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=99914">bug 99914</a> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">CC</td> <td> </td> <td>peter.hutterer@who-t.net </td> </tr></table> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Combined Keyboard+Mouse+Touchpad device problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=99914#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Combined Keyboard+Mouse+Touchpad device problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=99914">bug 99914</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>ok, there are a couple of issues here. The first one is that the device has everything on the same event node. That's not something that libinput handles well because historically the kernel split up the event nodes for us into one for keyboard,one for touchpad, one for mouse (though we do handle mouse+keyboard on the same node). For a touchpad to be identified as such you need BTN_TOOL_FINGER and BTN_TOUCH, both are missing. The event stream is confusing with a lot of relative deltas of -2/-2, roughly 4ms apart. So that would move the pointer to the top-left in a very short time. Given the speed of the events this would likely see maximum acceleration and thus be even faster. There are a few ABS_X/ABS_Y events but the max value there is 3072 which is a fraction of the 32k axis range. The pointer likely jumps a few pixels down but immediately moves back up due to the REL_X/REL_Y events. Probably too fast to be visible. (In reply to Gergely Nagy from <a href="show_bug.cgi?id=99914#c1">comment #1</a>) > - I press the "northwest" key, which should move the mouse towards the top > left corner: it moves to bottom right. indicates the screen is mounted the wrong way? the deltas are negative, so the screen is upside-down. > - I position the mouse back. > - I press the "northeast" key, which should move it towards the top right > corner: it moves to the bottom right. I don't see any positive REL_X/Y events, so the buttons are hooked up the wrong way. (In reply to Gergely Nagy from <a href="show_bug.cgi?id=99914#c2">comment #2</a>) > Because the firmware reports its x/y max as 32k, this explains why the > cursor always ends up on the bottom right corner. So I'm left wondering how > I can tell libinput to map the virtual touchpad's 32k*32k area to whatever > my resolution under X11 is? you can't, libinput doesn't know about that. The solution to this is to fix the firmware so the absolute range reflects the reachable axes and then let the rest of the stack DTRT.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>