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.

Sign up for GitHub

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

Jump to bottom

Revert back to CRD terminology vs. certificates #346

Open
james-ball-qualcomm opened this issue Dec 4, 2024 · 2 comments · May be fixed by #405
Open

Revert back to CRD terminology vs. certificates #346

james-ball-qualcomm opened this issue Dec 4, 2024 · 2 comments · May be fixed by #405
Assignees
@james-ball-qualcomm
Labels
enhancement New feature or request

Comments

@james-ball-qualcomm
Copy link
Collaborator

Now that I've thought this through better (see slides at https://docs.google.com/presentation/d/1dc7-uWNIHd6qMNlhWxfwCnzACQaSL2vfkHqP_qdpkac and screenshot of key slide below), I need to go back to having what is currently called certificate_models to CRD somehow.

image
@james-ball-qualcomm james-ball-qualcomm added the enhancement New feature or request label Dec 4, 2024
@james-ball-qualcomm james-ball-qualcomm self-assigned this Dec 4, 2024
@james-ball-qualcomm james-ball-qualcomm mentioned this issue Jan 10, 2025
Open
@james-ball-qualcomm
Copy link
Collaborator Author

Just going to rename the backend generator to CRD. The /arch files can stay unchanged.

@james-ball-qualcomm
Copy link
Collaborator Author

Also going to add "Processor" prefix to Certificate Class/Model to support non-processor certificates that don't follow this class/model naming scheme.

@james-ball-qualcomm james-ball-qualcomm linked a pull request Jan 10, 2025 that will close this issue
346 revert to crd terminology #405
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@james-ball-qualcomm james-ball-qualcomm

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

346 revert to crd terminology riscv-software-src/riscv-unified-db
1 participant
@james-ball-qualcomm