Repository navigation
Conversation
Owner
Author
|
Closing as superseded by #51, which consolidated the cumulative BRCB R1–R3 implementation onto current |
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.
Scope
Stacked on Phase 4D-R2a. Add a backward-compatible per-request access context to the static MMS object/dispatcher API so association-aware BRCB writes can be implemented without changing legacy object callbacks.
Implemented
MmsStaticRequestAccessContextcarryingassociation_id+ stable binary Owner identityMmsStaticContextualWriteCallbackappended toMmsStaticObjectEntrydispatch()overloads accept an optional access context with a default empty contextStill to complete in R2
Resv,ResvTms,Owner,RptEna,EntryID,PurgeBuf)Physical ESP32-P4 flash acceptance remains
READY_NOT_MEASURED.