Prevent conflicts between CRSF and GHST leading to radio failsafes #26118
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
tridge
reviewed
Feb 1, 2024
tridge
requested changes
Feb 1, 2024
andyp1per
force-pushed
the
pr-crsf-ghst-conflict
branch
from
dfd6696
to
46d5f46
Compare
do not change to GHST baudrate unless it has been specifically configured
andyp1per
force-pushed
the
pr-crsf-ghst-conflict
branch
from
46d5f46
to
02a556a
Compare
tridge
approved these changes
Feb 2, 2024
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.
Discriminate GHST and CRSF based on first byte
do not change to GHST baudrate unless it has been specifically configured
@rmackay9 @tridge this will need to go into 4.5 asap