The proper workaround/fix is to define `DeviceInterfaceGUIDs` (with an s) as a
`REG_MULTI_SZ` in the WCID descriptor. If you do that, then the GUID of your
WCID interface will be picked up by libusbx, whereas if using
`DeviceInterfaceGUID` (without the s) it won't.
We also should try to update the Windows enumeration as per (this
e-mail)[http://libusbx.1081486.n5.nabble.com/Libusbx-devel-RFC-0-2-Add-support-for-USB-3-bulk-streams-tp1911p2029.html]
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/140#issuecomment-25328155
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
