>> So this seems like a bug in libusbx that it doesn't seem to honor the
>> synchronous API expectations in this case, as evidenced by the concatenating
>> of the
>> buffers from multiple calls. Or am I missing something?
>
> Can you try using the libusb-win32 or libusbK driver instead of WinUSB?
Hi,
On 05/27/2013 04:54 PM, Sean McBride wrote:
> On Fri, 24 May 2013 17:22:19 -0600, Nathan Hjelm said:
>
>>> My app only communicates with one particular USB device, and I don't
>> much like the idea of my process running code whenever the user happens
>> to plug in a keyboard, mouse, USB key, o
On Fri, 24 May 2013 17:22:19 -0600, Nathan Hjelm said:
>> My app only communicates with one particular USB device, and I don't
>much like the idea of my process running code whenever the user happens
>to plug in a keyboard, mouse, USB key, or other unrelated thing.
>
>The code that is running is n
Hi again,
With some help from Pete, Xiaofan as well as Nathan, I have been working on
integrating the libusb hp API work done by Nathan for 1.0.16 on top of libusbx.
The plan still is to release this as 1.2.0 within the next few weeks.
Working towards that goal I've added BOS and SS EP comp supp
