On 2012.05.28 11:53, Xiaofan Chen wrote: >> Basically, xusb will try to access string descriptor 0xEE to find out if >> the device is WCID and display the WCID data if that is the case (which >> can be done on any platform, not just Windows). It looks like trying to >> access 0xEE on Mac produces a pipe stall. > > Supposedly this will indeed be a protocol stall on the control endpoint > and will automatically be cleared for the next control transfer.
Yeah, and to answer Peter's remark, we get a stall notice on Windows as well for devices that don't have a string at 0xEE, expect it's a debug message rather than a warning. I guess we may want to also align the severity of the stall warning on OS-X (or on other platforms if we think it should be warn always). Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
