And what happens if it's not in the `Port_#xxxx_Hub_#yyyy` format? Do we set
all the ports from that hub as port 0?
Also, what exactly does the ASMedia driver return as a string for this query?
>From what I'm seeing, your intent is to set the port number to zero, which is
>invalid, in the case of poking anything on an ASMedia connected hub, and
>pretend that everything's copacetic.
Well, with the code less than 5 lines above pretty much saying "if we can't
retrieve valid port data, then we eliminate the device", it kind of looks like
you are trying to hide your ASMedia annoyance (most likely a driver bug that
ASMedia should be the ones to fix) under the rug. As such, I don't think this
is something we can really go with: displacing the problem, rather than solving
it, will only end up impacting other users. This may sound like an acceptable
solution to you, but for everyone who expects consistency with how we assign
port numbers, and/or uniquely identify a device, not so much...
My other questions to you then are:
- Have you contacted ASMedia support and asked them if they are aware that
their driver is not compliant with Microsoft's API and breaks USB applications?
What did they say?
- Have you tried upgrading your ASMedia drivers to the latest version?
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/147#issuecomment-25055126
------------------------------------------------------------------------------
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
