Bladerf1 support with pure rust driver

[ratzrattillo]

If desired, we could add support for the BladeRF1 with libbladerf-rs, additionally to the support from Soapy.

[bastibl]

I don't have a BladeRF to test, but I'd be fine adding it.

Could you squash your commits and rebase them on the main branch please?

[ratzrattillo]

@bastibl , would you like to merge this feature?

[bastibl]

I think with this as dependency, we can no longer publish the create. IIRC, it requires a version, no?

[bastibl]

Maybe you could craft a release for the version that should be used here, so we don't have to reference the git repo.

[ratzrattillo]

Okay, i will find out how to publish a crate. Never did that before.

[ratzrattillo]

I published the driver on crates.io: https://crates.io/crates/libbladerf-rs/

[bastibl]

Sorry for the delay. Can you say something about the state of this implementation? Does TX/RX work, is it actively developed? Just that I know, I think we should mention the state of the impls somewhere in the readme.

[ratzrattillo]

Sorry for the delay. Can you say something about the state of this implementation? Does TX/RX work, is it actively developed? Just that I know, I think we should mention the state of the impls somewhere in the readme.

The goal of libbladerf-rs is not to replace the original libbladerf completely, as i do not have a BladeRF2 and thus cannot do an implementation for that board. Also i only own a BladeRF XB200 expansion baord, but not the XB-100 and not the XB-300, thus the implementation for those might be flawed.

The current implementation supports TX/RX as well as most of the methods that seify exposes.

It is actively maintained by me, with focus on bugfixing. Originally this implementation was meant to run on an android device, but unfortuantely it seems like the nusb library on which this project is based on stripped Android support.

[kevinmehall]

Originally this implementation was meant to run on an android device, but unfortuantely it seems like the nusb library on which this project is based on stripped Android support.

If nusb v0.2 broke a use case you have, please open a discussion on the nusb repo. Are you working with rooted Android devices? I'm assuming what you're referring to is that v0.2 no longer compiles the device discovery (sysfs and udev) parts of the Linux backend for Android targets, but those rely on Linux APIs that are not supported in the app sandbox on Android so v0.1 list_devices only worked with root and watch_devices didn't work at all. However, if you obtain a USB file descriptor via Android APIs or something like termux-usb, you can still pass it to Device::from_fd.

The plan to fully support Android is by calling Android APIs via JNI in kevinmehall/nusb#150, which I haven't had a chance to review or test yet. If you can review and/or test that and comment on that PR it could help move it along because part of the problem is that I'm not very familiar with Android.

[ratzrattillo]

Originally this implementation was meant to run on an android device, but unfortuantely it seems like the nusb library on which this project is based on stripped Android support.

If nusb v0.2 broke a use case you have, please open a discussion on the nusb repo. Are you working with rooted Android devices? I'm assuming what you're referring to is that v0.2 no longer compiles the device discovery (sysfs and udev) parts of the Linux backend for Android targets, but those rely on Linux APIs that are not supported in the app sandbox on Android so v0.1 list_devices only worked with root and watch_devices didn't work at all. However, if you obtain a USB file descriptor via Android APIs or something like termux-usb, you can still pass it to Device::from_fd.

The plan to fully support Android is by calling Android APIs via JNI in kevinmehall/nusb#150, which I haven't had a chance to review or test yet. If you can review and/or test that and comment on that PR it could help move it along because part of the problem is that I'm not very familiar with Android.

Thanks for the information on Device::from_fd. I will check this soon. I am also not very familiar with Android unfortunately. Next thing I will do in that regard is to write a small example app which controls my BladeRF.

[bastibl]

Thanks!