This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 39
2021.10.25: Working Group Meeting
Kumar Sankaran edited this page Oct 26, 2021
·
5 revisions
- Details: https://sites.google.com/a/riscv.org/risc-v-staff/home/tech-groups-cal
- Past meetings: https://github.com/riscv/riscv-platform-specs/wiki
- Meetings every alternate Monday
- 7AM PST until Mar 14 2021, 8AM PST after Mar 14 2021
- If the meeting Monday is a scheduled holiday in the US, the meeting will be held on Wed 8AM PST of the same week
- Anti-trust statement
- Open and collaborative
- Org chart:
- TSC -> Software HC -> Platform HSC (you are here)
- TGs and SIGs as needed
- M-Mode Requirements in the Platform Spec
- Platform schedule and owners tracker Excel located here https://docs.google.com/spreadsheets/d/1J4kqyW9tPxqY1CGcJUQsmtHt3FYlqGi_erWQGrmoQtU/edit#gid=0
- Google Drive Shared platform folder with all presentations, schedules and material located here https://drive.google.com/drive/folders/1ooqdnIsYx7XKor5O1XTtM6D1CHp4hc0p?usp=sharing
- Platform Specification Document located here https://github.com/riscv/riscv-platform-specs/blob/main/riscv-platform-spec.adoc
- Platform Policy Document located here https://docs.google.com/document/d/1U5qLoztZpCRSnw2s8tx4rB0SFPMQ27Svrr9jWRsOziY/edit
- As per the platform HSC meeting on 10/25/2021 at 8AM PST, the following was agreed by a majority of participants on the call as well as past participants and multiple distro reviewers:
- The M-mode requirements as in the current spec will be removed from the 2022 OS-A base and server platforms
- The platform spec will continue to mandate all the SBI requirements are as currently listed in the document
- OS-A base and server platforms will continue to comply with the RVA22U and RVA22S profiles
- The requirement to comply with the RVM20M64 profile will be removed from the OS-A base and server platforms
- If there are still any concerns from anyone regarding the decisions above, please reach out to Mark Himelstein ([email protected]) directly.
- Meeting recording here TBD