Add board-aware GPS UART profile#505
Draft
hjoungjoo wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
gps_port=autodefault and GPS Port setting so the runtime can choose the right serial deviceScope
This is split from the larger MF_PiFinder compatibility branch. It focuses on board/GPS UART profile behavior and intentionally avoids the Bookworm install-path changes that are already in #499.
Validation
cd python && pytest tests/test_sys_utils.py -qpython3 -m py_compile python/PiFinder/board_config.py python/PiFinder/sys_utils.py python/PiFinder/ui/callbacks.py python/PiFinder/ui/menu_structure.py python/tests/test_sys_utils.pygit diff --check upstream/main...HEADMore compatibility work is being split into feature-focused draft PRs; Bluetooth keyboard support is next.