On Thursday 22 July 2004 05:00 pm, Alan Stern wrote: > > By the way, do you know what the SE0 entries in that report mean? Do they > indicate a port reset?
My understanding is that the SE0 state is a port reset (D- = D+ = 0). > If they do, I would expect the second reset to > erase the device's memory of the initial 64-byte get_descriptor. Fresh > from the reset, the device would think the first transaction it got was > the set_address. But if that were true, then the device ought to work > under Linux where the first transaction really _is_ a set_address. It looks like the windows driver performs the initial get_descriptor with a maximum to determine the actual descriptor size. Then it resets the device and uses the actual length. This particluar device appears not to work with a request of less than actual length. Linux always requests 8, windows requests actual. I guess I'm surprised no one else has seen similar problems with other devices. Kyle. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
