g...@novadsp.com wrote:
> Once I have opened a device using LibUsbX, is there a
> synchronization handle I can pend on whilst waiting for the
> peripheral device to write back to the host?
The device is not allowed to transmit to the host before your
application requests data.
> // open device e
My USB handler thread(s) listen on other synchronization handles for
clean shutdown etc. Once I have opened a device using LibUsbX, is there
a synchronization handle I can pend on whilst waiting for the peripheral
device to write back to the host?
i.e.
// open device etc.
libusb_open_device_wi
On 2012.08.08 14:58, Markus wrote:
> I just applied your patch to 1.0.12 and can't see any problems
> with it. From a number of simple tests, it looks as if it
> behaves well.
Great. Glad to hear I haven't broken anything... ;)
> I'd however still keep a decent path length for the file name
> (bi
Hi Pete,
sorry for the late reply, I've been away for the last week.
I just applied your patch to 1.0.12 and can't see any problems
with it. From a number of simple tests, it looks as if it
behaves well.
I'd however still keep a decent path length for the file name
(binary_name), as 256 is no
On 2012.08.08 01:15, Peter Stuge wrote:
> I look forward to some testing! Even if it comes at the cost of the
> libusbK DLL it's still very nice that libusb-1.0 code can be used
> with the libusb-win32 driver.
The use of the K DLL shouldn't be a surprise at this stage.
It has announced as the meth
