wulf7
commented
3 years ago Here I first press the left button and then put a short stroke on the pad. hms0 keeps reporting the (relative) cursor position even after the stroke motion ends. The report stops when another press of the left button is given at the end of the event log. It seems spurious reports are continuously generated even the finger is off the touch pad.
It is a result of missing GPIO interrupt support. Sampling code reads last report generated by touchpad over and over again that results in cursor drift.
Is there any way to correct this?
No way with current code. I'll try to write code to filter out consecutive repeated packets when iichid is running in sampling mode. Hope it will help, so stay tuned.
In addition, if it is recongnized as a hmt device, it would be super.
Unfortunately, the touchpad uses proprietary Synaptics protocol rather than Microsoft one, thus it is not compatible with hms. I do have one device that uses such a protocol but it is connected over SMBus rather over I2C so even if would port driver for it, that driver could not be directly used.
cederom
omatsuda
Thank you very much for developing iichid.
I recently set up FreeBSD for a Panasonic laptop CF-QV. The touch pad of this machine is not recognized as a PS/2 mouse and definitely we need iichid. But at this moment, it is not successful: once the mouse cursor is moved with a short stroke on the touch pad, the cursor keeps moving even after the finger is off from the touch pad.
I'm using 13.0-CURRENT r368820 (right after the snapshot 201231) and the latest iichid (Dec. 27). xorg-7.7_3 is installed from the packages.
"dmesg" shows iicbus[01] and iic[01] are created, though there are some anxious messages: dmesg.txt
iicbus0: unknown card at addr 0x2c iicbus1: unknown card at addr 0x10 iicbus1: unknown card at addr 0x1f iicbus1: unknown card at addr 0x11
Anyway, when "kldload iichid", hms0 is created, but no hmt device.
kldload.txt
hms0 is connected to /dev/input/event6. Output of "evemu-record /dev/input/event6" is attached. event6.txt
Here I first press the left button and then put a short stroke on the pad. hms0 keeps reporting the (relative) cursor position even after the stroke motion ends. The report stops when another press of the left button is given at the end of the event log. It seems spurious reports are continuously generated even the finger is off the touch pad.
Is there any way to correct this? In addition, if it is recongnized as a hmt device, it would be super.