From: Chih-Wei Huang <cwhuang@android-x86.org>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-input@vger.kernel.org
Subject: Re: ET1602 Touchscreen doesn't work
Date: Fri, 3 Jun 2011 12:02:09 +0800 [thread overview]
Message-ID: <BANLkTimen=6OXOTww48CAn-ULaRVP_7zUw@mail.gmail.com> (raw)
In-Reply-To: <20110602144146.GB3508@nautilus.holoscopio.com>
2011/6/2 Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>:
> It depends on your userspace. It should work properly with X.org drivers
> evdev and evtouch. Are you trying this with Android?
Yes, exactly.
Actually the touchscreen is detected, but it appears twice:
[ 3.408922] input: HID TOUCH HID Touch Panel as
/devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input6
[ 3.412345] input: HID TOUCH HID Touch Panel as
/devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input7
[ 3.415386] generic-usb 0003:1BFD:1688.0003: input: USB HID v1.01
Mouse [HID TOUCH HID Touch Panel] on usb-0000:00:1d.3-2/input0
I tried to use getevent, a debug tool of android,
to get the touch events.
I found touch events appear in /dev/event7,
not in /dev/event6.
Is it the desired behavior?
But the Android framework seems only detect
/dev/event6 and ignore /dev/event7,
probably because they have the same name.
Any suggestion how to solve the problem?
Regards,
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
next prev parent reply other threads:[~2011-06-03 4:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikX9njth-jP6PpQuwL9sTUciu1nQA@mail.gmail.com>
2011-06-02 14:41 ` ET1602 Touchscreen doesn't work Thadeu Lima de Souza Cascardo
2011-06-03 4:02 ` Chih-Wei Huang [this message]
2011-06-03 12:44 ` Thadeu Lima de Souza Cascardo
2011-06-08 10:33 ` Chih-Wei Huang
2011-06-08 11:31 ` Benjamin Tissoires
2011-06-08 12:57 ` Thadeu Lima de Souza Cascardo
2011-06-08 14:56 ` Chih-Wei Huang
2011-06-08 15:31 ` Thadeu Lima de Souza Cascardo
2011-06-09 11:26 ` Chih-Wei Huang
2011-06-09 13:39 ` Thadeu Lima de Souza Cascardo
2011-06-10 2:23 ` Chih-Wei Huang
2011-06-13 15:09 ` Thadeu Lima de Souza Cascardo
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='BANLkTimen=6OXOTww48CAn-ULaRVP_7zUw@mail.gmail.com' \
--to=cwhuang@android-x86.org \
--cc=cascardo@holoscopio.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).