All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Gamari <ben@smart-cactus.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Allen_Hung@Dell.com, Mario_Limonciello@Dell.com,
	linux-input@vger.kernel.org
Subject: Re: Dell Latitude E7470 touchpad status
Date: Tue, 17 May 2016 11:50:06 +0200	[thread overview]
Message-ID: <877fet10a9.fsf@smart-cactus.org> (raw)
In-Reply-To: <20160517082309.GZ29844@pali>

[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]

Pali Rohár <pali.rohar@gmail.com> writes:

> Hi Ben!
>
> Maybe it could help you, look at my email sent to linux-input ML year
> ago: http://thread.gmane.org/gmane.linux.kernel.input/41210

Hi Pali!

Thanks, this looks great (assuming this is in fact the protocol spoken
by the E7470 hardware; perhaps Allen could confirm this?). I'll have a
go at rebasing this sometime soon, although it looks like this may take
a fair bit of work as the patch is of the usual... questionable quality
that you'd expect from a hardware vendor and on top of that the driver
itself seems to have evolved significantly.

>
> Also try to look at dell drivers page, there could be linux package for
> your laptop with drivers. Lot of them used to be in dkms format
> (upstream source code with dell changes).
>
I've been unable to find a support package for my machine on the web
site. However, I'm also in touch with Dell through the usual support
channel so perhaps they'll be able to provide a more up-to-date code
drop.

> ALPS code from Dell were open source, it was just hard to find it and
> compile it on other then one kernel version. And harder to generate
> patch (like I did in above email)...
>
Right, as I said it looks like rebasing this code drop onto a recent
kernel might require quite some effort.

I do wish that Dell would apply more pressure on their input device
vendors to take upstream support (or open protocol documentation)
seriously. It's very frustrating that we need to go through this same
process with every hardware iteration.

Thanks again for the reference, Pali!

Cheers,

- Ben


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2016-05-17  9:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 13:31 Dell Latitude E7470 touchpad status Ben Gamari
     [not found] ` <23E0F704395E694FA4710C833FA087E50D40B8BF13@TPEX7ADC101.APAC.DELL.COM>
2016-05-17  6:03   ` Ben Gamari
2016-05-17  8:23     ` Pali Rohár
2016-05-17  9:50       ` Ben Gamari [this message]
2016-05-17 13:16         ` Pali Rohár
2016-05-17 14:46           ` Allen_Hung
2016-05-17 15:22             ` Pali Rohár
2016-05-25  4:38               ` Allen_Hung
2016-05-25  7:39                 ` Pali Rohár
2016-05-25 12:09                   ` Ben Gamari
2016-05-25 14:45                     ` Pali Rohár
2016-05-25 15:19                       ` Hans de Goede
2016-05-25 15:32                         ` Pali Rohár
2016-05-25 12:32                   ` Ben Gamari
2016-05-25 15:43                     ` Pali Rohár
2016-05-25 15:47                       ` Hans de Goede
2016-05-25 15:53                       ` Ben Gamari
2016-05-25 16:01                         ` Packet format for ALPS V8 trackstick (Was: Re: Dell Latitude E7470 touchpad status) Pali Rohár
2016-05-26  8:55                           ` [PATCH] Alps SS4 V2 support for Dell Latitude 7470 Ben Gamari
2016-05-26  8:55                             ` [PATCH 1/3] input/alps: Split up ALPS_BUTTONPAD behavior change Ben Gamari
2016-05-26  8:55                             ` [PATCH 2/3] input/alps: Add touchstick support for V8 protocol devices Ben Gamari
2016-05-26  8:55                             ` [PATCH 3/3] input/alps: Add device description for Dell Latitude E7470 Ben Gamari
2016-05-26  9:05                               ` Pali Rohár
2016-05-26 12:19                                 ` Hans de Goede
2016-05-26 12:35                                   ` 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=877fet10a9.fsf@smart-cactus.org \
    --to=ben@smart-cactus.org \
    --cc=Allen_Hung@Dell.com \
    --cc=Mario_Limonciello@Dell.com \
    --cc=linux-input@vger.kernel.org \
    --cc=pali.rohar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.