The Linux RISC-V Kernel has adopted a policy to accept patches only for frozen/ratified RISC-V specs. This was done to align with RISC-V spec development process of the RISC-V Foundation and avoid maintenance burden. Considering the time taken by RISC-V spec development process, is there a better policy which Linux RISC-V Kernel can adopt ??
Projects such as QEMU RISC-V and OpenSBI have been accepting patches for draft specs without any issues. The policy adopted by these projects is as follows:
1) Features/functionality pertaining to draft spec will not be enabled by default
2) Backward-compatibility will not be maintained for features/functionality pertaining to draft spec
This talk is a place-holder for discussing above described Linux RISC-V Kernel Policy on draft specs.
|I agree to abide by the anti-harassment policy||I agree|