bladeRF/linux/kernel
Jon Szymaniak 4dae459b66 linux_driver: Added bus/addr ioctl() support & corrected return values
Added the following ioctl() items:
  BLADE_GET_BUS  - Get the bus number the device is attached to
  BLADE_GET_ADDR - Get the device's address on the bus

The ioctl() return values for copy_to_user()s were directly coming from
copy_to_user. In the case that copy_to_user() fails, -EFAULT is
returned.
2013-08-07 22:47:02 -04:00
..
.bladeRF.c.swn linux_kernel: RX and TX fixes 2013-07-22 03:45:28 -07:00
bladeRF.c linux_driver: Added bus/addr ioctl() support & corrected return values 2013-08-07 22:47:02 -04: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 doc: Fixed typo in linux driver README.md 2013-07-22 21:21:49 -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 tighter rule that applies the appropriate mode to the /dev/bladerf# entry.