• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

examples/22-Nov-2023-665534

libusb/22-Nov-2023-1,8451,409

libusb-compat.xcodeproj/22-Nov-2023-271257

m4/22-Nov-2023-7,9817,153

.gitD01-Jan-19700

AUTHORSD22-Nov-202331 31

COPYINGD22-Nov-202325.8 KiB505418

ChangeLogD22-Nov-20238.7 KiB287193

INSTALLD22-Nov-20239.2 KiB235177

LICENSED22-Nov-20232.2 KiB4838

MODULE_LICENSE_LGPLD22-Nov-20230

MacConfigExternalDebug.xcconfigD22-Nov-2023615 2019

MacConfigExternalRelease.xcconfigD22-Nov-2023854 2827

Makefile.amD22-Nov-2023462 2517

Makefile.inD22-Nov-202322.6 KiB727640

NEWSD22-Nov-2023725 2718

NOTICED22-Nov-202325.8 KiB505418

READMED22-Nov-20232 KiB4234

aclocal.m4D22-Nov-202338.6 KiB1,086971

compileD22-Nov-20233.6 KiB14379

config.guessD22-Nov-202344.4 KiB1,5461,332

config.hD22-Nov-20232.3 KiB8023

config.h.inD22-Nov-20231.9 KiB7853

config.subD22-Nov-202332.9 KiB1,6771,532

configureD22-Nov-2023395 KiB13,95210,937

configure.acD22-Nov-20231.9 KiB6754

depcompD22-Nov-202317.4 KiB590375

install-shD22-Nov-202313.3 KiB520344

libusb-config.inD22-Nov-20231.3 KiB8274

libusb.pc.inD22-Nov-2023268 1511

ltmain.shD22-Nov-2023239.4 KiB8,4626,520

missingD22-Nov-202310.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