Conversation

Notices

1. Embed this notice
   Greg K-H (gregkh@social.kernel.org)'s status on Tuesday, 29-Jul-2025 15:50:54 JST Greg K-H
   Looks like the risc-v community is learning from history! Hopefully this results in more upstream development efforts: https://riscv.org/blog/2025/07/risc-v-upstreaming/
   • Embed this notice
     Greg K-H (gregkh@social.kernel.org)'s status on Wednesday, 30-Jul-2025 14:26:40 JST Greg K-H

     in reply to

     • Alex
     • Marcin Juszkiewicz 🙃
     @stsquad @hrw Fixing the lack of almost all riscv soc drivers to be upstream so that I can boot a kernel.org release on one of them (i.e. a normal developer can test their changes) would be a good start. Which is one of the things that article says...
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Alex (stsquad@mastodon.org.uk)'s status on Wednesday, 30-Jul-2025 14:26:41 JST Alex

     in reply to

     • Marcin Juszkiewicz 🙃

     @hrw
     Any particular mistakes? I think System Ready for Client PC's could of come sooner and maybe we should have spent less time arguing about Device Tree vs ACPI but in general the standardisation push was the right thing - it's just poorly distributed.
     @gregkh

   • Embed this notice
     Marcin Juszkiewicz 🙃 (hrw@society.oftrolls.com)'s status on Wednesday, 30-Jul-2025 14:26:43 JST Marcin Juszkiewicz 🙃

     in reply to

     @gregkh

     That post reminds me many moments in Arm architecture history...

     Creation of armhf to have all distros target the same armv7.

     Creation of Linaro and work done by people there.

     SBSA, BSA specifications which tries to define aarch64 hardware and firmware interfaces.

     Work done on making enterprise Linux distros running on aarch64 servers.

     I hope that RISE will not follow aarch64 mistakes.