Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

252
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#riscv

2 posts2 participants0 posts today
Jean-Baptiste "JBQ" Quéru<p>In my little world of <a href="https://floss.social/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a>, I have stumbled across minor issues in some of the tools that I use.</p><p>I've had two cases so far where maintainers very quickly took my suggestion and made it available in their main branch. I've also had one where I haven't heard back from the maintainer, i.e. where I'm going to need to maintain my own fork (for <a href="https://floss.social/tags/RiscV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RiscV</span></a> compatibility). And that's OK. Beyond being glad that I got help, I'm glad that the original authors allow me also to do the work myself.</p>
Brad Linder<p>FireBeetle 2 is an upcoming $15 single-board PC with a low-power RISC-V processor, MIPI-CSI and MIPI-DSI interfaces, USb-C ports, WiFi, Bluetooth, and a microSD card reader. It's the size of Raspberry Pi Zero. <a href="https://linuxgizmos.com/updated-dfrobot-previews-risc-v-based-firebeetle-2-with-esp32-p4-targeting-image-and-video-applications/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">linuxgizmos.com/updated-dfrobo</span><span class="invisible">t-previews-risc-v-based-firebeetle-2-with-esp32-p4-targeting-image-and-video-applications/</span></a> <a href="https://fosstodon.org/tags/FireBeetle2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FireBeetle2</span></a> <a href="https://fosstodon.org/tags/RiscV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RiscV</span></a> <a href="https://fosstodon.org/tags/SingleBoardComputer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SingleBoardComputer</span></a></p>
deadprogram<p>Just released version 0.1 of TinyGo-TKey to develop apps for the Tillitis TKey-1 using TinyGo!</p><p><a href="https://github.com/hybridgroup/tinygo-tkey" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/hybridgroup/tinygo-</span><span class="invisible">tkey</span></a></p><p>TKey-1 is an open source, open hardware FPGA-based USB security token from the awesome team at Tillitis:<br><a href="https://tillitis.se/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tillitis.se/</span><span class="invisible"></span></a></p><p><a href="https://social.tinygo.org/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>golang</span></a> <a href="https://social.tinygo.org/tags/tinygo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tinygo</span></a> <a href="https://social.tinygo.org/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>embedded</span></a> <a href="https://social.tinygo.org/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://social.tinygo.org/tags/fpga" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fpga</span></a> <a href="https://social.tinygo.org/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a></p>
Jean-Baptiste "JBQ" Quéru<p>I finally got all my <a href="https://floss.social/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a> development tools to compile for <a href="https://floss.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a>, 3 of them were originally broken.</p><p>Usptream maintainers have already fixed 2 of them, and I've just filed a bug report for the last one.</p><p>RISC-V under qemu on my 13900K is about fast enough to emulate an Amstrad CPC at half speed. Hopefully I can get real hardware soon and get better performance. Ubuntu 25.10 is a few months away :)</p>
Flux<p>I'm considering <a href="https://mastodon.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> CPUs. I'm looking for open source RV32IMC with good debugging support and interrupts. Simplicity is more important than performance. I prefer Verilog. VexRiscv is an old favourite and Hazard3 is an interesting new option. What else should I consider? <a href="https://mastodon.social/tags/FPGA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FPGA</span></a></p>
Stewart X Addison<p><span class="h-card" translate="no"><a href="https://macaw.social/@andypiper" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>andypiper</span></a></span> If you find any more <a href="https://fosstodon.org/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a> hardware that I absolutely don't need then please let me know ;-)</p>
Olimex<p>More projects run on Open Source Hardware ESP32-P4-DevKit EUR 16 board with Espressif Dual Core RISC-V SOC <a href="https://www.youtube.com/shorts/PqLHHtLoO7w" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">youtube.com/shorts/PqLHHtLoO7w</span><span class="invisible"></span></a> <a href="https://mastodon.social/tags/esp32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>esp32</span></a> <a href="https://mastodon.social/tags/iot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iot</span></a> <a href="https://mastodon.social/tags/espressif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>espressif</span></a> <a href="https://mastodon.social/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a></p>
Rocky Linux :rockylinux:<p>🚨 It’s official: RISC-V will be joining the Rocky Linux 10 architecture lineup!</p><p>This milestone wouldn’t be possible without the incredible work of the Fedora RISC-V community. We’ve built on their upstream-first foundation to bring riscv64gc into the Rocky family—alongside x86_64, aarch64, ppc64le, and s390x.</p><p>Big thanks to <span class="h-card" translate="no"><a href="https://fosstodon.org/@fedora" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fedora</span></a></span>, @RISC-V International, and everyone helping push open hardware forward.</p><p>🧭 Read more: <a href="https://rockylinux.org/news/rockylinux-support-for-riscv" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">rockylinux.org/news/rockylinux</span><span class="invisible">-support-for-riscv</span></a><br><a href="https://fosstodon.org/tags/RockyLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RockyLinux</span></a> <a href="https://fosstodon.org/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> <a href="https://fosstodon.org/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fedora</span></a> <a href="https://fosstodon.org/tags/AltArch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AltArch</span></a></p>
Yogthos<p>Alibaba Group Holding launched the server-grade XuanTie C930 processor, designed for high-performance computing applications, including data-centers and autonomous vehicles. The chip will begin shipping to clients this month.</p><p>The open-source RISC-V instruction set architecture used in the C930 chip is expected to broaden domestic use of open-source chips in China, countering US tech restrictions.</p><p><a href="https://tech.yahoo.com/science/articles/alibabas-risc-v-chip-hits-093000410.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tech.yahoo.com/science/article</span><span class="invisible">s/alibabas-risc-v-chip-hits-093000410.html</span></a></p><p><a href="https://social.marxist.network/tags/china" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>china</span></a> <a href="https://social.marxist.network/tags/technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>technology</span></a> <a href="https://social.marxist.network/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jbqueru</span></a></span> and even then there are a lot of <a href="https://infosec.space/tags/distros" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>distros</span></a> that <em>should</em> be portable to <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> like <span class="h-card" translate="no"><a href="https://linuxrocks.online/@bunsenlabs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bunsenlabs</span></a></span> / <a href="https://infosec.space/tags/BunsenLabs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BunsenLabs</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> and <a href="https://infosec.space/tags/TinyCore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TinyCore</span></a>.</p><p>I just don't have an <a href="https://infosec.space/tags/OrangePi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OrangePi</span></a> <a href="https://infosec.space/tags/RV2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RV2</span></a> to target against...<br><a href="https://www.youtube.com/watch?v=Mln2j3VxAos" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">youtube.com/watch?v=Mln2j3VxAos</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jbqueru</span></a></span> OFC and in terms of <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> vs. <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM</span></a> it won't be competitive for quite some time as ARM includes a lot of <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proprietary</span></a> and <a href="https://infosec.space/tags/patented" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>patented</span></a> <a href="https://infosec.space/tags/PowerSaving" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PowerSaving</span></a> technologies that are just not available outside of said closed ISA.</p><ul><li>I do thus treat <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM64</span></a> like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a>: A <em>"black box"</em> that I cannot audit, verify or control beyond what it allows me to.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jbqueru</span></a></span> Also I hope for <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> to be the <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> of the future for long-term <a href="https://infosec.space/tags/OpenSourceHardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSourceHardware</span></a> and support.</p><p><a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM64</span></a> - just like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a> - is <em>yet another proprietary ISA</em> and almost all devices with it in terms of <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Laptops</span></a> have <a href="https://infosec.space/tags/AntiRepairDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AntiRepairDesign</span></a> like <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Apple</span></a>'s <a href="https://infosec.space/tags/MacBook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MacBook</span></a>|s that self-destroy their <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSD</span></a>|s which also contains it's <a href="https://infosec.space/tags/EFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EFI</span></a> / <em>"<a href="https://infosec.space/tags/BridgeOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BridgeOS</span></a>"</em>, <a href="https://www.youtube.com/watch?v=RYG4VMqatEY" rel="nofollow noopener noreferrer" target="_blank">making machines with fried SSDs <em>'braindead'</em>…</a></p><p>And yes, <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RAM</span></a> to also fails and making it not fully replaceable and upgradeable is inherently bad and I'm still mad at <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>frameworkcomputer</span></a></span> for their botched <a href="https://infosec.space/tags/FrameworkDesktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FrameworkDesktop</span></a> <a href="https://infosec.space/tags/PC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PC</span></a>!</p><ul><li>Cuz it's neither necessary nor beneficial for a <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Desktop</span></a> PC, unlike with the <a href="https://infosec.space/tags/Framework12" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Framework12</span></a> where the <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoC</span></a> used only supports single channel and a single SODIMM so it makes sense for them to take that into account.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jbqueru</span></a></span> personally, I hope for <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> to become <a href="https://infosec.space/tags/mainstream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mainstream</span></a> and be offered in more than just SBCs with <em><a href="https://infosec.space/tags/SolderedDownRAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SolderedDownRAM</span></a></em> but also regular formfactors like <a href="https://infosec.space/tags/UCFF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UCFF</span></a> / <a href="https://infosec.space/tags/NUC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NUC</span></a>, <a href="https://infosec.space/tags/MiniITX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MiniITX</span></a>, <a href="https://infosec.space/tags/MiniDTX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MiniDTX</span></a>, <a href="https://infosec.space/tags/microATX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microATX</span></a> &amp; <a href="https://infosec.space/tags/ATX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ATX</span></a>!</p>
Pierre-Alain TORETHas anyone given a try to <a href="https://snac.toret.fr?t=runbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#runbsd</a> <a href="https://snac.toret.fr?t=freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> or <a href="https://snac.toret.fr?t=netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a> on this <a href="https://snac.toret.fr?t=riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#riscv</a> motherboard <a href="https://store.deepcomputing.io/products/dc-roma-risc-v-mainboard-for-framework-laptop-13?variant=50663995146404" rel="nofollow noopener noreferrer" target="_blank">https://store.deepcomputing.io/products/dc-roma-risc-v-mainboard-for-framework-laptop-13?variant=50663995146404</a> ?<br>
David Chisnall (*Now with 50% more sarcasm!*)<p>Good luck to the <a href="https://infosec.exchange/tags/CHERI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CHERI</span></a> folks at the <a href="https://infosec.exchange/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> summit this week trying to convince the architecture review board not to mandate a specific capability format in the Y base architecture!</p><p>It would be a real shame to standardise a base architecture that is incompatible with accelerators, microcontrollers, or future versions of a Linux-capable system with a richer set of permissions. The Y base should be like the I base: not a stand-alone set of everything you need to build a usable system, but the common subset that <em>every</em> system needs. I hope you can persuade the RISC-V folks that new base architectures should respect the same principles as existing ones.</p>
YRabbit<p>New ten cent <a href="https://mastodon.sdf.org/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a> chip <a href="https://mastodon.sdf.org/tags/ch570" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ch570</span></a> from WCH. </p><p>There is a separate pin labeled “antenna”🙂 I really thought there was some Bluetooth inside, but it's only a radio module😕 </p><p>But I needed a USB-host and there it is! 😜 </p><p><a href="https://mastodon.sdf.org/tags/diy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>diy</span></a> <a href="https://mastodon.sdf.org/tags/electronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>electronics</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://fedi.catto.garden/users/gettie" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>gettie</span></a></span> that being said I've yet to see any competition since <a href="https://infosec.space/tags/Cyrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cyrix</span></a> got stomped out, <a href="https://infosec.space/tags/Transmeta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Transmeta</span></a> failed and <a href="https://infosec.space/tags/VIA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VIA</span></a> sold parts of <a href="https://infosec.space/tags/CentaurTechnology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CentaurTechnology</span></a> to <a href="https://infosec.space/tags/Zhaoxin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Zhaoxin</span></a> which now fab their stuff on <a href="https://en.wikipedia.org/wiki/Zhaoxin" rel="nofollow noopener noreferrer" target="_blank">16nm surplus'd</a> <a href="https://infosec.space/tags/TSMC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TSMC</span></a> nodes that were slated for export to <a href="https://en.wikipedia.org/wiki/MCST" rel="nofollow noopener noreferrer" target="_blank">MCST</a> but got embargo'd <em>for obvious reasons...</em></p><ul><li>Not that any of their chips were competitive past the <a href="https://infosec.space/tags/Cx586" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cx586</span></a>, and nowadays it'll be faster to run <a href="https://infosec.space/tags/86Box" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>86Box</span></a> on a <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> than <a href="https://en.wikipedia.org/wiki/Transmeta#Code_Morphing_Software" rel="nofollow noopener noreferrer" target="_blank">old silicon</a>...</li></ul><p>Still, it angers me since <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>OS1337</span></a></span> aims to be a foundation [to at least be able to recover data or backup/restore ancient hardware one can't get to run elsewhere]…</p><ul><li>Tho at least <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 6.6.x as <a href="https://infosec.space/tags/LTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LTS</span></a>-<a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kernel</span></a> release will still get fixes for quite some time...</li></ul>
Brad Linder<p>M5Stack Tab5 is a dev kit with a 5 inch touchscreen display, a 2MP camera, and an ESP32-P4 dual-core, 32-bit 400 MHz RISC-V processor, a 40 MHz RISC-V MCU, and a bunch of wired &amp; wireless I/O. Available now for $60. <a href="https://www.cnx-software.com/2025/05/09/m5stack-tab5-tablet-esp32-p4-iot-development-kit-5-inch-touchscreen-display-and-front-facing-camera/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cnx-software.com/2025/05/09/m5</span><span class="invisible">stack-tab5-tablet-esp32-p4-iot-development-kit-5-inch-touchscreen-display-and-front-facing-camera/</span></a> <a href="https://fosstodon.org/tags/ESP32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ESP32</span></a>-P4 <a href="https://fosstodon.org/tags/RiscV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RiscV</span></a> <a href="https://fosstodon.org/tags/DevKit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevKit</span></a> <a href="https://fosstodon.org/tags/M5StackTab5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>M5StackTab5</span></a> <a href="https://fosstodon.org/tags/M5Stack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>M5Stack</span></a></p>
omg! ubuntu<p>Ubuntu is serious about RISC-V, as news that its bringing Ubuntu 24.04 desktop to the Qualcomm Dragonwing Vision Kit shows </p><p><a href="https://www.omgubuntu.co.uk/2025/05/ubuntu-24-04-desktop-qualcomm-dragonwing-release" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">omgubuntu.co.uk/2025/05/ubuntu</span><span class="invisible">-24-04-desktop-qualcomm-dragonwing-release</span></a> </p><p><a href="https://floss.social/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a> <a href="https://floss.social/tags/ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ubuntu</span></a> <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linux</span></a></p>
rk: it’s hyphen-minus actually<p>Noodling around with RISC-V emulation, writing it in Go.</p><p>Supporting the atomic extension should be doable using Go atomics, but to do it right and without resorting to unsafe, I'd have to represent memory as a slice of int32s and do bullshit to read/write anything smaller than that if I want to have any sort of ergonomics on the atomic usage.</p><p>(Assuming I wanna support more than one CPU/HART running concurrently.)</p><p><a href="https://mastodon.well.com/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a> <a href="https://mastodon.well.com/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>golang</span></a> <a href="https://mastodon.well.com/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://mastodon.well.com/tags/emulation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>emulation</span></a></p>
ExploreLive feeds
About