Clone this repo:
  1. e486a62 Merge stage-aosp-master into pi-dev-plus-aosp am: 5fefc1024c by Xin Li · 12 months ago android10-c2f2-release android10-c2f2-s1-release android10-c2f2-s2-release android10-dev android10-mainline-media-release android10-mainline-networking-release android10-mainline-resolv-release android10-qpr1-b-release android10-qpr1-b-s1-release android10-qpr1-c-release android10-qpr1-c-s1-release android10-qpr1-d-release android10-qpr1-mainline-release android10-qpr1-release master ndk-sysroot-r21 android-10.0.0_r12 android-10.0.0_r13 android-10.0.0_r14 android-10.0.0_r15 android-10.0.0_r16 android-10.0.0_r18 android-10.0.0_r19 android-10.0.0_r20 android-10.0.0_r21 android-10.0.0_r22 android-10.0.0_r23 android-10.0.0_r24 android-10.0.0_r25 android-10.0.0_r26 android-10.0.0_r27 android-10.0.0_r28 android-10.0.0_r29 android-10.0.0_r7 android-10.0.0_r8 android-10.0.0_r9 android-mainline-10.0.0_r4 android-mainline-10.0.0_r5 android-mainline-10.0.0_r6 android-mainline-10.0.0_r7 android-mainline-10.0.0_r8 android-mainline-10.0.0_r9 android-r-preview-1
  2. 5fefc10 Merge stage-aosp-master into pi-dev-plus-aosp by Xin Li · 12 months ago
  3. 51fde36 DO NOT MERGE - Merge pi-dev@5234907 into stage-aosp-master by Xin Li · 1 year ago
  4. 4b4e064 Merge "Add default code reviewers into OWNERS" am: 03bb0718cc am: 613bb4e662 by Chih-hung Hsieh · 1 year, 1 month ago
  5. b78c76b Merge "Add default code reviewers into OWNERS" am: 03bb0718cc am: 613bb4e662 by Chih-hung Hsieh · 1 year, 1 month ago


Build Status Build status Coverity Scan Build Status

libusb is a library for USB device access from Linux, Mac OS X, Windows, OpenBSD/NetBSD and Haiku userspace. It is written in C (Haiku backend in C++) and licensed under the GNU Lesser General Public License version 2.1 or, at your option, any later version (see COPYING).

libusb is abstracted internally in such a way that it can hopefully be ported to other operating systems. Please see the PORTING file for more information.

libusb homepage:

Developers will wish to consult the API documentation:

Use the mailing list for questions, comments, etc:

(Please use the mailing list rather than mailing developers directly)