From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
jeff.chuang7178@gmail.com, james.chen@emc.com.tw,
herman.lin@emc.com.tw, Duson Lin <dusonlin@emc.com.tw>
Subject: Re: input: elantech.c: adding more Fujtisu notebooks to force crc_enabled
Date: Tue, 27 Jan 2015 15:27:52 -0800 [thread overview]
Message-ID: <20150127232752.GA24529@dtor-ws> (raw)
In-Reply-To: <54C74A69.7060105@ts.fujitsu.com>
On Tue, Jan 27, 2015 at 09:20:57AM +0100, Rainer Koenig wrote:
> Extending the patch from November 2014 with two more Fujitsu LIFEBOOK
> models that also ship the Elantech touchpad and don't work with
> crc_disabled.
>
> Signed-off-by: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
Applied, thank you.
However I am not happy with the direction we are going - the fact that
we need to add more and more laptops to the quirk. It would be better
if we could detect whether we need CRC or not by querying the touchpad
somehow. Elantech folks, could you help us here?
Thanks!
>
> ---
> My responsibility is enabling Linux on Fujitsu desktops and sometimes
> also notebooks. Stumbled into this issue during investigation of a
> customer project and successfully tested the patch on both machines.
>
> diff -uNr old/drivers/input/mouse/elantech.c new/drivers/input/mouse/elantech.c
> --- old/drivers/input/mouse/elantech.c 2015-01-27 08:51:18.101122218 +0100
> +++ new/drivers/input/mouse/elantech.c 2015-01-27 08:51:00.880921663 +0100
> @@ -1475,6 +1475,20 @@
> DMI_MATCH(DMI_PRODUCT_NAME, "CELSIUS H730"),
> },
> },
> + {
> + /* Fujitsu LIFEBOOK E554 does not work with crc_enabled == 0 */
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK E554"),
> + },
> + },
> + {
> + /* Fujitsu LIFEBOOK E544 does not work with crc_enabled == 0 */
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK E544"),
> + },
> + },
> #endif
> { }
> };
>
> --
> Dipl.-Inf. (FH) Rainer Koenig
> Project Manager Linux Clients
> Dept. PDG WPS R&D SW OSE
>
> Fujitsu Technology Solutions
> Bürgermeister-Ullrich-Str. 100
> 86199 Augsburg
> Germany
>
> Telephone: +49-821-804-3321
> Telefax: +49-821-804-2131
> Mail: mailto:Rainer.Koenig@ts.fujitsu.com
>
> Internet ts.fujtsu.com
> Company Details ts.fujitsu.com/imprint.html
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-27 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 8:20 input: elantech.c: adding more Fujtisu notebooks to force crc_enabled Rainer Koenig
2015-01-27 23:27 ` Dmitry Torokhov [this message]
2015-01-28 3:37 ` duson
2015-02-03 1:00 ` 洪一竹
2015-02-03 12:28 ` Rainer Koenig
2015-02-03 12:50 ` 洪一竹
2015-02-03 17:17 ` Vincent Jaubert
2015-02-04 10:46 ` 洪一竹
2015-02-04 11:55 ` Vincent Jaubert
2015-02-04 12:02 ` 洪一竹
2015-02-04 20:18 ` Vincent Jaubert
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=20150127232752.GA24529@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=dusonlin@emc.com.tw \
--cc=herman.lin@emc.com.tw \
--cc=james.chen@emc.com.tw \
--cc=jeff.chuang7178@gmail.com \
--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).