Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide access to native device handle #274

Closed
SignalWhisperer opened this issue Oct 1, 2020 · 0 comments
Closed

Provide access to native device handle #274

SignalWhisperer opened this issue Oct 1, 2020 · 0 comments

Comments

@SignalWhisperer
Copy link

After working a lot with Boost.Asio, when they abstract something, they still give access to the native element underneath (see here), and it seems SoapySDR does not provide this access.

Many times I'm faced with an incomplete Soapy driver for an SDR where not all the necessary calls have been fully implemented (see pothosware/SoapyBladeRF#36). Having access to the underlying native handle would allow me to not be stuck and to make the library calls myself. It would also allow to go beyond what the SoapySDR API can provide, since for example, it allows to set a clock reference but not its frequency.

Something as simple as:

void* getNativeHandle(void) const;

Where each driver could, if they so desire, return the appropriate handle to the device.

I understand if you do it for the device, you should do it for the stream, and some drivers might be using more than one object. I'm not aware of all the variations, but I still think it would be useful in some situations to have access to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant