2013/7/25 Tim Roberts <t...@probo.com>
> Juan Lang wrote:
> >
> > I've got a little test program that I'm running against a device I
> > have, which is supported by the winusb driver. Here's my little test
> > program:
> > ...
> > The program produces the following output when my device is inserted
> > into a USB 3.0 port:
> > ...
> > [ 0.069014] [00001f10] libusbx: debug [windows_get_device_list]
> > allocating new device for session [19D]
> > [ 0.070014] [00001f10] libusbx: error [init_device] device
> > '\\.\USB#VID_1050&PID_0211#6&BB8218&0&3' is no longer connected!
> > ...
> > Naturally it succeeds when the device is inserted in a USB 2.0 port.
> > I've verified the problem on an HP z420 with a TI USB 3.0
> > controller/drivers, and on a ThinkPad T430 with Intel-provided
> > controller/drivers.
> >
> > Any idea what gives?
>
> My guess is that your device violates the USB 3.0 specs. There are lots
> of devices that implemented the USB spec sloppily. Many of them got
> away with it because of forgiving USB 2 implementations, but USB 3 is
> stricter.
>
Thanks, that's helpful! Any common flaws you know about?
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
