Tags: chipsalliance/caliptra-sw
Tags
Respect the no-cfi feature in the drivers crate.
Respect the no-cfi feature in the drivers crate.
Put CFI behind a feature flag in caliptra-lms-types and caliptra-imag… …e-types.
[fix] Skip nightly release if caliptra-rtl submodule is stale Last night, the release workflow made a release, even though the caliptra-rtl submodule was not up-to-date: https://github.com/chipsalliance/caliptra-sw/actions/runs/6875915531 The syntax !"$CHECK_RELEASE_SYNC" does not work as intended; we should use -z instead.
Update to zerocopy 0.8.17 Also updates DPE submodule to pull in the same zerocopy. Zerocopy's derive macro for KnownLayout has changed. Compiling DPE in caliptra-sw fails because public interfaces are leaking these private types. The solution is to mark them as a public field. There may be another workaround, but since these types are being serialized to and from raw bytes, it makes sense that these private fields should be visible to callers.
Add libcaliptra APIs to check if ready for certain boot milestones. Previously the only APIs blocked until it reached those milestones. Now they can be checked asynchronously. This is also how `caliptra_is_csr_ready` works.
Add libcaliptra APIs to check if ready for certain boot milestones. Previously the only APIs blocked until it reached those milestones. Now they can be checked asynchronously. This is also how `caliptra_is_csr_ready` works.
PreviousNext