[oe] Problems touchscreen on CM-X270

[Mike Rapoport]

Hi,

Henk Geraads wrote:
> Hi,
> 
> I did enable the event debuging in the kernel, when i touch the touchscreen i've got:
> 
> system log:
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 3, Code: 0, Value: 354
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 3, Code: 1, Value: 479
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 228
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 0
> 	<7>evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0 
> 
> Why is the device string <NULL>, in case of the mouse is the correct mouse specified.

The UCB1400 driver does not set dev->phys, so that's why you see <NULL> in evbug
reports.
Try "hexdump /dev/input/eventX" and touch the touchscreen

> Part of the kernel bootmessages indicating that there is a touchscreen:
> 	input: Logitech USB-PS/2 Optical Mouse as /class/input/input0
> 	input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-pxa27x-1
> 	usbcore: registered new interface driver usbhid
> 	drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> 	Advanced Linux Sound Architecture Driver Version 1.0.14 (Fri Jul 20 09:12:58 2007 UTC).
> 	pxa2xx_ac97_reset: cold reset timeout (GSR=0x0)
> 	input: UCB1400 touchscreen interface as /class/input/input1
> 	ALSA device list:
>   #0: pxa2xx-ac97 (Philips UCB1400)
> 
> Thanks for any remarks!
> 
> Best regards,
> 
> Henk
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

-- 
Sincerely yours,
Mike.