move hw_flavour from the initializer into a separate API function #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
No it is also used in SDRangel but fixing by the version to v1.1.2 it should not have an impact. Eventually SDRplay support with libmirisdr4 may be dropped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
hw_flavourparameter formirisdr_openis only used in the example programs when initializing the device. It's just a convenience feature, but it breaks API for many other apps. I think, if it even should be handled by the library, it should have its own separate call.This brings back the long-requested (pothosware/SoapyOsmo#9) compatibility with the original libmirisdr.