• Home
Name Date Size #Lines LOC

..--

examples/03-May-2024-665534

libusb/03-May-2024-1,8451,409

libusb-compat.xcodeproj/03-May-2024-271257

m4/03-May-2024-7,9817,153

AUTHORSD03-May-202431 31

COPYINGD03-May-202425.8 KiB505418

ChangeLogD03-May-20248.7 KiB287193

INSTALLD03-May-20249.2 KiB235177

LICENSED03-May-20242.2 KiB4838

MODULE_LICENSE_LGPLD03-May-20240

MacConfigExternalDebug.xcconfigD03-May-2024615 2019

MacConfigExternalRelease.xcconfigD03-May-2024854 2827

Makefile.amD03-May-2024462 2517

Makefile.inD03-May-202422.6 KiB727640

NEWSD03-May-2024725 2718

NOTICED03-May-202425.8 KiB505418

OWNERSD03-May-2024137 43

READMED03-May-20242 KiB4234

README.versionD03-May-2024129 32

aclocal.m4D03-May-202438.6 KiB1,086971

compileD03-May-20243.6 KiB14379

config.guessD03-May-202444.4 KiB1,5461,332

config.hD03-May-20242.3 KiB8023

config.h.inD03-May-20241.9 KiB7853

config.subD03-May-202432.9 KiB1,6771,532

configureD03-May-2024395 KiB13,95210,937

configure.acD03-May-20241.9 KiB6754

depcompD03-May-202417.4 KiB590375

install-shD03-May-202413.3 KiB520344

libusb-config.inD03-May-20241.3 KiB8274

libusb.pc.inD03-May-2024268 1511

ltmain.shD03-May-2024239.4 KiB8,4626,520

missingD03-May-202410.9 KiB368275

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

README.version

1URL: http://sourceforge.net/projects/libusb/files/libusb-0.1%20%28LEGACY%29/0.1.12/libusb-0.1.12.tar.gz/download
2Version: 0.1.12
3