> 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
> 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).
The same is done by my hardware guy. In my case, there is no
EEPROM attached ... but he didn't pull up this pin up, until
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).
The same is done by my hardware guy. In my case, there is no
EEPROM attached ... but he didn't pull up this pin up, until I
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
Hello, Dimitry!
Dmitry Torokhov schrieb:
Hi,
On 6/27/07, Clemens Koller <[EMAIL PROTECTED]> 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
Hello, Dimitry!
Dmitry Torokhov schrieb:
Hi,
On 6/27/07, Clemens Koller [EMAIL PROTECTED] 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
On 6/27/07, Clemens Koller <[EMAIL PROTECTED]> wrote:
Hello, Dimitry!
Dmitry Torokhov schrieb:
> On 6/27/07, Clemens Koller <[EMAIL PROTECTED]> wrote:
>> drivers/usb/input/usbtouchscreen.c: usbtouch_probe - type->init()
>> failed, err: -19
>
> dmc_tsc10_init() returns -ENODEV (-19) when device
Hello, Dimitry!
Dmitry Torokhov schrieb:
On 6/27/07, Clemens Koller <[EMAIL PROTECTED]> 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
Hi,
On 6/27/07, Clemens Koller <[EMAIL PROTECTED]> 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
Hello, again!
Well, with lots of debugging enabled, I got to some more details about the
non working DMC TSC-10 USB Touchscreen:
(see also: http://lkml.org/lkml/2007/6/26/228 )
Whenever I plug in the TSC-10 I get the following output
hub 3-0:1.0: state 7 ports 4 chg evt 0004
ehci_hcd
Hello, again!
Well, with lots of debugging enabled, I got to some more details about the
non working DMC TSC-10 USB Touchscreen:
(see also: http://lkml.org/lkml/2007/6/26/228 )
Whenever I plug in the TSC-10 I get the following output
hub 3-0:1.0: state 7 ports 4 chg evt 0004
ehci_hcd
Hi,
On 6/27/07, Clemens Koller [EMAIL PROTECTED] 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
Hello, Dimitry!
Dmitry Torokhov schrieb:
On 6/27/07, Clemens Koller [EMAIL PROTECTED] 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
On 6/27/07, Clemens Koller [EMAIL PROTECTED] wrote:
Hello, Dimitry!
Dmitry Torokhov schrieb:
On 6/27/07, Clemens Koller [EMAIL PROTECTED] wrote:
drivers/usb/input/usbtouchscreen.c: usbtouch_probe - type-init()
failed, err: -19
dmc_tsc10_init() returns -ENODEV (-19) when device responds
14 matches
Mail list logo
