> Just want to copy the comments on top of enum.c here.
Yeah, I can read code and comments too, __when I have the time__.
I was simply hoping that you could speed up things by doing the analysis and
tell us exactly what process is used by usbview to compute the port number (NB:
the rest of the process is fairly close to what we do for our enum, if you look
at what each pass accomplishes. As a matter of fact, usbview was used as a
reference when crafting our enumeration)
As long as it requires 2 different API calls, that each essentially return the
same element we are interested in, albeit in a slightly different form, I don't
see how we can integrate this patch. Now, you're of course free to decide
whether you want to help us and ASMedia users further, by doing the analysis
work above, or just leave that to whichever libusb developer will get a chance
to do it, when/if they get a chance to do it.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/147#issuecomment-25197612
------------------------------------------------------------------------------
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
