On Tue, Nov 01, 2005 at 12:28:27PM -0500, EDWARD HALL wrote: > Eric, > > To answer your question, nothing should have changed in the code; > especially not in the kernal. I stopped the running application and > re-started it after reviewing the python code. > > Your mention of -EBUSY might be a clue. While my application was running, > I accidentally launched a second application that also interfaces with USB > and the USRP. The second application failed to launch and the original > application continued to run. It was when I stopped the original > application and tried to restart it that I began receiving the error > messages. I'm wondering if the -EBUSY flag is not resetting after the > conflict for access to the USRP. The problem continues after many computer > reboots and troubleshooting. Your idea of ignoring -EBUSY in usrp_prims.cc > may be a good work-around.
Jeff Long tracked it down a week or so ago. I've changed the code in CVS so that it just ignores the return value from usb_set_configuration. Eric _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
