Thanks very much for the feedback.
2013/9/18 mcuee <notificati...@github.com>
> I do not have a test setup to effectively testing this patch. We also know
> that this is a work around for some 3rd party xhci controller
> driver/firmware bugs where the new driver may already fix the issues.
>
> Ref:
> http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Reading-device-descriptor-and-config-descriptor-from-WinUsb-td1806.html
>
> It does seem to create some problems based on my simple test.
>
> $ ./examples/listdevs.exe
> libusbx: warning [cache_device_descriptors] could not get node connection
> inform
> ation for device '\\.\USB#VID_046D&PID_C52F#6&28E0277E&0&1': [87] The
> parameter
> is incorrect.
>
> Did you also get this warning prior to the change?
>
> libusbx: error [get_conn_info_ex] program assertion failed: device address
> colli
> sion with root hub
>
>
I'm aware of this, and left a comment describing it (marked
TODO(juanlang)). There's no way I know of to get the device address via
WinUSB. I can lie about the address with a different value and avoid this
error. That's probably better, because it'd cause fewer confused user
reports. The question is, how crucial is an accurate topology? In my case,
being able to open a device is important, and knowing its bus-relative
address is not.
Thanks,
--Juan
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
