Hello,

I'm trying to get touch working in Linux on a new Sony all-in-one VAIO touch system:

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Sony Corporation
Product Name: VPCL114FX
Version: C6U1957S
Serial Number: 27503932-3000406
UUID: FB1F4B20-A8C3-11DE-8D19-0024BE4424CA
Wake-up Type: Power Switch
SKU Number: N/A
Family: VAIO

Linux 2.6.27.8 #1 SMP i686 Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux

They are using NextWindow hardware:

dmesg | grep NextWindow
hiddev97: USB HID v1.11 Device [NextWindow Touchscreen] on usb-0000:00:1a.2-2

My problem is that linux is not creating a /dev/input/event* device for this device.

cat /proc/bus/usb/devices shows:

T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1926 ProdID=0065 Rev= 0.01
S: Manufacturer=NextWindow
S: Product=Touchscreen
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=82(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
E: Ad=02(O) Atr=03(Int.) MxPS= 64 Ivl=1ms

cat /proc/bus/input/devices shows:

I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0003 Vendor=054c Product=0374 Version=0111
N: Name="Sony RF Receiver"
P: Phys=usb-0000:00:1a.0-1/input0
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=kbd event2 js0
B: EV=12001f
B: KEY=837fff 2c3027 bf004444 0 c000000 ff 10c04 a27c007 ffa67bfa d941dfff febeffdf ffefffff ffffffff fffffffe
B: REL=40
B: ABS=ffffff01 701ff
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=054c Product=0374 Version=0111
N: Name="Sony RF Receiver"
P: Phys=usb-0000:00:1a.0-1/input1
S: Sysfs=/class/input/input3
U: Uniq=
H: Handlers=mouse0 event3
B: EV=17
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=140
B: MSC=10

I: Bus=0003 Vendor=05ca Product=18b5 Version=0402
N: Name="UVC Camera (05ca:18b5)"
P: Phys=usb-0000:00:1a.7-3
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=event4
B: EV=3
B: KEY=1 0 0 0 0 0 0 0 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=40001
B: SND=6

So my question is, why is the /dev/input/event* interface not being created, and how can I fix that?

First thing, what distro are you using?
Second, not to be an ass but, did you use google.com/linux or the forum site dedicated to the distro you are using?

0 members found this post helpful.

I'm using SLAX 6.0.9, which is derived from Slackware 12.2.

I didn't think this would be a distro-specific issue. My question is a little more basic:

What in the kernel decides whether to create an input/event device for a piece of hardware? Is it something that the device "says" when it is queried, or is there a table of USB IDs someplace?

Alternately, I'm told that this is a NextWindow 1950 device. Is it possible that someone has written an X Input Driver for that, or that there is an existing X Input Driver that might be adapted to work with it?

-Joshua

I cannot get the touchscreen working either; the issue is not the event (I got that) but the system does not recognize the touchscreen as an input device (i.e does not show-up when cat /proc/bus/input/devices);
Is there a file listing all input devices?

Yes, the problem is that no driver exist for this device.
I've the dell screen SX2210T from NextWindow, (VendorId: 0x1926, ProdId: 0x0064), and only work on Window Seven.

I've been able to start reverse engineering on this, still hard to do for signal analysis... I pretty you got the same type of screen (exactly the same output and analysis behavior of lsusb...).

More info here :
SX2210T analysis part 1,
part 2

More info here :
SX2210T analysis part 1,
part 2

txprog, thanks for the update. I'm also in touch with NextWindow, and I'll let you know if I get anywhere.

All I know so far is what you already found: the 1950 is *not* an HID compliant device. So it needs a custom driver.

That's what i'm actually trying to do But i'm stuck with this signal analysis problem :/

Now I am confused as to why a new driver has to be written??
NextWindow site gives installation procedures in Linux (http://www.nextwindow.com/nextwindow...linux_2.html);
I followed the directions but no luck; so why do we need a need driver?

Because that page is out of date. The new 1950 device is not HID compliant, and therefore does not work with that driver.

Any news on the driver...

Guys wanted to check , if there is any news on the NextWindow 1950 Touch Screen Linux Driver

Some people deep inside NextWindow told me that they expect to have a new driver for Linux "mid-year". Until then, I guess we just have to wait.

Hey guys,
I was wondering if there was an update to this at all?
Thanks,
~Eric