On Mon, 4 Jul 2005, jon wrote:
> OK Here is the new DMSG output with the unit connected
This shows VMware sending three messages to the device, which might be
enough to get it working properly. Those three messages are:
Get-Descriptor request for string descriptor 0, length 4
(i.e., get the default language code)
Get-Descriptor request for string descriptor 1, length 514 (?)
Get-Descriptor request for string descriptor 2, length 514 (?)
Presumably those last two requests are attempts to fetch the
Manufacturer and Product strings. They didn't work, maybe because of the
peculiar lengths or maybe because they used the wrong descriptor index
numbers. (lsusb -v will show what the correct index numbers are, and
evidently Linux was able to read the strings okay because they showed up
in your /proc/bus/usb/devices file.)
You can see those requests near the end of the log file you sent. Look
for the three sections that start with a line saying:
usb 2-1: usbdev_ioctl: CONTROL
Perhaps if you send equivalent requests at the start of your driver, the
device will start working.
Alan Stern
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
