bladeRF/linux/kernel
Robert Ghilduta a4f2a0027e linux_kernel: RX and TX fixes
data_*_used variable is introduced to keep track of the total number of data
packets that are inflight or have data in them. In the case of RX, a packet is
"used" when it is submitted, and it "unused" after data has been read. In the
case of TX, a packet is "used" when user-mode data is copied to it, and it is
"unused" after the URB has completed.
2013-07-22 03:45:28 -07:00
..
.bladeRF.c.swn linux_kernel: RX and TX fixes 2013-07-22 03:45:28 -07:00
bladeRF.c linux_kernel: RX and TX fixes 2013-07-22 03:45:28 -07:00
bladeRF.h kernel: Changing USB VID/PID to OpenMoko instead of Cypress. 2013-07-06 14:03:45 -07:00
Makefile FSK bridge example 2013-02-18 20:11:39 -08:00
README.md linux: Fixed some typos an added some URLs. 2013-07-17 00:33:13 -04:00

bladeRF Linux Kernel Driver

The linux kernel driver implements a USB device and has some buffering to be able to place multiple packets in flight at a time achieve the high datarates associated with USB 3.0 Superspeed.

Requirements

Even though we build a module for the kernel, your kernels source code is required to build against. We've tested with kernels as old as 3.5.0, but we mostly use Ubuntu for testing and development.

Building

  1. make
  2. See that bladeRF.ko has been made.
  3. sudo insmod bladeRF.ko

The kernel module should now be installed and ready to be used.

bladeRF udev Rule

Usually the udev rules associated with USB devices use the VID and PID to determine the matching for the rule and change the mode to be accessible to users of that group. In our testing, it's been seen that the particular udev rule changes the mode of /dev/bus/usb/... but not the preferred dev entry we create of /dev/bladerf#. Due to this, we have a relatively broad udev rule:

KERNEL=="bladerf*", MODE="0660", GROUP="plugdev"

Please feel free to suggest a tigher rule that applies the appropriate mode to the /dev/bladerf# entry.