Hello Everyone,
This is a discussion thread for evaluating the best approach when porting TempleOS to RISC-V. If you are on board with this project, I assume that you are at least somewhat familiar with RISC-V and leave out further explanations about its nature.
However, I wish to go into detail about the motivations about this project and the current state of the target platform
>Why port to RISC-V
Temple OS is brilliant in its approach of trying to be a modern Commodore 64, with it's lack of drivers and permanent Ring 0 operation. However, modern computers, including the x86 platform it was originally written for, are not suitable for an operating system which strives to hide nothing from the end user. Thanks to proprietary firmware (like the UEFI platform initialization code for modern chipsets) and Intel micro code, writing a bare metal application in x86-64 assembly turns out to be actually pretty high level at the end of the day. As such, having an open source software stack like GNU/Linux or Temple OS on a platform with proprietary firmware is paradoxical. RISC-V strives to be the first truly open source ISA standard, allowing anyone to implement it. Of course, at the end of the day someone will have to manufacture the actual hardware, but since RISC-V is completely open, eventually someone will come along to make a botnet free home-computer, which will be the perfect match for Temple OS
>Current RISC-V hardware situationto be continued...
Hello Everyone, This is a discussion thread for evaluating the best approach when porting TempleOS to RISC-V. If you are on board with this project, I assume that you are at least somewhat familiar with RISC-V and leave out further explanations about its nature.
However, I wish to go into detail about the motivations about this project and the current state of the target platform
>Why port to RISC-V Temple OS is brilliant in its approach of trying to be a modern Commodore 64, with it's lack of drivers and permanent Ring 0 operation. However, modern computers, including the x86 platform it was originally written for, are not suitable for an operating system which strives to hide nothing from the end user. Thanks to proprietary firmware (like the UEFI platform initialization code for modern chipsets) and Intel micro code, writing a bare metal application in x86-64 assembly turns out to be actually pretty high level at the end of the day. As such, having an open source software stack like GNU/Linux or Temple OS on a platform with proprietary firmware is paradoxical. RISC-V strives to be the first truly open source ISA standard, allowing anyone to implement it. Of course, at the end of the day someone will have to manufacture the actual hardware, but since RISC-V is completely open, eventually someone will come along to make a botnet free home-computer, which will be the perfect match for Temple OS
>Current RISC-V hardware situation to be continued...