[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <509AF634.2040500@gmail.com>
Date: Wed, 07 Nov 2012 16:00:52 -0800
From: David Daney <ddaney.cavm@...il.com>
To: David Solda <dso@...ress.com>
CC: Troy Abercrombia <ta@...ress.com>,
Kamal Mostafa <kamal@...onical.com>,
Ozan Çağlayan <ozancag@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>,
customercare <customercare@...ress.com>,
"mario_limonciello@...l.com" <mario_limonciello@...l.com>
Subject: Re: Why Cypress does not upstream its trackpad driver?
On 11/07/2012 03:30 PM, David Solda wrote:
> Kamal,
>
> My name is Dave Solda and I would be happy to answer any other questions that you have. Troy's response is correct however as in order to support the default Linux mouse class, our firmware would also have to be modified to do so, which cannot be done in system. Our packet protocol maxes out at an 8 byte packet, which requires a change to the Linux standard in this case.
>
> Our goal in working with canonical was to provide something on Linux that would support multi-touch and not only have default single finger movement supported.
>
> If I am mistaken and he Linux kernel would accept this, then we can proceed to upstream, however all indications we have is that this patch would be rejected. If you (or others on from the locus alias) have any inputs, I would be happy to receive them.
>
Really you should ask yourselves:
1) What benefit do you enjoy by keeping the code out of the upstream kernel?
2) What are the benefits of having a driver for your hardware in the
upstream kernel?
If 2 > 1, then the course of action seems obvious.
Doing nothing because of some perceived impediment doesn't help anybody.
David Daney
> Dave
>
>
>
> On Nov 8, 2012, at 7:13 AM, "Troy Abercrombia" <ta@...ress.com> wrote:
>
>> Hello Kamal
>>
>> Unfortunately, We're not able to upstream the driver as it would be denied because it changes the Linux mouse structure framework.
>>
>> Thanks
>> Troy
>> -----Original Message-----
>> From: Kamal Mostafa [mailto:kamal@...onical.com]
>> Sent: Wednesday, November 07, 2012 10:32 AM
>> To: Ozan Çağlayan
>> Cc: linux-kernel@...r.kernel.org; linux-input@...r.kernel.org; dmitry.torokhov@...il.com; customercare; mario_limonciello@...l.com
>> Subject: Re: Why Cypress does not upstream its trackpad driver?
>>
>> 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@...onical.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/
>>
>
> This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.
> N�����r��y���b�X��ǧv�^�){.n�+����{����zX��.��ܨ}���Ơz�&j:+v���.����zZ+��+zf���h���~����i���z�.�w���?����&�)ߢ.f��^jǫy�m��@A�a���.0��h�.�i
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists