From: Aaron Ma <aaron.ma@canonical.com>
To: Sebastian Schmidt <yath@yath.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: Re: PROBLEM: Changing speed on ThinkPad X1 Carbon 5th trackpoint causes "failed to enable mouse"
Date: Sun, 31 Dec 2017 02:54:55 +0800 [thread overview]
Message-ID: <c9f4591f-c40f-deb2-f379-310f159c06cb@canonical.com> (raw)
In-Reply-To: <20171230181625.GA1687@marax.lan.yath.de>
The patch[2] is recognized to ""ImPS/2 Generic Wheel Mouse""
Please refer to link:
https://lkml.org/lkml/2017/8/21/558
Which mentioned my commit can resolve his issue.
Your scroll mode is workable by libinput and that is not enabled by
kernel driver.
People who used "xorg-input-evdev" will *NOT* enable scroll mode.
Lenovo delivered some different touchpads/trackpoint, sometimes with
broken firmwares.
I have helped one person:edvard.holst@gmail.com who had investigated
trackpoint bug for long time, he mentioned the your link[1] long time
ago. Finally it's firmware didn't respond anything through PS/2 command.
LEN009a/LEN0072 do have some difference, but for your log and e-mail, I
didn't see any difference.
next prev parent reply other threads:[~2017-12-30 18:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 9:11 PROBLEM: Changing speed on ThinkPad X1 Carbon 5th trackpoint causes "failed to enable mouse" Sebastian Schmidt
2017-12-28 10:56 ` Aaron Ma
2017-12-28 14:28 ` Sebastian Schmidt
2017-12-28 15:53 ` Aaron Ma
2017-12-29 19:05 ` Sebastian Schmidt
2017-12-30 6:43 ` Aaron Ma
2017-12-30 9:57 ` Sebastian Schmidt
2017-12-30 13:54 ` Aaron Ma
2017-12-30 14:11 ` Sebastian Schmidt
2017-12-30 14:17 ` Aaron Ma
2017-12-30 14:40 ` Sebastian Schmidt
2017-12-30 15:00 ` Aaron Ma
2017-12-30 15:02 ` Greg KH
2017-12-30 15:08 ` Aaron Ma
2017-12-30 15:26 ` Greg KH
2017-12-30 15:46 ` Aaron Ma
2017-12-30 15:53 ` Sebastian Schmidt
2017-12-30 17:37 ` Aaron Ma
2017-12-30 18:16 ` Sebastian Schmidt
2017-12-30 18:54 ` Aaron Ma [this message]
2017-12-30 15:24 ` Sebastian Schmidt
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=c9f4591f-c40f-deb2-f379-310f159c06cb@canonical.com \
--to=aaron.ma@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=yath@yath.de \
/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).