Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove extension version numbers from certificate_model YAML files since they specify the version of the related standards #325

Open
james-ball-qualcomm opened this issue Nov 27, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@james-ball-qualcomm
Copy link
Collaborator

# Specification versions
tsc_profile: null # None for MC100
unpriv_isa_manual_revision: "20191213"
priv_isa_manual_revision: "20190608-Priv-MSU-Ratified"
debug_manual_revision: "0.13.2"

# XXX - Remove version information since specifying priv/unpriv ISA manual should imply this.
extensions:
  I:
    version: "~> 2.1"
    presence: mandatory
  C:
    version: "~> 2.2"
    presence: mandatory
@james-ball-qualcomm james-ball-qualcomm added the enhancement New feature or request label Nov 27, 2024
@james-ball-qualcomm james-ball-qualcomm self-assigned this Nov 27, 2024
@james-ball-qualcomm
Copy link
Collaborator Author

Just realized that the spec versions need to be a function of the certificate model version number. The plan is to change the major version number when newer spec versions are required. So, MC100v1 would be these old 2019 specs and then v2 would be the next ratified versions of the specs and so on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant