Since this issue will only affect very few users and there is a workaround (to
use Zadig), I think this is not a high priority issue to debug and fix.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/140#issuecomment-24635001---
On Tue, Sep 17, 2013 at 2:45 PM, Ramon Zambelli
wrote:
>> Also note that there exists limitations with regards to using WinUSB when
>> accessing interfaces using LIBUSB_RECIPIENT_INTERFACE
>> See
>> https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-Known_Restrictions
>
> From the linkj
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-RFC-0-2-Add-support-for-USB-3-bulk-streams-td1911i20.html#a1937
Under Windows, libusbx fails to access WCID interface of a USB composite device
when using the Windows 7/8 built-in WinUSB driver (with system winusb.inf).
When using Zadig to
Hi Xiaofan,
My bad. I switched to an older branch to look at something else and
thought I had switched back to head afterwards. I see now looking through
the bash history that I mis-typed the checkout command on the return trip
and didn't catch it.
Yes, head appears to build correctly without t
'dev' ptr used ("DEVICE_CTX(dev)") before it virified against
NULL
You can merge this Pull Request by running:
git pull https://github.com/maksqwe/libusbx master
Or you can view, comment on it, or merge it online at:
https://github.com/libusbx/libusbx/pull/139
-- Commit Summary --
* 'de
On Tue, Sep 17, 2013 at 2:09 PM, Gary Carlson
wrote:
> automake: warning: possible forward-incompatibility.
> automake: At least a source file is in a subdirectory, but the
> 'subdir-objects'
> automake: automake option hasn't been enabled. For now, the corresponding
> output
> automake: object f
