Lines Matching refs:libusb

11     Improve libusb-config for cross-compiling (SF#2809877)
24     libusb-1.0 can return result codes 0, -1 through -12 and -99.  The old
25     libusb-0.1 software was always returning the negative of an errno.h
28     Unfortunately the current version of libusb-compat passes through some
29     of the libusb-1.0 error codes unchanged.  (Some of the error codes are
33     The patch attached to the below bug report makes sure all libusb-1.0
34     error codes are translated into the libusb-0.1 equivalent negative of
36     errno is always being set as some callers of libusb-0.1 expect that to
37     be the case.  Finally since errno is now always being set by libusb-
65     For maximum compatibility, this makes libusb-compat-0.1 behave like
66     libusb-0.1 on BSD, where endpoint addresses are sanitized for all control
82     libusb-0.1 by running each transfer in it's own thread, and forcefully
85     This bad programming practice is imposed by libusb-0.1 not offering any
86     way to cancel ongoing transfers. Someone should rewrite libusb-0.1 to
89     Killing libusb-1.0 threads while they are event handling will often
104     Xiofan Chen reports that this worked on libusb-0.1.
117     Update to new libusb context API
125     This doesn't make much sense, but libusb-0.1 does it, so we will do it
166     libusb-compat-0.1 and the real libusb-0.1, and suggested this approach.
169     	pkg-config --variable=emulated libusb
175     Pretend to be libusb-0.1.12
177     Pointed out by Ludovic Rousseau: some programs check for specific libusb
198     update for new libusb configuration API
250     add testlibusb example from libusb-0.1