Re: [Libusbx-devel] Major problems using libusbx on CentOS 5

2014-01-30 Thread Chris Dickens
Hi Judd, Attached is a patch to remove hotplug functionality from the Linux backend, while still retaining all other fixes. This essentially gives you 1.0.18 without hotplug. If you have time to try it, please let me know how it works out. Chris From c79d3eec1a54ea2f2da4a383d1f186fa9587 Mon

Re: [Libusbx-devel] Major problems using libusbx on CentOS 5

2014-01-27 Thread Tim Roberts
Judd Taylor wrote: 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

Re: [Libusbx-devel] Major problems using libusbx on CentOS 5

2014-01-27 Thread Judd Taylor
Roberts [t...@probo.com] Sent: Monday, January 27, 2014 12:23 PM To: libusbx-devel@lists.sourceforge.net Subject: Re: [Libusbx-devel] Major problems using libusbx on CentOS 5 Judd Taylor wrote: I've got a big (and late) project that needs to use libusb/libusbx to ingest data from a satellite demodulator

Re: [Libusbx-devel] Major problems using libusbx on CentOS 5

2014-01-25 Thread Chris Dickens
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

Re: [Libusbx-devel] Major problems using libusbx on CentOS 5

2014-01-25 Thread Alan Stern
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