On Fri, Jun 03, 2011 at 12:02:09PM +0800, Chih-Wei Huang wrote: > 2011/6/2 Thadeu Lima de Souza Cascardo <cascardo@xxxxxxxxxxxxxx>: > > 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 You should use the device capabilities, like what events it does generate. If it does generate X and Y axis events, that's the right device. Best regards, Cascardo.
Attachment:
signature.asc
Description: Digital signature
