Make the DECT-2020 NR+ libmodem.a available as a feature #16
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.
This is a do-over of #15 after moving towards a testable application with nrf-modem.
Unlike the original approach it switches (rather than adding) the library; consequently, this needs to be feature-gated to keep the library usable. (The original idea with #15 was to just always link both, let the user decide what they reference and the linker what to gc, but actually the different libmodem.a have different texts for identical symbols).
How much this is additive (as features should be) I can not tell because I don't see into the proprietary libraries, but I guess that using DECT will break the other cases. But we're in low-level embedded crates, and feature additivity is generally not valued so much when there's already a hard decision for which chip is to be selected.
The issue remains that for this to be practically releasable, a firmware would need to be available.
An extra commit switches on short enums. It remains to be tested whether the radio libmodem is built this way as well.