linux-kernel - Re: [PATCH] input: Add support for eGalax TouchKit USB touchscreen used on HP tx1305us

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200806281757.48201.daniel.ritz-ml@swissonline.ch>
Date:	Sat, 28 Jun 2008 17:57:47 +0200
From:	Daniel Ritz <daniel.ritz-ml@...ssonline.ch>
To:	Alastair Bridgewater <nyef@...phacker.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH] input: Add support for eGalax TouchKit USB touchscreen used on HP tx1305us

On Saturday 28 June 2008 17:19:16 Daniel Ritz wrote:
> hi
> 
> > The eGalax touchscreen used in the HP tx1305us tablet PC (and presumably 
> > the rest of the tx1000 series) uses a different format for events from 
> > the device than the existing driver supports.
> > 
> is there more information available? datasheets? drivers?
> 
> > Add a new device description and interrupt packet handler for the 
> > touchscreen used in the tx1305us, claiming the USB device ID for the 
> > device that this patch was tested with from the older eGalax device code.
> >
> NAK. you cannot change device IDs currently used to some new code.
> this will break most eGalax setups as the device ID 0x0eef,0x0001 is used
> in most of them, including the one i have..
> 
> you'll need to find a way to distinguish the screens. as a starting point
> i attached an lsusb -vvv output from my screen...
> 

reading the latest driver guide and programming guide from eGalax (now EETI btw.
www.eeti.com.tw ) it turns out that the newer devices should support the HID
format and report with that by default. those newer screens are handled by the
'usbhid' driver. have you tried loading that one before usbtouchscreen?

can you give an lsusb -vvv output?

in case the usbhid driver does not work, it's possible to put the touchscreen
into the non-HID operating mode and have to current code work again..it's easy
to code...but please try usbhid first...

rgds
-daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/