On Tue, 1 Feb 2011, kholis wrote:
> On Mon, Jan 31, 2011 at 10:10 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > The log you created shows _some_ device doing something: Bus 002 Device
> > 013 (you mentioned it yourself in the previous email). Wasn't that the
> > Keytouch keyboard?
> >
>
> yup. Bus 002 Device 013 is Keytouch keyboard at that time.
>
> > Can you run another similar test? I want to compare the logs to see if
> > the keyboard fails in the same way as before. This time try typing a
> > line of text on the keyboard before you unplug it (after starting the
> > usbmon trace).
> >
>
> Actually at previous log i typed the keyboard too.
All right. I don't know why it seemed to work at first but not later.
> > Also, it would help if you unplug your USB mass-storage device and the
> > USB mouse before running the test, if possible.
> >
>
> Here is my another test. the scenario are:
> 1. copy the output of /sys/kernel/debug/usb/usbmon/2u to temp file
> since keyboard always on Bus 002 according to "lsusb".
> 2. unplugged the keyboard
> 3. plugged the keyboard again
> 4. type something
> 5. stop usbmon stace (Ctrl+C)
The log shows that the device failed at the same place as before: when
the system tried to retrieve its configuration string descriptor. The
patch below should work around this problem.
Alan Stern
Index: usb-2.6/drivers/usb/core/quirks.c
===================================================================
--- usb-2.6.orig/drivers/usb/core/quirks.c
+++ usb-2.6/drivers/usb/core/quirks.c
@@ -68,6 +68,10 @@ static const struct usb_device_id usb_qu
/* M-Systems Flash Disk Pioneers */
{ USB_DEVICE(0x08ec, 0x1000), .driver_info = USB_QUIRK_RESET_RESUME },
+ /* Keytouch QWERTY Panel keyboard */
+ { USB_DEVICE(0x0926, 0x3333), .driver_info =
+ USB_QUIRK_CONFIG_INTF_STRINGS },
+
/* X-Rite/Gretag-Macbeth Eye-One Pro display colorimeter */
{ USB_DEVICE(0x0971, 0x2000), .driver_info = USB_QUIRK_NO_SET_INTF },
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
