Repository navigation
Integrate standalone Embassy through runtime time profiles - #1
Draft
sanchuanhehe wants to merge 2 commits into
Draft
sanchuanhehe wants to merge 2 commits into
sanchuanhehe wants to merge 2 commits into
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
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.
Integrate Embassy through the existing runtime facade instead of a parallel component. The existing
embassyprofile keeps its single SchedulerPort and 1 ms resolution (1 MHz ABI); experimentalembassy-onlyconsumes HAL TIMER/TCXO without compiling the thread scheduler. Both profiles share a bounded queue and one registration. Waker callbacks run outside queue borrows; shared timer generation covers callback reentry.Validation: independent remote dependency graph, 86 base / 91 shared host tests, 14 standalone tests per chip, UI/doc/negative-feature checks and three-chip target Clippy passed. WS53 normal/fault and WS63/BS21 standalone QEMU passed (old-chip TCXO model fix required). The existing coexist HIL fixture prints the same
native_ticks=7 embassy_ticks=7threshold failure before and after migration in QEMU; it is not qualified here. No hardware operations or release. New HAL/profile and RF contract dependencies remain unpublished; the explicit development lane is not registry release qualification.