Re: pms elantech v4 touchpad desync due to odd 5 byte packet

2020-01-24 Thread Alexander Cronheim
Hi Ulf, Thanks for replying. > that is indeed an odd phenomenon - and an odd workaround which I > wouldn't like to see in pms without being sure that there is a > firmware bug. If you don't mind to make more tests, I'll send > you some patches for debugging (please be patient, it may take a >

Re: pms elantech v4 touchpad desync due to odd 5 byte packet

2020-01-24 Thread Ulf Brosziewski
Hi Alexander, that is indeed an odd phenomenon - and an odd workaround which I wouldn't like to see in pms without being sure that there is a firmware bug. If you don't mind to make more tests, I'll send you some patches for debugging (please be patient, it may take a while). Regards, Ulf On

pms elantech v4 touchpad desync due to odd 5 byte packet

2020-01-23 Thread Alexander Cronheim
Hi, In my machine, sometimes an odd 5 byte packet is received by pms in the 6 byte elantech v4 touchpad protocol as documented in [1]. The packet in question in hex notation is 80 80 36 00 00, which corresponds with a zero movement trackpoint packet missing its first byte which normally carries