2025-08-06 TSC Meeting
Date
Aug 6, 2025
Disclosures
Participants
Agenda
Minutes Approval
Announcements
Proposal of Work
Profiles
Strategic Priorities
Presentations
None
Votes
Notes & Action Items
Meeting transcript and video: link
Summary
Announcements
The meeting began with announcements, including the introduction of Tariq Kurd as a new strategic representative and the opening of nominations for TSC chairs. Jeff noted that the chairs election would occur in two weeks. Guy announced the creation of a blog to report on and gather feedback about meetings.
RVV Digital Signal Processing Task Group Proposal for Work
Dmitry presented a proposal for organizing an RVV Digital Signal Processing Task Group to define extensions for more efficient signal processing across various applications, including wireless audio, voice, and automotive. He highlighted gaps in existing RVV support, such as wider accumulators and more efficient arithmetic operations, and outlined objectives like refining application domains, identifying benchmarks, and defining extensions with potential sub-sets. The group aims to reuse RVV 1.0 infrastructure, focus on integer/fixed-point operations, and create specifications with support from organizations like IBM, Synopsis, China Telecom, and others. Derek inquired about overlaps with existing extensions, to which Dmitry explained that while there is functional overlap, the proposed approach leverages RVV's infrastructure for scalable and efficient processing.
Dmitry discussed the status of some relevant specifications and prototypes from Synopsis and others, noting that while initial material exists, it will need review and recombination due to known issues. They agreed to proceed with a broader review of the proposal, with Dmitry and his team given approval to move forward.
RVA23.1 and RVB23.1 Proposal
The Technical Steering Committee (TSC) discussed the development of new profiles RVA23.1 and RVB23.1, which will include five optional extensions. David Weaver explained that these minor releases follow a 6-month to 1-year schedule and outlined the differences between RVA and RVB classifications. The committee agreed to proceed with a fast-track process for these profiles, with a deadline of August 31st for considering new extensions. Greg clarified that the TSC's role was to provide initial feedback, and the process would continue through the Architecture Review Committee. The conversation ended with a brief mention of strategic priorities for community individuals, which Guy requested to discuss further.
Strategic Priorities for Community/Individuals
Guy led a lengthy discussion about the collected information. Some common themes were identified such as many items appear to be too vague or raising issues which have already been addressed. Several companies appear to not be members and most likely are items from Individual members. Common topical areas included cryptography, trusted execution, vector/matrix, and microcontroller needs.
Next steps for the Community/Individual requirements is that the RISC-V Staff will filter the names/companies. Then, Guy will review and summarize with action items.
Detailed Notes
Quorum achieved at 0:12 into meeting
Agenda items
RVV Digital Signal Processing Task Group Proposal for Work
Discussion:
How differ from P extension is there any logic?
Answer: This is built on RVV. Higher throughput is targeted but has some similarities. Andes feels this will help in areas like FFT.Some specifications have been created by sponsors and will be reviewed. These will be reviewed and used as foundational
Approved by TSC Chair and Vice-chair to proceed to Member Review
RVA23.1 and RVB23.1 Proposal
Discussion:
Explanation of Expansion v. Development
Why are the asterisks in RVB column and not RVA?
Answer: Felt RVB options would move faster than would for RVA.When would the cut-off date for ratification?
Answer: Allowed for inclusion of next Board meeting, but not further. Could move, but was picked to begin execution.Will proceed to ARC for Fast Track review.
Strategic Priorities for Community/Individuals
Working information: link
Adjournment
Motion to Adjourn Made By:
Seconded By:
Time Adjourned:
