android_external_libusbx, branch cm-11.0

fix build on linux

2018-06-18T04:10:27+00:00

Change-Id: If8bcf74c828302b4f9bb90b1641579c5fd046c44

fixes for building windows

2013-08-14T20:55:09+00:00

Change-Id: I4c26d86e57c6373c23a9908104f11119dfc467da

Fixes for libusbx on AOSP.

2013-08-14T17:23:30+00:00

Windows: Fix a cast warning when compiling for x64 in VS

2013-08-13T18:00:54+00:00

* Also fixes and closes #129 again

Windows: Fix VS2010 project files

2013-08-12T21:04:39+00:00

* Closes #129

Android: Add examples and stress tests

2013-08-11T21:14:13+00:00

Android: Add formal Android support

2013-08-11T21:12:03+00:00

* Also fix an issue with LIBUSB_LOG_LEVEL_NONE

Core: Add compile time option to use native OS logging facility

2013-08-09T00:55:04+00:00

* This change makes it easier to debug issues in UI applications
  which don't necessarily have a console connected to stderr.
* Outputting to the debugger shouldn't occur in normal situations so
  this change has to be explicitly enabled by a build-time config flag.
* Uses OutputDebugString() on Windows platforms or the syslog facility
  on other OSes, if available.
* Also align the report of configure defaults to autotool's.

linux: ensure the netlink socket is correctly opened with older Linux kernels

2013-08-08T03:01:43+00:00

It is possible for the extra socket flags (available from 2.6.27 on) to be
defined but not available. Check for this case and set the flags correctly
on the netlink socket.

Core: Fix potential segfault caused by using freed memory

2013-08-08T02:45:43+00:00

When a transfer is submitted, the device is referenced in libusb_submit_transfer()
and unreferenced in usbi_handle_transfer_completion(). This transfer could potentially
be freed by any user callback, or is freed by libusb if LIBUSB_TRANSFER_FREE_TRANSFER
is set in the flags. The call to unreference the device uses this potentially freed
memory. Reading the device handle beforehand will prevent this disaster.