Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Clayton Shepard authored 6 years ago and rdoost committed 6 years ago

Signed-off-by: Rahman Doost <doost@rice.edu>

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Not much has been changed in the driver (that used libbladerf 1.0).
Some bugs have been fixed. Documentation has been added. A configuration
file has been added too, put in the directory ./configuration/bladeRF.

To use a bladeRF device, see documentation in targets/ARCH/BLADERF/README.

Only the BladeRF x40 has been tested.

Performance is not too bad at 5MHz, a bit worse at 10MHz and on the test
machine I used I face realtime problems at 20MHz when I push downlink
throughput.

So, there is still some work to do to have a good support of bladeRF.

Add a parameter to load_configmodule API to allow an exec to specify that it may be run with only  command line options

abort execution when an unknown option is passed via the command line: add config_check_cmdlineopt API to config module, create lte-softmodem-common.c source to remove duplicate code in lte-softmodem.c and lte-uesoftmodem.c, fix segfaults in exec_function of lte-uesoftmodem

1. Modify all expressions using original LTE-RRC data types for new generated ones
2. Does not change any program logic

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

new interpretation of sdr_addrs string in RU config file: this is now directly passed to the uhd to specify a device. It may contain a device type (i.e., "type=x300") or an IP address (i.e., "addr=192.168.10.2")

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>