From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Gerhard Mack" <gmack@innerfire.net>
Cc: linux-kernel@vger.kernel.org, "Andrew Morton" <akpm@osdl.org>
Subject: Re: linux 2.6.16.16 breaks touchscreens
Date: Thu, 1 Jun 2006 15:37:18 -0400 [thread overview]
Message-ID: <d120d5000606011237x33b347a3h88847a4d7e2fc10f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605190932470.16521@mtl.rackplans.net>
On 5/19/06, Gerhard Mack <gmack@innerfire.net> wrote:
> hello,
>
> I have a touchscreen device that works on 2.6.14 but breaks on 2.6.16.
>
> The kernel is detecting the device and it is registering in
> /proc/bus/input/devices but not showing up in /dev/input
>
> dmesg:
>
> input: eGalax Inc. USB TouchController as /class/input/input0
> usbcore: registered new driver touchkitusb
> mice: PS/2 mouse device common for all mice
> ts: Compaq touchscreen protocol output
>
> /proc/bus/usb/devices:
> I: Bus=0003 Vendor=0eef Product=0001 Version=0100
> N: Name="eGalax Inc. USB TouchController"
> P: Phys=/input0
> S: Sysfs=/class/input/input0
> H: Handlers=mouse0 event0 ts0
> B: EV=b
> B: KEY=400 0 0 0 0 0 0 0 0 0 0
> B: ABS=3
>
> kiosk10:/dev/input# ls -l
> total 0
> crw-rw---- 1 root root 13, 63 2006-05-19 09:06 mice
> crw-rw---- 1 root root 10, 223 2006-05-19 09:06 uinput
>
Gerhard,
Were you able to resolve this issue? It looks like your device is
properly recognized by the kernel and I see that "ts" handler was
bound to it so the only thing missingis the device node. I am pretty
sure it is udev issue.
--
Dmitry
prev parent reply other threads:[~2006-06-01 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 13:38 Gerhard Mack
2006-06-01 19:37 ` Dmitry Torokhov [this message]
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=d120d5000606011237x33b347a3h88847a4d7e2fc10f@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=gmack@innerfire.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®