docs: sync RCP-ARCHITECTURE.md after cpp-RCP's v3.0.0 rewrite - #190
Merged
Conversation
cpp-RCP shipped a full ground-up rewrite (cpp-RCP issue #129, ROADMAP.md Phase 17), ported module-by-module from c-RCP's current RC5-conformant implementation, tagged v3.0.0 today. Several cpp-RCP conformance gaps this document previously tracked as open are now closed as a direct, verifiable result of that rewrite -- corrected in place rather than left stale: - Table 30 Row-2 evt[2:0] wiring: previously 'not implemented' for all 8 endpoint types; now conformant, verified directly against the current codebase (can/lin/adc/i2c/uart/iseled/mdio/pwm.hpp all wire real ACF-header evt decode and dispatch). - Section 13.5.1 compound-wait comparison primitive: previously 'not yet implemented'; now conformant (acf.hpp's compound_wait_evt_valid/ compound_wait_match, the same 8-mode shape as c-RCP's reference, threaded through request.hpp's real dispatch). - request.hpp field-level gaps (Compound's cmp_exec_delay/ cmp_repetitions, Triggered's trigger_source_ep/trigger_signal_nr/ trigger_threshold, Timed's presentation_time): previously described as fields present only in comments; now confirmed as real fields with real scheduling/dispatch logic. A different, narrower set of real gaps remains (cited honestly, pulled from cpp-RCP's own current .fusa-reqs-pending.json rather than left unspecified). go-RCP's and rust-RCP's entries in this document are untouched -- not re-verified in this pass, no claims changed for either. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.com>
10 tasks
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.
cpp-RCP shipped a full ground-up rewrite (issue #129, tagged v3.0.0) that closed several conformance gaps this doc previously tracked as open for cpp-RCP: Table 30 Row-2 evt[2:0] wiring (all 8 endpoint types), the §13.5.1 compound-wait comparison primitive, and the specific request.hpp field-level gaps (cmp_exec_delay/cmp_repetitions, trigger_source_ep/trigger_signal_nr/trigger_threshold, presentation_time). All three verified directly against the current cpp-RCP codebase before updating the doc, not assumed from the rewrite's existence. A smaller, different set of real gaps remains for cpp-RCP and is cited honestly from its own current
.fusa-reqs-pending.json. go-RCP's and rust-RCP's entries are untouched.