linux 2.6.16.16 breaks touchscreens

linux 2.6.16.16 breaks touchscreens

[Gerhard Mack]

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 Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

Re: linux 2.6.16.16 breaks touchscreens

[Dmitry Torokhov]

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