Jonas Malaco

> See my previous comment, I already explained why this happens and the fix. @RyanHope Thanks for chipping in, but you previously reported va_list + ctypes problems only on 32-bit...

Related: libusb/libusb#735 ("Document that libusb_set_option may also return NOT_FOUND")

@jonoboy9 > Should I delete the libusbK driver so as to reinstall the previous driver. I am not too strong with device divers. I'm honestly not very familiar with UsbDk,...

@copslock Since libusb0, libusbk and libusbK are extensively overloaded terms, I unfortunately have no idea what you meant. Also, do you have a reference you can link to?

@copslock > [...] There are also reasons for _not_ installing the libusbK driver, and instead use WInUSB or even the Generic HID Driver on Windows. As there are reasons for...

This seems reasonable. Besides ctypes bindings for the [`libusb_wrap_sys_device`](http://libusb.sourceforge.net/api-1.0/group__libusb__dev.html#ga98f783e115ceff4eaf88a60e6439563c) ([added in libusb 1.0.23](https://github.com/libusb/libusb/blob/1e9d26a753a741bfdb0769b4c895697d16edcc27/ChangeLog#L18)) and [`libusb_get_device`](http://libusb.sourceforge.net/api-1.0/group__libusb__dev.html#gafe70b8a797893d4d16985980acec956a) APIs, I think we should have a PyUSB interface that abstracts these details. Of the...

Since we generally only have a single LibUSB instance per process, I'm reluctant to simply expose that functionality: one caller (say, in one of your dependencies) could easily break expectations...

@mcuee I definitively need to build/get a test device for myself... could you suggest a device and setup that's easy to configure for this?

Thanks @mcuee , I'll look into these.

Hi @mrnuke, Do you think you can help me with this? You could start by adding the [additonal libusb async functions](http://libusb.sourceforge.net/api-1.0/group__libusb__asyncio.html) to the [`libusb1`](https://github.com/pyusb/pyusb/blob/master/usb/backend/libusb1.py) backend. --- I still don't have...