What’s next for Tyr?
In a new @lwn subscriber-only article, Daniel Almeida explores a possible 2026 roadmap for upstreaming Tyr — a Rust driver for CSF-based Arm Mali GPUs — and shares his thoughts on the path forward.
What’s next for Tyr?
In a new @lwn subscriber-only article, Daniel Almeida explores a possible 2026 roadmap for upstreaming Tyr — a Rust driver for CSF-based Arm Mali GPUs — and shares his thoughts on the path forward.
Linux kernel framework for PCIe device emulation, in userspace
https://github.com/cakehonolulu/pciem
#HackerNews #LinuxKernel #PCIE #Emulation #Userspace #Technology #Development
Working on mainline Linux? 🤔
Upstream early for feedback, or wait until your code is fully polished?
Early upstream = faster feedback, early rework hints, collaboration from day one.
Waiting = fewer distractions for maintainers, cleaner mailing lists, less churn.
What’s your take? #LinuxKernel
The Linux kernel's Rust support has been officially approved, marking the end of its experimental phase and paving the way for broader memory-safe adoption. 🚀🐧💻 A game-changer for kernel stability! Details: https://www.heise.de/en/news/Linux-Kernel-Rust-Support-Officially-Approved-11109808.html #LinuxKernel #Rust #OpenSource #Newz
Linux Kernel Rust Code Sees Its First CVE Vulnerability
https://www.phoronix.com/news/First-Linux-Rust-CVE
#HackerNews #LinuxKernel #RustCVE #Vulnerability #CyberSecurity #OpenSource #TechNews
The Linux kernel's Rust support has been officially approved, marking the end of its experimental phase and paving the way for broader memory-safe adoption. 🚀🐧💻 A game-changer for kernel stability! Details: https://www.heise.de/en/news/Linux-Kernel-Rust-Support-Officially-Approved-11109808.html #LinuxKernel #Rust #OpenSource #Newz
The Input Stack on Linux – An End-To-End Architecture Overview
https://venam.net/blog/unix/2025/11/27/input_devices_linux.html
Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:
#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else
We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""
The Input Stack on Linux – An End-To-End Architecture Overview
https://venam.net/blog/unix/2025/11/27/input_devices_linux.html
Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:
#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else
We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""
Once again saw someone blaming the #rust support in the #Linux #kernel for their problems, when in fact the problem at hand had nothing at all to do with it[1].
Kinda funny but also quite worrying at the same time.
See the slightly edited screenshot from a chatroom message below for an example from today. If you look closer, you see that it is a segfault in a userspace #rustlang program.
[1] I once even saw someone complaining when the kernel in fact did not even have CONFIG_RUST enabled…
Once again saw someone blaming the #rust support in the #Linux #kernel for their problems, when in fact the problem at hand had nothing at all to do with it[1].
Kinda funny but also quite worrying at the same time.
See the slightly edited screenshot from a chatroom message below for an example from today. If you look closer, you see that it is a segfault in a userspace #rustlang program.
[1] I once even saw someone complaining when the kernel in fact did not even have CONFIG_RUST enabled…
Quick reminder on the likely reason why Valve's New Steam Machine only supports #HDMI 2.0:
""At this time an open source HDMI 2.1 implementation is not possible without running afoul of the HDMI Forum requirements.""
This is what Alex Deucher, the maintainer of the amdgpu #kernel driver, said one and a half years ago here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1417#note_2303163
And from the ticket it looks like the problem remains.
See also Alex's earlier comment from early 2021 in the ticket:
https://gitlab.freedesktop.org/drm/amd/-/issues/1417#note_830547
""HDMI 2.1 is not available on #Linux due to the HDMI Forum.""
Quick reminder on the likely reason why Valve's New Steam Machine only supports #HDMI 2.0:
""At this time an open source HDMI 2.1 implementation is not possible without running afoul of the HDMI Forum requirements.""
This is what Alex Deucher, the maintainer of the amdgpu #kernel driver, said one and a half years ago here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1417#note_2303163
And from the ticket it looks like the problem remains.
See also Alex's earlier comment from early 2021 in the ticket:
https://gitlab.freedesktop.org/drm/amd/-/issues/1417#note_830547
""HDMI 2.1 is not available on #Linux due to the HDMI Forum.""
3/ Linus weighted in on the "guidelines for tool-generated content" for #Linux debate:
""[…] Honestly, I think the documented rule should not aim to treat AI as anything special at all, and literally just talk about tooling.
Exactly because we've used things like coccinelle (and much simpler tools like 'sed', for that matter) for ages.
IOW, this should all be about "tool-assisted patches should be described as such, and should explain how the tool was used". […]""
See https://lore.kernel.org/lkml/CAHk-=wgEPve=BO=SOmgEOd4kv76bSbm0jWFzRzcs4Y7EedpgfA@mail.gmail.com/ for details. And the later replies https://lore.kernel.org/lkml/CAHk-=wir-u3so=9NiFgG+bWfZHakc47iNy9vZXmSNWSZ+=Ue8g@mail.gmail.com/ and https://lore.kernel.org/lkml/CAHk-=whczwG=+-sAzoWoTY_VOwdFH3b5AkvQbgh+z98=p1iaXA@mail.gmail.com/
The latter contains:
""
> Copyright reasons, mainly.
I really don't see the argument.
The copyright issues are all true for all other code too. In fact, the copyright issues are a thing whether tools were involved or not.
Copyright is *always* a thing. […]""
The Linux Kernel Looks to "Bite the Bullet" in Enabling Microsoft C Extensions
https://www.phoronix.com/news/Linux-6.19-Patch-Would-MS-Ext
#HackerNews #LinuxKernel #MicrosoftCExtensions #OpenSource #TechNews #Phoronix
The #Linux developers currently discuss a new document covering "guidelines for tool-generated content"
https://lore.kernel.org/all/20251105231514.3167738-1-dave.hansen@linux.intel.com/
""The shiny new AI tools (chatbots, coding assistants and more) are impressive. Add new Documentation to guide contributors on how to best use #kernel development tools, new and old.""
Working on mainline Linux? 🤔
Upstream early for feedback, or wait until your code is fully polished?
Early upstream = faster feedback, early rework hints, collaboration from day one.
Waiting = fewer distractions for maintainers, cleaner mailing lists, less churn.
What’s your take? #LinuxKernel
