Pete,
I took a quick look at the WinUSB isoc calls and they are similar in concept
but have a different structure and signature. There is also a semantic
different in that WinUSB requires an extra call to WinUsb_RegisterIsochBuffer()
and WinUsb_UnregisterIsochBuffer() while to my knowledge libusbk does not have
an equivalent, and different calls for ASAP read/writes vs scheduled.
Further, since WinUSB isoc is only available on Windows 8.1, I'm not sure
within the current libusbx framework how one would check the platform and
notify the API user that WinUSB does or does not have isoc support on the
current platform. I chose to use libusbK because it appeared to support Windows
XP and up.
Either way, the implementation of each sub API will be slightly different and
require a minor bit of specific code. I tried to emulate the patterns that
libusbx provided though and work within the existing framework as much as
possible.
I don't think a lack of WinUSB isoc support should prevent adding the libusbK
isoc support, although I would be willing to refactor the libusbK specific
components a bit further at this stage to make room for WinUSB.
I may look into doing the WinUSB isoc backend if necessary for my purposes
(better performance on Win8.1, perhaps) but we need to discuss the
implementation per above and didn't want to hold up what I've done so far.
Josh
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/164#issuecomment-30195087
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
