On Thu, Mar 19, 2015 at 9:17 AM, Dominic Spill <[email protected]> wrote: > On 19 March 2015 at 12:16, Chris Hallinan <[email protected]> wrote: >> >> Hmm, I'm using kernel 3.12, definitely no hackrf module, but I still >> can generate the same error simply by issuing hackrf_info in a short >> loop. > > Yes, this is unrelated to the looping issue, it just presents the same > error message (i.e. it can't connect to the HackRF). > >> Once the error happens, it is permanent. Unplugging and replugging >> the USB cable resolves it. > > I'm fairly certain this is related to the way that linux or libusb > handle the repeated opening and closing of a device. > > Is there a reason that you need to open and close the device often?
No, I don't need that capability for what I'm doing now, I was just trying to add my info to the discussion because obviously the issue isn't resolved. Yes, it is likely either in libusb or the usb kernel driver(s) but I don't have any specific knowledge of that stack. Thanks, Chris -- Life is like Linux - it never stands still. _______________________________________________ HackRF-dev mailing list [email protected] https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
