By default, logging is set to NONE, which means that no output will be produced. These negative error codes relate to LIBUSB_ERROR constants which are listed on the miscellaneous documentation page. Libusb functions typically return 0 on success or a negative error code on failure. The libusb homepage includes a list of real-life project examples which use libusb. Some example programs can be found in the libusb source distribution under the "examples" subdirectory. The Synchronous and asynchronous device I/O documentation provides some insight into this topic. One decision you will have to make is whether to use the synchronous or the asynchronous data transfer interface. To begin reading the API documentation, start with the Modules page which links to the different categories of libusb's functionality. Compatible with libusb-0.1 through the libusb-compat-0.1 translation layer.Thread safe (although the asynchronous interface means that you usually won't need to thread).Asynchronous (more complicated, but more powerful).All transfer types supported (control/bulk/interrupt/isochronous).See the Application Programming Interface page for a complete list of the libusb functions. You can probably find less verbose introductions by searching the web. Full information can be found in the USB 3.0 Specification which is available for free download. This documentation assumes knowledge of how to operate USB devices from a software standpoint (descriptors, configurations, interfaces, endpoints, control/bulk/interrupt/isochronous transfers, etc). After reviewing this documentation, feedback and questions can be sent to the libusb-devel mailing list. This documentation is aimed at application developers wishing to communicate with USB peripherals from their own software. Libusb is an open source library that allows you to communicate with USB devices from user space.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |