linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Tunin <hanipouspilot@gmail.com>
To: linux-input@vger.kernel.org
Cc: mgottschlag@gmail.com
Subject: Re: Unusual Focaltech driver behavior
Date: Fri, 17 Apr 2015 12:56:46 +0300	[thread overview]
Message-ID: <5530D8DE.7070604@gmail.com> (raw)
In-Reply-To: <5530C7D2.8090106@gmail.com>

> I noticed that myself and got some complaints like this.
> https://github.com/hanipouspilot/ubuntu-fixes/issues/2
> 
> General issue is that when one finger is on the touchpad, movement of a second finger is ignored, if the first finger does not move.
> Usually with other touchpads, when you have one finger on the touchpad and move the other, it is recognized as two-finger scrolling.
> The device itself sends relative packages as normal in that case, but linux driver ignores them, until first finger is moved.
> 
> I guess, Windows driver behaves same way. I can't test it, since I do not have Windows installed on that laptop.
> 
> As I understood, Windows driver ignores that one finger is on button area and recognizes movement of the other as one-finger movement.
> 
> It is clear that we do not know the full protocol or parameters of all touchpad models to have that button area always correct.
> But it looks like button area is set when 3rd byte in abs package is 00. There is a good chance that it is common for all touchpad models.
> 
> Do you have ideas how to fix it the easiest way?
> 
> Regards,
> 
> Dmitry
> 

I looked at it some more and noticed that if I put one finger on touchpad, then another, then move the second one, rel packets are ignored.
But if keeping both fingers on touchpad, I move the first one, rel packets work OK.
This is wrong. I can't get what's wrong with the code at the moment.

  reply	other threads:[~2015-04-17  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  8:44 Unusual Focaltech driver behavior Dmitry Tunin
2015-04-17  9:56 ` Dmitry Tunin [this message]
2015-04-17 13:33   ` Benjamin Tissoires
2015-04-17 13:39     ` Dmitry Tunin
2015-04-17 13:57       ` Benjamin Tissoires
2015-04-17 14:49         ` Dmitry Tunin
2015-04-17 14:56           ` Dmitry Tunin
2015-04-17 15:43             ` Benjamin Tissoires
2015-04-17 15:54               ` Dmitry Tunin
2015-04-21  5:35                 ` Peter Hutterer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5530D8DE.7070604@gmail.com \
    --to=hanipouspilot@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mgottschlag@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).