From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Solda <dso@cypress.com>
Cc: "Troy Abercrombia" <ta@cypress.com>,
"Kamal Mostafa" <kamal@canonical.com>,
"Ozan Çağlayan" <ozancag@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
customercare <customercare@cypress.com>,
"mario_limonciello@dell.com" <mario_limonciello@dell.com>
Subject: Re: Why Cypress does not upstream its trackpad driver?
Date: Wed, 07 Nov 2012 16:15:49 -0800 [thread overview]
Message-ID: <2208882.BvOrfBvj6F@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <EE629F2C-DD83-403C-AD73-E9ED966EEA91@cypress.com>
Hi David,
On Wednesday, November 07, 2012 06:30:11 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.
I am unable to parse this... I do not believe anyone asks you to change
your firmware and if your protocol needs 8 bytes to transmit device state -
that's fine.
> 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.
This really depends on whether the changes to the psmouse framework make
sense or not. Please start submitting patches for review/discussion and
we can go from there.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-11-08 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 22:47 Ozan Çağlayan
2012-11-07 18:32 ` Kamal Mostafa
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 [this message]
2012-11-08 0:26 ` David Solda
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=2208882.BvOrfBvj6F@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=customercare@cypress.com \
--cc=dso@cypress.com \
--cc=kamal@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=ozancag@gmail.com \
--cc=ta@cypress.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
all inboxes | Powered by JetHome®