From: Sebastian Schmidt <yath@yath.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Aaron Ma <aaron.ma@canonical.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] Revert "Input: trackpoint - add new trackpoint firmware ID"
Date: Mon, 8 Jan 2018 16:11:01 +0100 [thread overview]
Message-ID: <20180108151101.GA2220@marax.lan.yath.de> (raw)
In-Reply-To: <20180107065201.q2xck62unijt3avr@dtor-ws>
Hi Dmitry,
On Sat, Jan 06, 2018 at 10:52:01PM -0800, Dmitry Torokhov wrote:
> Guys, could you please try the patch below? It will not solve the
> "speed" issue on 0x01 devices, but hopefully we won't be exposing
> non-existing controls on others.
Thanks for looking into this. Which speed issue on 0x01 devices? I
thought those were the legacy ones that used to work and still do as
ever.
I've tried your (slightly modified, see below) patch and the trackpoint
now gets apparently[1] correctly detected as "psmouse serio2:
trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3". However, I
still have the feeling that it's a lot more sensitive (or faster?) than
with the regular PS/2 driver - even with libinput accel speed turned to
-1. I don't know how I could measure this objectively, but there must be
some difference between the trackpoint driver and the regular one. Is it
maybe an init sequence that causes it to report more sensitively, or a
different resolution, or ...? I really have no idea how mice work. :)
Also, I'm wondering, since my trackpoint works just fine as "Generic
PS/2 Mouse", including the third button. The driver even says:
| /*
| * Bare PS/2 protocol "detection". Always succeeds.
| */
| static int ps2bare_detect(struct psmouse *psmouse, bool set_properties)
| {
| [...]
| /*
| * We have no way of figuring true number of buttons so let's
| * assume that the device has 3.
| */
| __set_bit(BTN_MIDDLE, psmouse->dev->keybit);
| }
|
| return 0;
| }
So I wonder what driver Aaron was using that didn't report a third
button. What vendor/firmwares did you (get reports of) have that middle
mouse button problem on, Aaron?
Thanks,
Sebastian
1: If it's actually Elan. I've taken out my battery but could only
find FRU numbers on the back of the keyboard, no signs of a vendor.
<https://photos.app.goo.gl/iafpfzvRY042dOBo2> or
<https://t.yath.de/IMG_20180108_143205.jpg>
In trackpoint_start_protocol:
> + switch (param[0]) {
> + case TP_VARIANT_IBM:
> + case TP_VARIANT_ALPS:
> + case TP_VARIANT_ELAN:
> + case TP_VARIANT_NXP:
> + if (variant_id)
> + *variant_id = param[0];
> + if (firmware_id)
> + *firmware_id = param[1];
> + break;
^^^^^
That should be a return 0.
> + }
>
> - return 0;
> + return -ENODEV;
> }
next prev parent reply other threads:[~2018-01-08 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 15:22 [PATCH] Revert "Input: trackpoint - add new trackpoint firmware ID" Sebastian Schmidt
2017-12-30 15:32 ` Greg KH
2017-12-30 15:41 ` Sebastian Schmidt
2017-12-31 4:37 ` Aaron Ma
2017-12-31 8:26 ` Greg KH
2017-12-31 8:51 ` Aaron Ma
2018-01-02 7:08 ` Dmitry Torokhov
2018-01-02 13:57 ` Aaron Ma
2018-01-05 0:56 ` Dmitry Torokhov
2018-01-05 13:29 ` Aaron Ma
2018-01-05 16:23 ` Dmitry Torokhov
2018-01-07 6:52 ` Dmitry Torokhov
2018-01-08 15:11 ` Sebastian Schmidt [this message]
2018-01-09 0:40 ` Dmitry Torokhov
2018-01-09 1:35 ` Peter Hutterer
2018-01-14 20:39 ` ulrik.debie-os
2018-01-14 20:57 ` ulrik.debie-os
2018-01-16 23:49 ` Dmitry Torokhov
2018-01-21 20:37 ` ulrik.debie-os
2018-01-21 21:08 ` Dmitry Torokhov
2018-01-22 18:41 ` Dmitry Torokhov
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=20180108151101.GA2220@marax.lan.yath.de \
--to=yath@yath.de \
--cc=aaron.ma@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
/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).