Open Source | Three Parties Collaborate to Build an Open Source Dream, with Tens of Thousands of Lines of Code Merged into the Mainline.
We sincerely thank the PLCT team from the Institute of Software at the Chinese Academy of Sciences (special thanks to the project maintainer, Professor Wang Chen), the team led by Professor Dai Hongjun from Shandong University, the Guo Ren team from Pinecone Semiconductor, the Taixiao Linux Community team, the Milk-v team, and all outstanding open-source community developers, including Jisheng Zhang and inochi amaoto.
We are pleased to announce that on November 2nd, Beijing time, Alcu’s CV1800B and SG2042 achieved preliminary support and were merged into the Linux 6.7 mainline. This marks the first official support and maintenance by Linux for Alcu’s products and the first time two processors from the RISC-V camp have entered the Linux 6.7 mainline. Alcu will continue to adhere to the philosophy of open-source collaboration, working together with the global open-source community to enhance the RISC-V software ecosystem.
Phoronix, a well-known overseas technical website, commented: “Also notable with the Linux 6.7 SoC updates is initial support for Sophgo RISC-V processors. The CV1800B is now supported as used by the Milk-V Duo board.”
“But even more exciting than that little Milk-V Duo board is preparations for the Sophgo SG2042. The SG2042 is being used by the Milk-V Pioneer for a 64-core RISC-V mATX workstation board.”
Educational Note: Why Do We “Upstream”?
The significance of “doing upstream” lies in directly interacting with the open-source community and addressing issues at the source. This process is known as “upstream first.” The primary operation in the open-source community is maintaining the mainline version, which is referred to as the “upstream.” Once you submit code or make modifications, these are considered “upstream.” Additionally, “upstream first” is an excellent open-source principle, with the core idea that any modifications based on open-source projects should be submitted first to the upstream project itself and then included in one’s own product. The benefits of this approach include avoiding duplication of work, reducing the likelihood of errors and conflicts, and being able to promptly access the latest feature updates.