From: "Henrik Rydberg" <rydberg@euromail.se>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Richard Nauber <richard.nauber@googlemail.com>,
linux-input@vger.kernel.org
Subject: Re: [RFC] Port of hid-egalax to the unified hid-multitouch driver
Date: Tue, 8 Mar 2011 14:29:25 +0100 [thread overview]
Message-ID: <20110308132925.GA19098@polaris.bitmath.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1103081413220.19969@pobox.suse.cz>
> > This reminds me that we have to switch the other drivers to
> > hid-multitouch too.
>
> That would be nice. I don't see this really being done for the upcoming
> merge window, right Benjamin?
There has been no activity in that direction here either...
> > Actually, I was not in favor of porting this driver into hid-multitouch.
> > eGalax has two differents protocols: one for resistive technology (which
> > is compatible with hid-multitouch in its current form), and one for
> > capacitive technology (which requires the "corrupt packet length"
> > quirk).
> >
> > Apparently, according to the kernel logs the Samsung MB30 is a resistive
> > technology (correct me if I'm wrong). This means that we also need
> > testings for the capacitive one.
> >
> > I'll let the community decide whether we should include this in
> > hid-multitouch. Henrik, Jiri, any idea?
>
> Either directly hid-multitouch, or hid-multitouch-capacitive sub-module
> should be fine.
Maybe it is obvious already, but I think the patch is great. There is
really no reason to split the driver - in particular given that the
manufacturer has ensured similar behavior from both types.
Thanks,
Henrik
next prev parent reply other threads:[~2011-03-08 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 13:24 [RFC] Port of hid-egalax to the unified hid-multitouch driver Richard Nauber
2011-03-07 10:04 ` Benjamin Tissoires
2011-03-08 13:14 ` Jiri Kosina
2011-03-08 13:29 ` Henrik Rydberg [this message]
2011-03-08 15:12 ` Benjamin Tissoires
2011-03-08 15:21 ` Jiri Kosina
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=20110308132925.GA19098@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=richard.nauber@googlemail.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).