From: Varun Wadekar <vwadekar@nvidia.com>
To: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
Cc: "USB list" <linux-input@vger.kernel.org>,
"Harry Hong" <hhong@nvidia.com>,
"Bharat Nihalani" <bnihalani@nvidia.com>,
"Henrik Rydberg" <rydberg@euromail.se>,
"Benjamin Tissoires" <benjamin.tissoires@enac.fr>,
"Stéphane Chatty" <chatty@enac.fr>
Subject: Re: NVidia Multitouch driver.
Date: Tue, 11 Jan 2011 11:12:05 +0530 [thread overview]
Message-ID: <4D2BEDAD.5050604@nvidia.com> (raw)
In-Reply-To: <AANLkTike5xYAMCJKd7Lh0i4op3Z4fRDUMAOx5-s==541@mail.gmail.com>
Got it. I will try to get these changes pushed upstream.
Support for multiple fingers is completely touch panel driven. We have
successfully verified
than 10 fingers also work fine on Android with another touch panel.
On Tuesday 11 January 2011 11:00 AM, Mohamed Ikbel Boulabiar wrote:
> On Tue, Jan 11, 2011 at 5:54 AM, Varun Wadekar <vwadekar@nvidia.com> wrote:
>> Do you mean to say there are certain things missing in the touch driver?
>> What do you mean by the last linux kernel?
> I have found that patch by chance because I haven't seen it sent to
> linux-input ml (which what is the std)
> I just want it to get pushed to the mainline linux kernel as it is the
> upstream of all linux distributions and for the android linux kernel
> tree itself.
>
> I just don't like to see only android getting drivers patches as it
> can be seen as an action of forking the main kernel.
>
> You can rebase the patch to the last tree and get help and feedback
> from other developers for its integration. Company support of its own
> drivers is very appreciated here.
>
>
> And when analyzing the code I got a question. Does the nvodm hw
> supports only 2 fingers or it's only caused by android limitation ?
> Can the hw report more than 2 fingers ? (4 for example)
>
> Thanks
>
> i
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2011-01-11 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 23:41 NVidia Multitouch driver Mohamed Ikbel Boulabiar
2011-01-11 4:54 ` Varun Wadekar
2011-01-11 5:30 ` Mohamed Ikbel Boulabiar
2011-01-11 5:42 ` Varun Wadekar [this message]
2011-01-11 8:19 ` Stéphane Chatty
2011-01-11 14:59 ` Mohamed Ikbel Boulabiar
2011-01-12 4:12 ` Varun Wadekar
2011-01-12 4:15 ` Harry Hong
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=4D2BEDAD.5050604@nvidia.com \
--to=vwadekar@nvidia.com \
--cc=benjamin.tissoires@enac.fr \
--cc=bnihalani@nvidia.com \
--cc=boulabiar@gmail.com \
--cc=chatty@enac.fr \
--cc=hhong@nvidia.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).