From: William Sherman <shermanw@indiana.edu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
Linux Input <linux-input@vger.kernel.org>,
William Sherman <shermanw@indiana.edu>
Subject: Re: usbhid: HP LD4200tm touchscreen ALMOST works
Date: Tue, 02 Nov 2010 09:46:21 -0400 [thread overview]
Message-ID: <4CD0162D.1000800@indiana.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.1011011717460.15851@pobox.suse.cz>
On 11/1/10 5:22 PM, Jiri Kosina wrote:
> On Mon, 1 Nov 2010, Dmitry Torokhov wrote:
>
>>> I'm looking to dig into the usbhid driver code to get me the last
>>> mile and get my HP LD4200tm touchscreen working on my Linux system.
>>> [NOTE: I posted about this elsewhere, but as I think about it more,
>>> this is more of a linux-kernel issue than anything else, so I'm
>>> reprising that note here.]
>>
>> I think you'll have better luck on linux-input...
>
> Thanks for CC, Dmitry.
Yes, thanks from me too for pointing this thread in the right direction.
I also sent a revised (updated) post to the linux-kernel list, but was
not aware of the linux-input list.
> Thanks a lot for the detailed analysis. What would actually be interesting
> to see would be the HID debugfs output. Namely
>
> 1) mount debugfs
> 2) cat /sys/kernel/debug/<device>/rdesc
> 3) obtain output of /sys/kernel/debug/<device>/events and annotate it as
> you did for your previous output (i.e. "this happens when I do one-finger
> move", "this happens when I do two-finger trick to make it work").
>
> This way, it'd be much easier to see what is actually hapenning on HID
> level.
Great. I will do that as soon as I can -- which is when I arrive at
SuperComputing to setup our system. The display (our only one) is currently
on a truck bound for New Orleans.
In the meantime, I wrote a very simple application that parses the
data directly from /dev/hidrawN, does a simple parse, and then
creates X events with the Xtest API. Of course, I'm only doing
single touch, since that's all I need for the moment.
I also have a Dell SX2210T touch screen with the NextWindow interface.
We made some partial progress on our Ubuntu 10.10 system with the nwfermi
driver, but again, not quite all the way -- of course now that computer
is on the road, and I'm not having as much luck with that touchscreen
on my Fedora 13 system.
> Thanks,
Thank you both, and more to come,
Bill
--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technologies Inst
Indiana University
shermanw@indiana.edu
prev parent reply other threads:[~2010-11-02 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 23:48 usbhid: HP LD4200tm touchscreen ALMOST works William Sherman
2010-11-01 21:14 ` Dmitry Torokhov
2010-11-01 21:22 ` Jiri Kosina
2010-11-02 13:46 ` William Sherman [this message]
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=4CD0162D.1000800@indiana.edu \
--to=shermanw@indiana.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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