Welcome to the RISC-V Technical wiki landing page. All good technical things for RISC-V can be found here. If something is missing, please reach out to firstname.lastname@example.org for more help.
Just starting to learn about RISC-V? Try our Getting Started document for an overview of how to work with us. For a technical introduction, see our Getting Started Guide for an overview of running operating systems on RISC-V.
|Architecture Review||oversight||Admin||Must be completed prior to Freeze. Also including opcodes and new/changed architectural State approval (e.g., CSRs, data registers).|
|Asciidoctor APIs||documentation||Website||APIs for automating aspects of the doc email@example.com|
|Asciidoc Writers' Guide||documentation||Website||Introduction to Asciidocfirstname.lastname@example.org|
|Benchmark Links||links||Links||Links to existing benchmark email@example.com|
|Code of Conduct||etiquette||Document||RISC-V Code of Conduct - please read firstname.lastname@example.org|
|Content Requests||requests||Link||Send email to RISC-V Content team for web content, collaborative PR, blog posts, email@example.com|
|Ecosystem Software Links||URLs||Document||docs, repos, videos, firstname.lastname@example.org|
|Email groups - members||subscribe||Portal||Member portal - working groups email server, hosted via Groups.email@example.com|
|Email groups - public||subscribe||Portal||Public mailing lists (hosted on google groups) including ISA-DEV and SW-DEV, and other firstname.lastname@example.org|
|Extension Development Lifecycle||extensions||Document||Diagram of the lifecycle of milestones when developing a new email@example.com|
|intro||Document||How to work with the RISC-V technical firstname.lastname@example.org|
|Getting Started: Operating Systems||into||Education||A technical overview of how to run standard operating systems - Zephyr and Linux - on popular RISC-V email@example.com|
|GitHub Info||documenation||Link||A detailed page of our GitHub organizations and which repos live in which firstname.lastname@example.org|
|Glossary||documentation||Document||Glossary of email@example.com|
|Help||email address to get firstname.lastname@example.org|
|Information directory||repo||Folder||has prior art, glossary, links, content, email@example.com|
|ISV list||ISVs||Resources||List of ISVs within the RISC-V firstname.lastname@example.org|
|Jira||bug reporting||Admin||Issue tracking for RISC-V International issues - use Github Issues for extension-specific email@example.com|
|Misc Info||misc||wiki||Some misc info for historical reference|
|On-Deck Specification Dashboards||table||Links||All current ISA and Non-ISA specs prepping for their Freeze or "Ready for Ratification" firstname.lastname@example.org|
|Other organizations||links||Links||other organizations that do work related to RISC-V or ecosystem technology that enables RISC-V members to develop and deploy email@example.com|
|Policies||policies||Folder||Folder containing all working policies - approved, in process, and firstname.lastname@example.org|
|Prior Art Links||legal||Links||Links to prior email@example.com|
|Shared Drive||repo||Folder||Shared storage for the entire technical firstname.lastname@example.org|
|Slack space||messaging||Admin||Live messaging for the community - if you are new, add yourself with this email@example.com|
|Software Ecosystem Status||status||Admin||status of components|
|Specifications||extensions||Links||Official links to approved firstname.lastname@example.org|
|Specification status||status||Document||All working specs and their status including development partners and email@example.com|
|Tech Chairs Folder||status||Folder||Folder with minutes and status decks for TSC and firstname.lastname@example.org|
Tech Groups Calendar (OLD!)
|calendar||Admin||We will be slowly phasing out this calendar for the remainder of August 2021. We will give the tech chairs 1 month to move their events over since many folks are on vacation in August.||email@example.com|
Technical Meetings Calendar (NEW!)
See below for instructions on how to subscribe.
|Technical Organizational Charts||organization||Admin||slides with graphs and prose and information firstname.lastname@example.org|
|Technical Working Groups||contacts||Document||List of all working groups, chairs/co-chairs, and email@example.com|
|Vote Status||status||wiki||election, policy, charter, waiver vote firstname.lastname@example.org|
|Zoom Links||video conferencing||Admin||Links to zoom meetings (scroll to the right)||email@example.com|
If you already use Google Calendar at your company, click here to add this calendar to your own.
The ICS file is also available for those not using Google Calendar. This should work with Outlook and other modern calendar apps.
ALL meetings should have someone with host privileges in control, and should be set to
When you use a RISC-V zoom account, the account will be zoom+xyz@riscv where xyz is one of the licenses we have allocated. You do NOT need to log in as this user.
Instead, join the meeting, then click the Participants in the main menu to bring up the Participants Panel
In the lower right you should see either the "Claim Host" button or the [...] area to get more options. "Choose Claim Host".
Enter the host code to become the host so you can moderate the meeting. Check your email from October 20, 2020 for the host code or request if from the Technical Program Managers at firstname.lastname@example.org.
If successful, your main menu should now look like this:
Once you have become host, you can now do such activities as recording the meeting, using breakout rooms, and other features.
To record meetings, simply press the "Record" button in the main menu and wait for the message that the meeting is recording. You may record on your computer or use the cloud.
Once recording as started, the main menu will now look like this:
When done recording, select "Pause/Stop Recording" or exit the meeting. If you elected to record you meeting on your computer, you'll be prompted for where to place the processed recording when you stop recording or leave the meeting. If you selected to have the meeting recorded to the cloud, it will be mailed to the owning email id for the session.