<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - ABS_MT_DISTANCE is not handled by libinput"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101861#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - ABS_MT_DISTANCE is not handled by libinput"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101861">bug 101861</a>
from <span class="vcard"><a class="email" href="mailto:zboszor@pr.hu" title="Zoltán Böszörményi <zboszor@pr.hu>"> <span class="fn">Zoltán Böszörményi</span></a>
</span></b>
<pre>I have a kernel patch based on parts of the GPL EETI kernel driver
I got sent to by way of a PC maker. The patch is at:
<a href="http://marc.info/?l=linux-input&m=150167441312020&w=2">http://marc.info/?l=linux-input&m=150167441312020&w=2</a>
With this patch, xf86-input-libinput works out of the box.
The way EETI treats their devices is somewhat funny.
Their kernel driver leaves a backdoor (a pipe) so the older generation of their
closed source daemon can switch it into some specific mode. Then the daemon
opens a new uinput device and feeds it with data.
Same with their latest generation of said daemon which talks to the device
over a hidraw device node. The in-kernel hid-multitouch driver then completely
loses events and only the events fed by the daemon to uinput is accepted.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>