bladeRF/host/drivers/linux
Jon Szymaniak 0d00dbc8e2 driver/linux: Updated README.md
Added note that this driver should not be used in its current form.
2014-07-05 12:20:10 -04:00
..
bladeRF.c linux driver: fix RX routines 2014-04-29 05:57:27 -04:00
Makefile libbladeRF & CLI: [WIP] In the process of switching over to CMake 2013-08-12 03:24:16 -04:00
README.md driver/linux: Updated README.md 2014-07-05 12:20:10 -04:00

bladeRF Linux Kernel Driver

Important note: This kernel module is very much out of date and should not be used in its current form. libbladeRF now utilizes libusb is now used to interface to the bladeRF. In the future, this module will be revisited, with high-performance applications in mind.

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 tighter rule that applies the appropriate mode to the /dev/bladerf# entry.