From: Cedric Sodhi <manday@gmx.net>
To: linux-input@vger.kernel.org
Subject: HID: Dead ./debug/hid/xxx/events
Date: Wed, 16 Nov 2011 10:50:30 +0100 [thread overview]
Message-ID: <20111116095030.GC3335@slate> (raw)
Hello everyone,
the context for this problem is getting the eGalax USB Touchscreen, ID
056a:0090, to work as such, as it is discussed on the linuxwacom-devel
list (see [1]).
Quickly summarized:
Adding the device as USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH5, in line with
the ..._MULTITOUCH[1-4], succeeds in thus far, as that it appears as a
HID Touchscreen. However, as of 3.1.x, clicking, id est touching "jams"
as in the click is never released.
Updating to 3.2.x-torvalds' kernel should have resolved that jamming,
but instead no clicks or releases are recognized at all.
The real problem with debugging that, though, is that
/sys/kernel/debug/hid/<eGalax>/events
remains dead, in any kernel, 3.1.x-gentoo, 3.1.x-vanilla and
3.2.x-torvalds alike.
I hope that you may have an idea as for any of the problems, especially
why there appears no output on the ./events node (the according node for
my keyboard reports events just fine).
Pasted is .config [2] for 3.2.x-torvalds and ./hid/<eGalax>/rdesc [3] on
3.2.x-torvalds.
[1]
http://sourceforge.net/mailarchive/forum.php?thread_name=CAGzDe_Y2cSMxVPm-rcNSrMsew2V5Y0vbVyhXJBFCKraq7EaZ8g@mail.gmail.com&forum_name=linuxwacom-devel
[2] http://paste.pocoo.org/show/508548/
[3] http://paste.pocoo.org/show/508550/
next reply other threads:[~2011-11-16 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 9:50 Cedric Sodhi [this message]
2011-11-16 10:17 ` HID: Dead ./debug/hid/xxx/events Benjamin Tissoires
2011-11-16 10:25 ` Cedric Sodhi
2011-11-16 13:41 ` Chris Bagwell
2011-11-16 14:55 ` Cedric Sodhi
2011-11-16 15:40 ` Cedric Sodhi
2011-11-16 16:15 ` Chris Bagwell
2011-11-16 17:01 ` Benjamin Tissoires
2011-11-16 20:48 ` Cedric Sodhi
2011-11-16 21:22 ` Benjamin Tissoires
2011-11-17 6:58 ` Cedric Sodhi
2011-11-16 21:23 ` Chris Bagwell
2011-11-17 6:59 ` Cedric Sodhi
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=20111116095030.GC3335@slate \
--to=manday@gmx.net \
--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).