6 ms·
My understanding is its contained to the "edges", mostly in drivers and not in the "core" kernel. Still interesting indeed.
by Alupis 1y ago
My understanding is its contained to the "edges", mostly in drivers and not in the "core" kernel.
Still interesting indeed.
- preisschild 1y agofor now, due to gcc-rs not being completed yet and the rustc compiler not supporting every linux architecture
- dralley 1y agoThere's two gcc-based compilers for Rust, gcc-rs which is part of the gcc suite and written in C++, and rustc_codegen_gcc, which is an optional backend for the existing Rust compiler written in Rust which emits an intermediate representation that GCC can understand. rustc_codegen_gcc is much closer to completion.
- lights0123 1y agoIt surprised me that Linux 6.12's QR code generator is written in Rust and enabled in at least Arch and Fedora.
- jeffbee 1y agoWhy does the kernel need a QR code generator?
- lights0123 1y agohttps://www.phoronix.com/news/Linux-6.12-DRM-Panic-QR-Code https://www.phoronix.com/news/Linux-6.12-DRM-Panic-QR-Code
- infogulch 1y agoOh that's pretty nifty. It's always been a pita to get data (logs, traces, metadata etc) off of a crashed system. This is less human readable, but any human that wants to read it will want the raw data anyway. Way easier to do this than try to run photos of a screen through OCR.
- deleted 1y ago[deleted]
- Twirrim 1y agoA QR code can capture 3k of data, you can capture a lot of context and details in that, particularly if you apply a little bit of compression (and the kernel has compression algorithms embedded in it). More than can be captured on a screen normally, without it zooming out of sight.
- jeffbee 1y agoAn 80x25 ascii display carries 2000 characters which isn't shabby. But yeah, a lot harder to photograph.
- 6SixTy 1y agoWould most people rather have a cell phone picture of the screen for debug logs, or a QR code that has those logs ready to be scanned and copy/pasted?