From: Sebastian Schmidt <yath@yath.de>
To: Aaron Ma <aaron.ma@canonical.com>
Cc: 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: Sat, 30 Dec 2017 15:40:40 +0100 [thread overview]
Message-ID: <20171230144040.GB23284@marax.lan.yath.de> (raw)
In-Reply-To: <d8770041-baf4-205e-7818-7ea477f69a29@canonical.com>
On Sat, Dec 30, 2017 at 10:17:55PM +0800, Aaron Ma wrote:
> Sorry, I don't know anything about the firmware software.
> So you can NOT expect me to fix the firmware issue.
You changed trackpoint.c in ec667683c532c93fb41e100e5d61a518971060e2 to,
according to the commit message, “support version 2 and 3”. Even though
I don’t understand the change, because according to the comment next to
TP_MAGIC_IDENT (and the code in trackpoint.c), the version is reported
in param[1], not in param[0]. Also it’s called “MAGIC_IDENT” and not
“SUPPORTED_FIRMWARE_VERSIONS”.
> I have helped answer all the question I can.
> I don't know why you blame me like this.
Because reverting your commit fixes the issue for me. In fact, I was
just starting to reverse engineer the differences between firmware
versions 3 and 4, when I noticed a file called
“Alps_Pointing-Device_Updater_amd64_1_4.exe”, and all the other binaries
also saying only “ALPS” and not “Synaptics”, in the
trackpoint_fw_updater_1.0.0.9.zip update package (for model 20HR). Are
you actually certain that Gen5 X1s do always contain a Synaptics
Trackpoint and not some models an ALPS one? Does changing the speed on
your FW version 0x03 or 0x02 work at all?
I’m suspecting that by changing the TP_MAGIC_IDENT to supposedly newer
firmware versions you just made that driver wrongly recognize an ALPS
trackpoint as whatever trackpoint.c is for.
And I am, in fact, upset, since you don’t appear to be supporting the
code you have written, even though it causes regressions. Then you ask
me to install a kernel that includes a keylogger without any warning
whatsoever and now “yeah, sysfs is barely used, just use GNOME”. Who
else should I blame, please?
Thanks,
Sebastian
next prev parent reply other threads:[~2017-12-30 14:40 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 [this message]
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
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=20171230144040.GB23284@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).