summaryrefslogtreecommitdiff
path: root/usrp/host/lib/usrp_local_sighandler.cc
diff options
context:
space:
mode:
authorJohnathan Corgan2009-08-17 23:46:30 -0400
committerttsou2009-09-15 18:06:27 -0400
commitb5aa407ec2b1bdebc1c950a9428789fe50327776 (patch)
treeecbc04220951ee75640cdcc17048d81525f54d0c /usrp/host/lib/usrp_local_sighandler.cc
parent895f2e04a9d962cfe56d416691600b5c619ea180 (diff)
downloadgnuradio-b5aa407ec2b1bdebc1c950a9428789fe50327776.tar.gz
gnuradio-b5aa407ec2b1bdebc1c950a9428789fe50327776.tar.bz2
gnuradio-b5aa407ec2b1bdebc1c950a9428789fe50327776.zip
Applied libusb-1.0 patch set from Thomas Tsou <ttsou@vt.edu>:
This patch set updates the usrp to support libusb-1.0. Asynchronous I/O through libusb is added with fusb_libusb1.*, which is heavily based on fusb_linux.*. In short, URB's and ioctl calls are replaced with libusb_transfer structs and native calls. Transfer reaping is handled by libusb and associated callbacks. I get 32Mb/s on all of my machines using test_usrp_standard_rx or tx. Due to the API rewrite in 1.0 from 0.12, there are alot of changes, many are simply name changes. Known Issues: Transmit and receive both work, but not at same time (e.g. usrp_benchmark_usb.py). libusb does not create any internal threads, so for a single session fusb_libusb1 works in the same manner as fusb_linux with the callback called at controlled times. With multiple libusb sessions the callback may occur at any time and threading issues come into play causing behavior to become undefined. The use of separate libusb_contexts _might_ solve this issue; I have not had the time to look into it.
Diffstat (limited to 'usrp/host/lib/usrp_local_sighandler.cc')
0 files changed, 0 insertions, 0 deletions