linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
To: Varun Wadekar <vwadekar@nvidia.com>
Cc: "USB list" <linux-input@vger.kernel.org>,
	"Harry Hong" <hhong@nvidia.com>, "Gary King" <gking@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 06:30:48 +0100	[thread overview]
Message-ID: <AANLkTike5xYAMCJKd7Lh0i4op3Z4fRDUMAOx5-s==541@mail.gmail.com> (raw)
In-Reply-To: <4D2BE29A.4060400@nvidia.com>

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

  reply	other threads:[~2011-01-11  5:31 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 [this message]
2011-01-11  5:42     ` Varun Wadekar
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='AANLkTike5xYAMCJKd7Lh0i4op3Z4fRDUMAOx5-s==541@mail.gmail.com' \
    --to=boulabiar@gmail.com \
    --cc=benjamin.tissoires@enac.fr \
    --cc=chatty@enac.fr \
    --cc=gking@nvidia.com \
    --cc=hhong@nvidia.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rydberg@euromail.se \
    --cc=vwadekar@nvidia.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).