linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Xiaoxiao Liu <xiaoxiao.liu-1@cn.alps.com>,
	dmitry.torokhov@gmail.com, Hui Wang <hui.wang@canonical.com>,
	XiaoXiao Liu <sliuuxiaonxiao@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Xiaojian Cao <xiaojian.cao@cn.alps.com>,
	"zhangfp1@lenovo.com" <zhangfp1@lenovo.com>
Subject: Re: 答复: 答复: 答复: [PATCH] input: alps-fix the issue the special alps trackpoint do not work.
Date: Thu, 23 May 2019 16:01:54 +1000	[thread overview]
Message-ID: <20190523060154.GA10526@jelly> (raw)
In-Reply-To: <20190522074030.64sy7xt3wnomtxjb@pali>

On Wed, May 22, 2019 at 09:40:30AM +0200, Pali Rohár wrote:
> On Wednesday 22 May 2019 07:30:43 Xiaoxiao Liu wrote:
> > Hi Pali,
> > 
> > Ok, and cannot you set ALPS_DUALPOINT flag based on that
> > alps_check_is_trackpoint() result and then update
> > alps_process_packet_ss4_v3() code to supports also
> > V8 trackpoint packets?
> > --> Yes, we can do like so, when we use the v8 method to process the trackpoint , the mouse speed is not ideal.
> >       Then we choose the standard mouse driver.
> 
> Mouse speed is something which is configurable. Have you configured it
> somehow? Also there is libinput project should handle these settings
> more properly.
> 
> Adding Peter Hutterer, maintainer of libinput to loop. I think he could
> help with this problem.

libinput has a quirk for a magic multiplier on trackpoints. it was the only
solution I found that came close to "working" given that every device seems
to provide some other random magic data. Doc for it is here:
https://wayland.freedesktop.org/libinput/doc/latest/trackpoint-configuration.html

There are also different speeds depending on which xorg driver you'd use (or
libinput/Wayland), so a "mouse speed is not ideal" is almost a guarantee,
given a large enough variety of setups :) That's why we have the speed
toggle, but I'm happy to hear any suggestions on how to make the trackpoint
more useful (in libinput anyway).

> I do not think it is a good idea to force back to generic PS/2 mouse
> driver for touchpads and trackpoints. Native drivers for touchpads and
> trackpoints supports multitouch, absolute reporting and lot of other
> things... Also calculation of mouse speed from absolute positions on
> touchpads can be more easily fixed as from emulated relative movements.

Yeah, agree. Using PS/2 mouse drivers means you lose *all* the extra
features touchpads have like palm detection, tapping, scrolling, gestures,
etc.

Cheers,
   Peter

> 
> Dmitry, what is your opinion about this problem? What should psmouse.ko
> do in this situation? Disallow usage of absolute mode and force bare
> PS/2 relative mode?

  reply	other threads:[~2019-05-23  6:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 11:01 [PATCH] input: alps-fix the issue the special alps trackpoint do not work XiaoXiao Liu
2019-05-21  1:07 ` 答复: " Xiaoxiao Liu
2019-05-21  2:26   ` Hui Wang
2019-05-21  9:46     ` Pali Rohár
2019-05-22  2:53       ` 答复: " Xiaoxiao Liu
2019-05-22  6:35         ` Pali Rohár
2019-05-22  7:30           ` 答复: " Xiaoxiao Liu
2019-05-22  7:40             ` Pali Rohár
2019-05-23  6:01               ` Peter Hutterer [this message]
2019-05-24  5:25                 ` Hui Wang
2019-05-24  5:36                   ` Peter Hutterer
2019-05-24  5:50                     ` Hui Wang
2019-05-24  7:26                       ` Pali Rohár
2019-05-24  7:37                         ` Hui Wang
2019-05-24  9:37                           ` Peter Hutterer
     [not found]                             ` <f0c2dff9-519e-d54d-4cd0-2be666656dc2@canonical.com>
2019-05-24 10:58                               ` Peter Hutterer
2019-05-25  1:33                                 ` Hui Wang
2019-05-24  9:32                         ` Peter Hutterer
2019-05-24  9:52                           ` Pali Rohár

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=20190523060154.GA10526@jelly \
    --to=peter.hutterer@who-t.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hui.wang@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=sliuuxiaonxiao@gmail.com \
    --cc=xiaojian.cao@cn.alps.com \
    --cc=xiaoxiao.liu-1@cn.alps.com \
    --cc=zhangfp1@lenovo.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).