NameDateSize

..22-Apr-20134 KiB

aclocal.m422-Apr-201338.6 KiB

AUTHORS22-Apr-201331

ChangeLog22-Apr-20138.7 KiB

compile22-Apr-20133.6 KiB

config.guess22-Apr-201344.4 KiB

config.h22-Apr-20132.3 KiB

config.h.in22-Apr-20131.9 KiB

config.sub22-Apr-201332.9 KiB

configure22-Apr-2013395 KiB

configure.ac22-Apr-20131.9 KiB

COPYING22-Apr-201325.8 KiB

depcomp22-Apr-201317.4 KiB

examples/22-Apr-20134 KiB

INSTALL22-Apr-20139.2 KiB

install-sh22-Apr-201313.3 KiB

libusb/22-Apr-20134 KiB

libusb-compat.xcodeproj/22-Apr-20134 KiB

libusb-config.in22-Apr-20131.3 KiB

libusb.pc.in22-Apr-2013268

LICENSE22-Apr-20132.2 KiB

ltmain.sh22-Apr-2013239.4 KiB

m4/22-Apr-20134 KiB

MacConfigExternalDebug.xcconfig22-Apr-2013615

MacConfigExternalRelease.xcconfig22-Apr-2013854

Makefile.am22-Apr-2013462

Makefile.in22-Apr-201322.6 KiB

missing22-Apr-201310.9 KiB

NEWS22-Apr-2013725

README22-Apr-20132 KiB

README

1libusb-compat-0.1
2=================
3
4A compatibility layer allowing applications written for libusb-0.1 to work
5with libusb-1.0. libusb-compat-0.1 attempts to look, feel, smell and walk
6like libusb-0.1.
7
8Do not attempt to install libusb-0.1 and libusb-compat-0.1 on the same system.
9
10Known quirks/differences from libusb-0.1:
11 1. usb_resetep(), a previously deprecated function, is implemented as
12    equivalent to calling usb_clear_halt().
13 2. libusb-0.1 allowed you to open a device which you did not have permission
14    to do anything useful with (all I/O requests would immediately fail).
15    libusb-compat-0.1 does not allow you to open such devices. You can still
16    read descriptor info without opening a device.
17 3. usb_device's "num_children" attribute is hardcoded to 0, and "children"
18    is hardcoded to NULL. Do you need this information in your software? Let
19    us know on the mailing list, and we'll add it.
20 4. Some libusb-0.1 users may have implemented I/O cancellation by running
21    transfers in their own threads and simply killing the thread when they
22    don't want to do the transfer any more. This is bad programming practice
23    for obvious reasons, and this lack of functionality was one of the primary
24    drivers for libusb-1.0 development. With libusb-1.0 or libusb-compat-0.1
25    backed by libusb-1.0, forcefully killing threads in this way is likely
26    to cause all libusb I/O to halt. Instead, port your application to use
27    libusb-1.0's asynchronous transfer API, which supports transfer
28    cancellation.
29 5. Error codes returned on certain events may not exactly match the error
30    codes returned by libusb-0.1. Patches accepted to bring us closer to the
31    behaviour of libusb-0.1 on Linux.
32
33libusb homepage:
34http://libusb.sourceforge.net
35
36Use the mailing list for questions, comments, etc:
37https://sourceforge.net/mailarchive/forum.php?forum_name=libusb-devel
38
39- Daniel Drake <dsd@gentoo.org>
40(use the mailing list rather than mailing developers directly)
41
42