[DOC] Update release process and adjust how core versions are mirrored#862
Merged
calebofearth merged 1 commit intomainfrom Oct 30, 2025
Merged
[DOC] Update release process and adjust how core versions are mirrored#862calebofearth merged 1 commit intomainfrom
calebofearth merged 1 commit intomainfrom
Conversation
…d Core process on doc updates and RCs
calebofearth
changed the title
6 tasks
bharatpillilli
approved these changes
Oct 30, 2025
calebofearth
added a commit
that referenced
this pull request
Oct 30, 2025
…e versions are mirrored (#862) Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches. Add some clarifying language Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem
calebofearth
added a commit
that referenced
this pull request
Nov 5, 2025
* [DOC] Reword note about warm reset (#737) Previous wording sounded like it implied a required hitless update. This changes it to use "mutable firmware" instead. * [DOC] Update known lint issues in CaliptraSSIntegrationSpecification.md (#814) Veer core fixed *_up undriven signals. * [DOC] Cherry-pick: 1933efd, for release process doc * [DOC] Cherry-pick: 35abc25, Update release process and adjust how core versions are mirrored (#862) Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches. Add some clarifying language Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem * [DOC] Cherry-pick: Fix some incorrect and redundant language on DMA programming (#847) * Fix redundant/outdated guidance for FW to program DMA assist * Fix a link to Caliptra.md spec * Regenerate ToC; cleanup whitespace * [DOC] Update caliptra-rtl submodule to pull latest doc updates * Update version to 2.0.1 * Update release notes for 2.0.1 * [DOC] Update caliptra-rtl submodule to pull an RDL desc update (doc only) * MICROSOFT AUTOMATED PIPELINE: Stamp 'cwhitehead-msft-2.0.1-docs' with updated timestamp and hash after successful run --------- Co-authored-by: Zach Halvorsen <zhalvorsen@google.com> Co-authored-by: Clayton Kuchta <ckuchta@microsoft.com>
11 tasks
calebofearth
added a commit
that referenced
this pull request
Nov 14, 2025
…s are mirrored (#862) Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches. Add some clarifying language Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem
calebofearth
added a commit
that referenced
this pull request
Nov 14, 2025
…s are mirrored (#862) Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches. Add some clarifying language Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem
calebofearth
added a commit
that referenced
this pull request
Nov 17, 2025
…s from main (#913) * Update caliptra-rtl submodule to tip of patch_v2.1 * Update caliptra-rtl again for final docs * [DOC] Cherry-pick: Reword note about warm reset (#737) Previous wording sounded like it implied a required hitless update. This changes it to use "mutable firmware" instead. * [fc,dv] Cherry-pick: Add missing precondition to FcAxiFilterDaiAccessError_A (#838) * [fc,dv] Add missing precondition to FcAxiFilterDaiAccessError_A Because discard_fuse_write stays high for some time after a request, the previous version of this property wasn't actually true. It was of the form discard ##1 done[->1] |=> error but that doesn't quite work. If you get a DAI request that is discarded followed by a good one, then the history looks like: 1. An AXI write triggers a DAI request that should be discarded. 2. The filter notices, asserting discard_fuse_write [START A] 3. Some time later, the operation finishes 4. It correctly responds with an access error [END A] 5. On the next cycle, discard_fuse_write is still true. [START B] 6. discard_fuse_write drops at some point. ... 7. Now there's a good DAI request. 8. On the next cycle, discard_fuse_write is false (no problem here!) 9. Some time later, this second operation finishes 10. The response doesn't have an access error. [END B WITH FAILURE!] Oh dear... This commit strengthens the precondition to the form dai_req ##1 discard ##0 done[->1] |=> error With the history above, "START B" doesn't happen on step 5. The property next starts matching on step 7, but won't match on step 8 (because discard_fuse_write is false), so there is no error. Thank you, pchunghoon, for the careful description of what was going on (issue #833). Note that the ##0 is required after the second term (instead of ##1), because it's possible to see dai_req_i go high then see discard_fuse_write_i on the following cycle, with dai_cmd_done_o true at the same time (followed by an AccessError on the following cycle). * MICROSOFT AUTOMATED PIPELINE: Stamp 'lowrisc_tighten_dai_sva' with updated timestamp and hash after successful run --------- Co-authored-by: EMRE KARABULUT <63821295+ekarabu@users.noreply.github.com> Co-authored-by: Emre Karabulut <ekarabulut@microsoft.com> * [ENV] Cherry-pick: Remove unused obsolete scripts (#846) * Remove obsolete or internal-use-only scripts * MICROSOFT AUTOMATED PIPELINE: Stamp 'cwhitehead-msft-rm-defunct-scripts' with updated timestamp and hash after successful run * MICROSOFT AUTOMATED PIPELINE: Stamp 'cwhitehead-msft-rm-defunct-scripts' with updated timestamp and hash after successful run --------- Co-authored-by: EMRE KARABULUT <63821295+ekarabu@users.noreply.github.com> Co-authored-by: Emre Karabulut <ekarabulut@microsoft.com> * [DOC] Cherry-pick: Fix some incorrect and redundant language on DMA programming (#847) * Fix redundant/outdated guidance for FW to program DMA assist * Fix a link to Caliptra.md spec * Regenerate ToC; cleanup whitespace * [ENV] Regenerate file lists to fix corrupted Avery VIP paths and rm duplicate lines * [DOC] Cherry-pick: Update release process and adjust how core versions are mirrored (#862) Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches. Add some clarifying language Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem * [TB] Cherry-pick: Fix I3C streaming boot test (#874) * [TB] Fix I3C streaming boot test TB was killing test before FW was done with AXI causing AXI monitor failures at the end. SV test now waits for FW to update the DEVICE_STATUS_0 register before proceeding. * MICROSOFT AUTOMATED PIPELINE: Stamp 'ckuchta-fix-i3c-rand-streaming-boot' with updated timestamp and hash after successful run * [DOC] Cherry-pick: Remove old inout ports from spec (#892) #883 * [VAL] Cherry-pick: Fix MCI register test handling of capabilities reg (#908) * Fix usage of cap lock in mci reg test * Fix usage of get_reg_exp_data() and reduce verbosity of several prints * Format * MICROSOFT AUTOMATED PIPELINE: Stamp 'cwhitehead-msft-mci-reg-test-fix' with updated timestamp and hash after successful run * MICROSOFT AUTOMATED PIPELINE: Stamp 'cwhitehead-msft-2p1-docs-and-mci-val' with updated timestamp and hash after successful run --------- Co-authored-by: Zach Halvorsen <zhalvorsen@google.com> Co-authored-by: Rupert Swarbrick <rswarbrick@lowrisc.org> Co-authored-by: EMRE KARABULUT <63821295+ekarabu@users.noreply.github.com> Co-authored-by: Emre Karabulut <ekarabulut@microsoft.com> Co-authored-by: Clayton Kuchta <ckuchta@microsoft.com>
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
2 participants
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.
Adjust version numbering so that only major/minor versions of Caliptra Core mirror Caliptra Subsystem, but not patches.
Add some clarifying language
Link to the updated process for release candidates and documentation patches as described in Caliptra core, and apply to Subsystem