RISC-V: scope of the open specification
AbstractYou may read the RISC-V instruction set and build a processor without a use fee. The computer around it still needs separate permissions for core designs, physical circuits and firmware.
You can read the RISC-V instruction set, implement it and ship a processor without a use fee. A student and a chip company can work towards the same published target. Ubuntu already does.
For the computer around that processor, there are further questions. The instruction-set label does not identify the core design, memory circuits, boot firmware or compiler. Each layer has its own terms. The first grant is real. It is not a grant for the machine.
Open terms, written down
RISC-V passes Read and Build under the three tests. The ISA manual uses Creative Commons Attribution 4.0; the FAQ states “There is no fee to use the RISC-V ISA”. A contributing member’s necessary-claims grant is royalty-free for licensed implementers.
For commercial use of the name and logo, organisational membership and the agreement are required. Non-commercial research and academic projects have the guidelines’ route. The ISA is free to implement; commercial use of the name has separate terms.
The grant covers the compliant part, not the surrounding product. A CPU must fully implement the relevant normative elements of at least one final base specification. Partial or non-conforming implementations fall outside it; other IP may still be needed, possibly for a fee.
These are different choices from the PCIe terms, with their $4,500 non-member hard copy and patent arrangement among members. A shared computing interface can be made available without selling its use.
A shared target is what openness buys
A profile tells software which extensions it may assume. RVA23 defines user and supervisor requirements, including standard vector support and the hypervisor extension. It is a common target, not a complete platform.
Ubuntu 25.10 targets RVA23S64. Systems that do not meet it cannot run that release; earlier hardware stays on Ubuntu 24.04. The Server Platform specification also requires RVA23S64 for every application processor. A student-built core and a commercial one that conform have the same published software target.
The profile specifies neither peripherals, boot nor execution environment, and sets no performance requirement. Custom extensions can sit beside it. For proof, a chip’s label needs more than the label.
SpacemiT’s K3 datasheet calls its X100 cores fully RVA23-compliant while labelling its A100 AI cores RVA23* without the hypervisor extension that RVA23S64 requires. These are vendor claims. RISC-V International supplies architectural tests, run by chip makers on their own testbenches; coverage of RVA23 was not established.
Independent conformance results are still needed.
The gate moves to the core
The ISA specifies behaviour. For the circuit design that performs it, choose a core and read another licence.
| Core | Licence |
|---|---|
| Rocket Chip | Apache 2.0 and a BSD-style licence |
| BOOM | BSD 3-clause |
| CVA6 | Solderpad Hardware Licence 0.51 |
| XiangShan | Mulan PSL v2 |
| VexRiscv | MIT |
| PicoRV32 | ISC |
These are openly licensed designs, not a finding that any meets RVA23 or that every RISC-V chip contains one. Commercial cores have separate terms. SiFive describes revenue from upfront licensing fees and royalties based on the chip’s selling price.
You may design a core for the ISA. The core inside the chip you buy need not be open.
The gate moves to the circuits
Memory, PCIe and USB use physical-layer circuits, or PHYs, outside the ISA. K3 lists LPDDR5 and LPDDR4x memory and six integrated PHYs, three shared between PCIe and USB. Its datasheet does not identify their source. Licensed LPDDR5X PHY IP is sold on the market; that does not establish whose PHYs K3 uses.
At this layer, the instruction-set label supplies no answer about origin or terms. The buyer still needs one.
Where the lower layers are already open
Much of the firmware and toolchain is available for inspection and reuse. Boot, discovery and devices remain platform matters: “Profiles only describe ISA features, not a complete execution environment.” (profiles).
| Layer | Status |
|---|---|
| OpenSBI firmware | BSD 2-clause |
| U-Boot boot loader | GPL 2.0 |
| SBI specification | In RISC-V International’s ratified library |
| Boot and Runtime Services | Same library |
| UEFI and ACPI | UEFI Forum; implementation through a free adopter membership |
GCC uses GPL 3.0 with a runtime-library exception. LLVM uses Apache 2.0 with LLVM exceptions. The firmware is openly licensed, the specifications come from two bodies, and a builder can assemble much of this layer from public sources. It does not reveal circuits whose origin is absent from a datasheet.
The gate returns through extensions
The ISA reserves custom encodings. Extensions outside RISC-V International’s definitions are non-standard. The compiler must know which ones your chip uses.
T-Head’s XTheadVector is non-standard and non-conforming: its encodings overlap the standard vector extension, it follows vector 0.7.1 rather than ratified 1.0, and tools should report an error if both are enabled. Customisation may be useful. Software built for a vendor’s extension may run only on that vendor’s chips.
The compiler can be open while its output loses portability.
Open means every layer
RISC-V demonstrates that an instruction set can be published, adopted and shipped without a use fee. The student has a real starting point. The core, PHYs, firmware, toolchain and extensions still need their own permissions.
Agenxy proposes that every processor sold as open identify the licence at each of those layers and publish independently run results for its claimed profile. A buyer deciding what they can inspect, repair or reproduce needs to know which parts are available. Calling the ISA open does not supply a usable computer. The freedom to build one must reach the rest of it.
Sources
The contributing-member grant is in Regulations appendix A, section 2; compliance is defined in schedule 1. The Regulations were amended on 27 July 2023; branding guidelines updated on 31 October 2025. RVA23 was ratified on 21 October 2024. Server Platform v1.0 was ratified/listed in May 2026. K3’s datasheet is V1.9, 24 September 2026.
RVA23U64 requires the 64-bit base, M, A, F, D, C, B and V, with smaller extensions including Zicond, Zcb, Zfa, Zawrs and Supm. RVA23S64 adds Sv39, Sstc and Sha, including H, under privileged architecture 1.13. Full lists are in the ISA manual. Profiles are now part of that manual.
SBI v3.0 was listed in July 2025; Boot and Runtime Services v1.0 in August 2025.
Sources, including the repository licences, were consulted on 10 October 2026.