From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: Baantoo multi-touch screen trouble
Date: Fri, 13 Apr 2012 14:30:24 +0100 [thread overview]
Message-ID: <201204131430.24672.tvrtko.ursulin@onelan.co.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1204131442050.16373@pobox.suse.cz>
On Friday 13 Apr 2012 13:42:24 Jiri Kosina wrote:
> On Fri, 13 Apr 2012, Tvrtko Ursulin wrote:
> > > Oops, I think I assumed that the features that will come in 3.4 are
> > > already in 3.3... sorry.
> > >
> > > Once hid-multitouch is loaded, you have to manually tell him to handle
> > > your device:
> > > # echo 3 2453 0100 0 >
> > > /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
> > >
> > > That should do the trick.
> >
> > Yep, that makes it work.
> >
> > Thanks for your help!
> >
> > If you would want to have any additional data about this panel just
> > shout, I will have access to it for a couple of more days.
>
> Guys, who of you is going to send me patch adding the device ID into
> in-kernel list?
It is unlikely to be me unless someone explains to me in detail what needs to
be done, at which point it is probably quicker for that person to do it. I for
example don't even understand why this, allegedly HID Multitouch class
compliant, device needs explicit adding? Is it not compliant after all? Is it
that multiple HID devices it exposes a non-standard thing? Does it then need a
vendor specific class (looking at hid-multitouch.c). Sorry this whole area is
just new and unknown to me.
Tvrtko
next prev parent reply other threads:[~2012-04-13 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 15:29 Baantoo multi-touch screen trouble Tvrtko Ursulin
2012-04-12 14:47 ` Tvrtko Ursulin
2012-04-12 16:05 ` Benjamin Tissoires
2012-04-13 8:02 ` Tvrtko Ursulin
2012-04-13 9:21 ` Benjamin Tissoires
2012-04-13 9:33 ` Tvrtko Ursulin
2012-04-13 12:42 ` Jiri Kosina
2012-04-13 13:30 ` Tvrtko Ursulin [this message]
2012-04-17 9:07 ` Jiri Kosina
2012-04-17 12:12 ` Tvrtko Ursulin
2012-04-17 12:19 ` 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=201204131430.24672.tvrtko.ursulin@onelan.co.uk \
--to=tvrtko.ursulin@onelan.co.uk \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
/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).