Beyond the significant PCI-e requirements, I'm tickled pink that many of the server platform requirements are "do what x86 does"... ACPI, UEFI, a TPM. I hope they do a better job with standards compliance than some of the shadier Wintel OEMs!
CUDA is proprietary technology, guarded by patents and mostly closed-source. And its originator, NVIDIA, while being a member of the Khronos consortium, and technically supporting OpenCL, makes it much more difficult for you to do anything in OpenCL than in CUDA - even though it is sometimes almosy zero effort to enable some OpenCL equivalent (e.g. : Half-precision types. They exist in CUDA; in OpenCL on NVIDIA - you can't have them).
So, live with CUDA on other hardware? No thank you.
The interesting part is that this is less "CUDA now runs on RISC-V" and more "Nvidia is defining what a CUDA-capable RISC-V server has to look like."
That could end up being a pretty influential de facto server profile for the architecture.
Beyond the significant PCI-e requirements, I'm tickled pink that many of the server platform requirements are "do what x86 does"... ACPI, UEFI, a TPM. I hope they do a better job with standards compliance than some of the shadier Wintel OEMs!
All these AI do is eat hot chip and lie
Any fab born after 2005
related: https://www.sifive.com/development-platforms/sifive-bigsky-s...
When does bigsky ship?
hot chips. hot planet.
CUDA is proprietary technology, guarded by patents and mostly closed-source. And its originator, NVIDIA, while being a member of the Khronos consortium, and technically supporting OpenCL, makes it much more difficult for you to do anything in OpenCL than in CUDA - even though it is sometimes almosy zero effort to enable some OpenCL equivalent (e.g. : Half-precision types. They exist in CUDA; in OpenCL on NVIDIA - you can't have them).
So, live with CUDA on other hardware? No thank you.
Just make more RAM.