Hi,
It is my great pleasure to announce the release of libusb 1.0.18 (as
well as the simultaneous final release of libusbx 1.0.18), which marks
the long awaited merging back of libusbx with libusb!
With this release, we are finally consolidating the two projects back
into one, and bringing the
Closed #168 via fc458425b6dd6258e562e44c22978ab22412ff0a.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/168--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Lea
On Sat, 25 Jan 2014, Chris Dickens wrote:
> You are going to have trouble using the same interface from two different
> processes. Linux maintains exclusive access for a process once it has
> claimed an interface until it is released or the file descriptor is closed
> (either intentionally or from
You are going to have trouble using the same interface from two different
processes. Linux maintains exclusive access for a process once it has
claimed an interface until it is released or the file descriptor is closed
(either intentionally or from the process exiting). If you claim the
interface i
I've got a big (and late) project that needs to use libusb/libusbx to ingest
data from a satellite demodulator.
I need async capability, as well as the ability to talk via two different
logical interfaces via different processes, even through they are on the same
USB interface (logical interfac
