From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: linux-kernel@vger.kernel.org, "Daniel Ritz" <daniel.ritz@gmx.ch>
Subject: Re: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type / type->init() failed.
Date: Wed, 27 Jun 2007 15:19:03 -0400 [thread overview]
Message-ID: <d120d5000706271219i7a892c27j33b9476bd3d9b2ae@mail.gmail.com> (raw)
In-Reply-To: <4682A4E2.4020206@anagramm.de>
On 6/27/07, Clemens Koller <clemens.koller@anagramm.de> wrote:
> Hello, Dimitry!
>
> Dmitry Torokhov schrieb:
> > On 6/27/07, Clemens Koller <clemens.koller@anagramm.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 don't.
> I guess there are different firmware releases for the different
> TSC-10* devices which behave... well... different. :-(
>
Could be, although according to that data sheet 0x0600 is ACK for both
touchschreens with and without EEPROMs.
I think most of the changes fro USB touchscreen came in from Daniel
Ritz, let's try CCing him...
--
Dmitry
next prev parent reply other threads:[~2007-06-27 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 16:48 Clemens Koller
2007-06-27 17:04 ` Dmitry Torokhov
2007-06-27 17:56 ` Clemens Koller
2007-06-27 19:19 ` Dmitry Torokhov [this message]
2007-06-28 15:31 ` Clemens Koller
2007-06-29 8:22 ` Holger Schurig
2007-06-29 8:29 ` Holger Schurig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d120d5000706271219i7a892c27j33b9476bd3d9b2ae@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=clemens.koller@anagramm.de \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®