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

Tuning step fixes #1115

Merged
merged 3 commits into from
Sep 10, 2024
Merged

Tuning step fixes #1115

merged 3 commits into from
Sep 10, 2024

Conversation

kk7ds
Copy link
Owner

@kk7ds kk7ds commented Sep 10, 2024

  • Fix several drivers with zero tuning steps
  • Prioritize radio-supplied tuning steps

The valid_tuning_steps must be ... valid.
The ft1d driver has seemingly had incorrect tuning step handling since
the beginning. As a result, stricter handling of tuning steps
provided by the radio started to break down. This fixes them to work
according to the OEM software for all the available steps.
This makes the UI consider the radio's tuning steps, if defined as
the first course of action. The existing code tried the standard
set followed by the radio's set, assuming the radio's would be a
subset, which is of course not always true.

This also makes required_step() consider the radio-specific steps
after the standard ones, if there are any strange ones to allow the
radio to define ones that are not in the standard list.

Related to #10968
@kk7ds kk7ds merged commit 43f6ad6 into master Sep 10, 2024
6 checks passed
@kk7ds kk7ds deleted the fix-tuning-steps branch September 10, 2024 04:29
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

Successfully merging this pull request may close these issues.

1 participant