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.

Sign up for GitHub

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

Jump to bottom

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

Commits on Sep 10, 2024

  1. Fix several drivers with zero tuning steps 

    The valid_tuning_steps must be ... valid.
    @kk7ds
    kk7ds committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    fe0db30 View commit details
    Browse the repository at this point in the history

  2. ftXd: Fix tuning step handling 

    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.
    @kk7ds
    kk7ds committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    68458f8 View commit details
    Browse the repository at this point in the history

  3. Prioritize radio-supplied tuning 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 committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    99cfeae View commit details
    Browse the repository at this point in the history