https://bugs.freedesktop.org/show_bug.cgi?id=100165
Peter Hutterer <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
CC| |[email protected]
| |m, [email protected]
--- Comment #2 from Peter Hutterer <[email protected]> ---
urgh, please attach long outputs as attachments, makes analysis a bit easier.
first weird thing: udevadm doesn't show ID_INPUT_TOUCHPAD but the log claims
it's tagged as touchpad. what's going on there? did you modify some rules but
then attached a different udevadm output?
That's the real bug here to fix, remove whatever assigns ID_INPUT_TOUCHPAD and
the device should work as mouse.
the internal/external bit should be added to the hwdb in systemd, see the
instructions at the top of the file:
https://github.com/systemd/systemd/blob/master/hwdb/70-touchpad.hwdb
but first: this touchpad needs to be detected by the kernel correctly. Right
now it's in relative mouse emulation mode. The touchpad needs to be switched to
absolute mode, usually by sending the right initialization sequence from the
kernel. Once that's done, the device should announce ABS_X/ABS_Y etc and then
the rest should fall into place.
If it works under Ubuntu, try their kernel and then get them to upstream the
patches if it truly works. Otherwise, quick email search suggests
https://patchwork.kernel.org/patch/5596041/ as a place to start kernel hacking.
There's a chance that the new device is still a synaptics one and that it's
hooked up the same way. CC-ing benjamin just in case he knows more.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
