RISC-V: Maturing an Open Standards Development Process
summary
RISC-V commits to becoming an internationally recognized standard by submitting as an ISO PAS fast-track candidate and tightening its specification lifecycle: groups require a charter, a proof-of-concept (simulator, toolchain, kernel and apps) before public review, and a formal freeze/final-draft stage. To close the “spectator gap” voting is now tied to active participation, empty comments forfeit influence, proposals have an 18-month timebox, and opcode scarcity (32-bit space nearly exhausted) forces stricter gatekeeping.
AI-written summary · about
chapters (9)
- 0:00RISC-V standards maturity
- 1:24RISC-V’s open standards role
- 4:15Freedom drives innovation
- 9:14Open source vs open standards
- 13:33What makes a true standard
- 19:57RISC-V specification process
- 29:42Process improvements
- 35:22Participation gaps in standards
- 47:13Q&A on opcodes
related talks
45mOpen Collaboration in Action: How We Build RISC-V
19mGetting Involved in RISC-V Technical Committees
41mRISC-V and Open Source Hardware BoF
36mRISC-V and RISE Project BoF
43mOpen Hardware: Skyrocketing Momentum & Global Adoption from Embedded to Enterprise
06mRISC-V 101: Welcome Remarks and Introductions
23mMaturing the RISC-V Ecosystem: From Technology to Product
31mWhat is RISC-V?