Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Henk Geraads" <linux@hf-electronics.com>
To: <openembedded-devel@openembedded.org>
Subject: Problems touchscreen on CM-X270
Date: Mon, 3 Nov 2008 07:46:21 +0100	[thread overview]
Message-ID: <NGBBLNEOGLJIIJKLFLPFMECBDKAA.linux@hf-electronics.com> (raw)

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.

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





             reply	other threads:[~2008-11-03  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  6:46 Henk Geraads [this message]
2008-11-03 14:31 ` Problems touchscreen on CM-X270 Mike Rapoport

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=NGBBLNEOGLJIIJKLFLPFMECBDKAA.linux@hf-electronics.com \
    --to=linux@hf-electronics.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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