Thanks. I don't mind the idea of not using APIs that seem to be flaky (or
rather, that hardware manufacturers appear to have overlooked) to figure out
the port number, but on the other hand, this adds a lot of code for something
that we used to get with a single API call, and for something as elementary as
getting the OS tell us which port a device is connected to. If we find that
`SPDRP_LOCATION_INFORMATION` works all the time, it would drastically simplify
the change we need to make to get a port number.
Also, we need to be careful about issuing IOCTLs to hubs. Some of these __may__
generate bus traffic, and we have a bunch of people who get very annoyed about
traffic being issued to the bus during enum, as it may disrupt ongoing
time-critical transfers.
I'll try to take a closer look at your proposal when I get a chance. Thanks
again for taking the time to investigate and submit it.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/147#issuecomment-25328384
------------------------------------------------------------------------------
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
