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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4682A4E2.4020206@anagramm.de>
Date:	Wed, 27 Jun 2007 19:56:50 +0200
From:	Clemens Koller <clemens.koller@...gramm.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type
 / type->init() failed.

Hello, Dimitry!

Dmitry Torokhov schrieb:
> 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.

Yes, thank you!
I just had a look into the datasheet.
(tsc10usb_pi_e.pdf, Rev. 1.2 from November 1, 2005)
and I will need more debugging info to the dmc_tsc10_init()...

As I wrote, I am using the TSC-103 without EEPROM.
(I can add one if it's of any use.)
The PanelID is 0 (pin 3 [SEL1] is low), so it's the "first"
device on the bus.

What exact chip version and EEPROM configuration do you use?
I guess there are different firmware releases for the different
TSC-10* devices which behave... well... different. :-(

Regards,
-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ