linux-kernel - Re: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type / type->init() failed.

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]

Date:	Thu, 28 Jun 2007 17:31:16 +0200
From:	Clemens Koller <clemens.koller@...gramm.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	linux-kernel@...r.kernel.org, daniel.ritz@....ch,
	hs4233@...l.mn-solutions.de
Subject: Re: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type
 / type->init() failed.

Hello, Dimitry!

Dmitry Torokhov schrieb:
> Hi,
> 
> On 6/27/07, Clemens Koller <clemens.koller@...gramm.de> wrote:
>> drivers/usb/input/usbtouchscreen.c: usbtouch_probe - type->init() 
>> failed, err: -19
> 
> dmc_tsc10_init() returns -ENODEV (-19) when device responds with
> something other than 0x06 0x00 to the "reset" and "set rate" commands.
> It would be interesting to see what your touchscreen responses are.

I found the problem:
After the reset, I got a 0x06 0x00 back, which is fine.

But when the driver sets the coordinate output rate, the TSC-103
answered 0x15 0x01 which means that the TSC-10 is used with an
EEPROM but the EEPROM data is empty (which is correct).

In that case the driver should at least continue to allow
initialization of the EEPROM later on. But as we don't have the
infrastructure to write the calibration data back to EEPROM, only
touch screen manufacturers which want to use the EEPROM will run into
that problem...

The same is true if there is no EEPROM present but the EEPROM is enabled.
Anyway, I disabled my EEPROM by pulling the SEL4 pin high because I don't
need/want it (yet).

So, it *works for me* but just for future reference:
The DMC TSC-10 driver doesn't start, when it has an empty (new)
EEPROM attached.

I started to do some more error handling, but it's propably not
worth doing so if the driver(s) has only limited functionality (and
no userspace app using it).

Thank you,
-- 
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
-
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/