I'll be presenting some of my latest work on Xous & Baochip with @Xobs at #39C3 on Day two, 11PM room One:

https://fahrplan.events.ccc.de/congress/2025/fahrplan/event/xous-a-pure-rust-rethink-of-the-embedded-operating-system

Hope to see you there!

For more on Baochip, checkout bluesky: https://bsky.app/profile/baochip.com or read the source at github: https://github.com/baochip/baochip-1x

The TL;DR is that Baochip is a "mostly-open" RTL SoC in 22nm TSMC, purpose-built for Xous and expressly packaged for IRIS inspection. It packs in five RISC-V CPU cores (one Vexriscv CPU at 350MHz, and four PicoRV's at 700MHz), 2MiB on-chip SRAM and 4MiB on-chip RRAM (basically FLASH).

I'm aiming to have the chip broadly available by early 2026. Right now I have first silicon. You can follow development & ask questions on the Baochip discord at https://discord.gg/yesbcPF9Xy

Sorry, no website yet - I suck at marketing - but hey, at least the source code is up!

@draconigen @drahardja
Color: sand. I think a smart girl knows where to find a cheap silicon refining machine^W creature.

@ljs I remember just using ps (and have in my stash lots of debugging)

@ljs anyway, not sure if you're just venting or do need help, but just in case, checking the qemu cmdline and guest kernel options might be where I'd start.

@ljs just checked, nothing local here. But I haven't tested it in a while.

@ljs yeah I might have had patches for that, don't think they are upstream.

At the 2025 #Linux #Kernel Maintainers Summit this week the "rust for Linux" experiment has just been deemed concluded (https://lwn.net/SubscriberLink/1050174/6b6d55c90ce1100f/ ).

Rust for Linux maintainer Miguel Ojeda now submitted a patch to follow up on that and remove the "The Rust experiment" section from the #Linux #kernel's docs, as "Rust is here to stay":

conclude the Rust experiment – https://lore.kernel.org/lkml/20251213000042.23072-1-ojeda@kernel.org/

He writes:

""The Rust support was merged in v6.1 into mainline in order to help determine whether Rust as a language was suitable for the kernel, i.e. worth the tradeoffs, technically, procedurally and socially.

At the 2025 Linux Kernel Maintainers Summit, the experiment has just been deemed concluded.

Thus remove the section -- it was not fully true already anyway, since there are already uses of Rust in production out there, some well-known Linux distributions enable it and it is already in millions of devices via Android.

Obviously, this does not mean that everything works for every #kernel configuration, architecture, toolchain etc., […]

But the experiment is done, i.e. Rust is here to stay.

I hope this signals commitment from the kernel to companies and other entities to invest more into it, e.g. into giving time to their kernel developers to train themselves in Rust.

[…]""

#LinuxKernel #Rustlang

Note that the name of the primary author, Nikolaj Bjørner (of Dane origin), does not appear anywhere in the page or page source.

Did you know? Z3 is written in Dane, apparently.

@fasterthanlime it's even funnier because the clickbait seems entirely accidental:
https://hachyderm.io/@kernellogger/115694406218280742

The end of the kernel Rust experiment

https://lwn.net/Articles/1049831/ #LWN

The Paris Rust meetup @ Criteo will be starting soon (tm)! I have a quick presentation on Rust tips for Advent of Code.

@benjojo

It's somewhat nice that malicious crypto miners exist, because they seem to be way faster (for most cases) on the uptake of new RCE exploits and they do fairly harmless (CPU time abuse) actions.

Friend found their react server components server down, and upon investigating found the docker container that normally had their JS server process in, was now ./3s83jmfv.out (I guess it had killed the main process to secure a monopoly for that instance)

Annoying? Sure, but that is way better than "hello I have just nicked your .env file and ransomware/blackmailed you"

I for one am glad that the crypto mining worm people are here to out-compete the more nasty people!

@benjojo