lkml.org 
[lkml]   [2007]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type / type->init() failed.
Date
> 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.

No, I don't think so. Not in it's current form.


Currently, usbtouchscreen doesn't have any means to initialize an
EEPROM. And in the absence of such a possibility, you need other
means to accomplish your task. The current behavior provides you
with this "plan b":

If you set the rate and that doesn't work because no EEPROM is
there, the driver fails. While doing it, it will release the
device.

This brings in the opportunity to access the touchscreen
controller from userspace, e.g. with libusb, and write the
EEPROM. After this, reboot, and be happy. Because now the device
would act correctly on the "set rate" command and would be
usable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-29 10:33    [W:0.274 / U:0.716 seconds]
©2003-2014 Jasper Spaans. Advertise on this site