So a bit like extending Mozilla Application Suite aka Seamonkey instead of focusing on standalone products?
cmhe
joined 2 years ago
AFAIK, UEFI isn't technically a requirement. However, TPM 2.0 is, and that requires UEFI.
TPM 2.0 does not require UEFI. I have a system here with TPM 2.0 and only legacy boot support. And you can just buy a TPM 2.0 module and connect it with any board, that has a SPI connector.
TBH, it is very difficult to me differentiating between the different flavors of authoritarians.
Maybe someone can make an easy to understand comparison matrix? You know, "Kills people because they have a different opinion.", "Suppresses minorities.", etc.
Matrix is federated, Signal is not.
Not necessarily, RISC-V is permissibly licensed, so they could add proprietary extensions, that would make the binaries or even compilers only work with their implementation of the RISC-V ISA.
Embrace, Extend, Extinguish tactics would work on RISC-V, and I trust billionaires and huge corporations to enshittify it.
Big player joins RISC-V, creates design, introduces proprietary extensions, builds compilers that use them, software depend on them, other RISC-V designers need to license them, because the whole platform now depends on them.
Also based on how complicate it is to port Linux to different SoCs, which at least share a common ISA, it will be much more difficult if you need to support even more RISC-V ISAs with different proprietary extensions, not only in the kernel, but in the toolchain as well.