From: Kamal Mostafa <kamal@canonical.com>
To: "Ozan Çağlayan" <ozancag@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
dmitry.torokhov@gmail.com, customercare@cypress.com,
mario_limonciello@dell.com
Subject: Re: Why Cypress does not upstream its trackpad driver?
Date: Wed, 07 Nov 2012 10:32:11 -0800 [thread overview]
Message-ID: <1352313131.2751.152.camel@fourier> (raw)
In-Reply-To: <CAFub=KTf2dWxM9=saG2JaNJpEioJM8rM3UBG9BkyxRN-+j0psQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2790 bytes --]
On Tue, 2012-11-06 at 17:47 -0500, Ozan Çağlayan wrote:
> Hi,
>
> This driver [0] was written with a cooperation of Cypress, Dell and
> Canonical Engineers within the last 3-4 months. It is very nice that
> Cypress as a vendor cooperated with Canonical (Because Canonical works
> with Dell for their Project Sputnik and Dell XPS13 is used as the main
> hardware for that project and Dell XPS13 has this type of trackpad,
> Bingo!), and I am also glad that Ubuntu users benefits from this
> driver.
>
> The driver brings multi-touch scrolling, disable-while-tapping and
> makes Fn+Fx touchpad disable/enable work for not only Dell XPS13 but
> for all laptops having this trackpad (My Lenovo Ultrabook U300s for
> example, I tested the patches on fedora 17's 3.6 kernel and it works
> quiet nice)
>
> But what I am not getting that why NOBODY from Cypress/Canonical/Dell
> isn't bothering to push this driver to upstream?
In fact, Canonical is working on preparing the Cypress PS/2 trackpad
driver for submitting upstream.
> Is it too hard? I don't think so as the patches are quite non-invasive
> and small.
Your estimate of the work/risk involved not withstanding, I chose to
deploy this experimental driver in stages -- first in the oem-specific
"Sputnik project" kernel, then (recently) in the main Ubuntu kernel,
then finally (soon) upstream -- so as to minimize regressions while
shaking out the bugs. For example, the version to which you linked does
include a regression (breaks some ALPS touchpads) which we discovered
only after deploying in Ubuntu.
I expect to submit the Cypress driver upstream within two weeks. Of
course, my work on the driver is (and has been) publicly available[1].
-Kamal Mostafa <kamal@canonical.com>
[1] The latest version of this driver is represented by the patch set:
http://kernel.ubuntu.com/git?p=ubuntu%2Fubuntu-quantal.git&a=search&h=HEAD&st=commit&s=Cypress+PS%2F2
>
> Is the only distribution around is Ubuntu?
> Is the only laptop sold in the world is Dell XPS13 with an Ubuntu?
>
> I'm not trying to be impolite but it hurts me to see that a vendor
> produces an open-source driver for its device but makes use of it only
> through a specific distribution.
>
> If Cypress is just beginning developing open-source drivers for their
> devices, I hope that after this mail they will be much sensitive about
> the issue and push their drivers even before the release of their
> devices to make user experience flawless.
>
> (I googled and searched the archives of LKML and linux-input but
> couldn't find a discussion or patch series about the driver. If I
> missed it, ignore the whole stuff above)
>
> [0]: http://patchwork.ozlabs.org/patch/178903/
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-07 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 22:47 Why Cypress does not upstream its trackpad driver? Ozan Çağlayan
2012-11-07 18:32 ` Kamal Mostafa [this message]
2012-11-07 23:13 ` Troy Abercrombia
2012-11-07 23:27 ` richard -rw- weinberger
2012-11-07 23:30 ` David Solda
2012-11-08 0:00 ` David Daney
2012-11-08 0:15 ` Dmitry Torokhov
2012-11-08 0:26 ` David Solda
2012-11-08 3:45 ` Ben Gamari
2012-11-08 7:41 ` Dmitry Torokhov
2012-11-08 8:09 ` David Solda
2012-11-08 8:13 ` Ozan Çağlayan
2012-11-08 8:54 ` Dmitry Torokhov
2012-11-09 4:06 ` Robert Hancock
2012-11-12 10:57 ` Cruz Julian Bishop
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=1352313131.2751.152.camel@fourier \
--to=kamal@canonical.com \
--cc=customercare@cypress.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=ozancag@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 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).