From: Benjamin Tissoires <benjamin.tissoires@gmail.com>
To: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: Baantoo multi-touch screen trouble
Date: Fri, 13 Apr 2012 11:21:22 +0200 [thread overview]
Message-ID: <CAN+gG=HBTO4UvEQ1SVMS1sicHbBDaTP83E9cTUm1M3c9KSechA@mail.gmail.com> (raw)
In-Reply-To: <201204130902.51885.tvrtko.ursulin@onelan.co.uk>
Hi,
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.
If it's not working, then we may need the full report descriptors
(without the ** UNAVAILABLE **). You can do that by using the script
there: http://lii-enac.fr/en/architecture/linux-input/multitouch-howto.html#report
Cheers,
Benjamin
On Fri, Apr 13, 2012 at 10:02, Tvrtko Ursulin
<tvrtko.ursulin@onelan.co.uk> wrote:
> On Thursday 12 Apr 2012 17:05:34 Benjamin Tissoires wrote:
>> Hi Tvrtko,
>>
>> I misread your first mail, sorry for that. I did not saw that your
>> device was a Hid one detected as a multitouch one. Under 3.3, just do:
>> $ sudo modprobe hid-multitouch
>>
>> And the device should be handled by hid-multitouch.
>>
>> The 3.3 kernel, detects that your device should be handled by
>> hid-multitouch, but it does not load it automatically. You may add
>> this module in the configuration file.
>
> Unfortunately nothing interesting happened with hid-multitouch loaded. Nonew
> kernel messages, no devices claimed/created.
>
> Are there any tools (couldn't find any) which can probe/analyze this device
> from userspace? Or something that would explain why it works better with
> earlier kernels?
>
> Tvrtko
next prev parent reply other threads:[~2012-04-13 9:21 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 [this message]
2012-04-13 9:33 ` Tvrtko Ursulin
2012-04-13 12:42 ` Jiri Kosina
2012-04-13 13:30 ` Tvrtko Ursulin
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='CAN+gG=HBTO4UvEQ1SVMS1sicHbBDaTP83E9cTUm1M3c9KSechA@mail.gmail.com' \
--to=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=tvrtko.ursulin@onelan.co.uk \
/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).