Graphics
Separating the Wayland Compositor and Window Manager
<p>Current Wayland compositor implementations handle window management and compositing in the same monolithic process. Wayland does not however force this architecture.</p>
<p>I am the author of the <a href="https://isaacfreund.com/software/river/">river</a> Wayland compositor. It supports a custom Wayland protocol, <a href="https://codeberg.org/river/river/src/branch/main/protocol/river-window-management-v1.xml">river-window-management-v1</a>, which allows a special "window manager" Wayland client to handle all window management policy, draw server side decorations, setup keybindings, and more.</p>
<p>My goal with this work is to make hacking on Wayland window managers significantly more accessible and promote ecosystem diversity. There is already a <a href="https://codeberg.org/river/wiki/src/branch/main/pages/wm-list.md">growing list of window managers</a> developed for the new protocol.</p>
<p>This talk will give an overview of this new protocol and the advantages/disadvantages of separating the Wayland compositor and window manager. There will also be a brief demo.</p>
Additional information
| Live Stream | https://live.fosdem.org/watch/k4601 |
|---|---|
| Type | devroom |
| Language | English |
More sessions
| 2/1/26 |
<p>A couple years ago, Alyssa Rosenzweig developed a compute-based geometry and tessellation shader implementation for the Asahi (OpenGL) and Honeykrisp (Vulkan) drivers. Since then, the core of this implementation has been extracted into a common library within Mesa called libpoly. In this talk, Faith will talk about the changes needed to libpoly as well as panvk in order to integrate libpoly into panvk for geometry shader support on Mali GPUs.</p>
|
| 2/1/26 |
<p>This years update on the FOSDEM videobox!</p> <p>FOSDEM is a massive event with 30 different tracks spread over two days. Our goal is to not only capture video of every talk, but also to fully live stream everything. In this talk, the current versions of the hardware and software powering this crazy endeavour will be presented.</p>
|
| 2/1/26 |
<p>In October 2023, when Raspberry Pi 5 was announced, a new version of Raspberry Pi OS based on Debian 12 Bookworm was released. After two years, in October 2025, the new release based on Debian 13 Trixie was released. </p> <p>This talk will review what improvements have been made in the graphics stack of the Raspberry Pi, focusing on the kernel (v3d) and user space (v3d/v3dv) GPU driver upgrades. </p> <p>Now all Trixie Raspberry Pi users are taking advantage of Mesa 25.0.7. It exposes Vulkan ...
|
| 2/1/26 |
<p>Along the years, FOSDEM and its Graphics Devrooms have featured many talks about the status of different Mesa3D drivers. But what is Mesa3D? How did the project start? How is it structured?</p> <p>This talk provides a comprehensive introduction to Mesa3D, aimed at people who have some graphics knowledge, but have never written a GPU driver. We will trace the project from its origins to being the industry standard for several vendors nowadays.</p> <p>More specifically, we will cover its ...
|
| 2/1/26 |
<p>With the sunsetting of Xorg based environments the need for bespoke window management experiences has not gone away. But a new approach is needed that fits the Wayland paradigm.</p> <p><a href="https://canonical.com/mir">Mir</a> is a library for building Wayland compositors that supports a wide range of projects with their own Window Management needs: 1. embedded displays with a single fullscreen app (<a href="https://ubuntu.com/frame">Ubuntu Frame</a>); 2. phones and tablets with multiple ...
|
| 2/1/26 |
<p>This talk introduces Tyr, a new Rust-based GPU driver for the Linux kernel. We’ll begin with a brief look at how modern GPUs work before diving into Arm’s GPU architecture and explain how it’s supported at the kernel level, highlighting the key components of a Linux GPU driver. We’ll conclude with an overview of the project’s current status and what’s ahead on the roadmap.</p>
|
| 2/1/26 |
<p>Like most window-system architectures, X is fundamentally event-driven. So why not use an API that reflects that?</p> <p>This talk is about an X interface library which is built on event-driven paradigms from the ground up. It sits in the same place in the software stack as Xlib and xcb; it's an alternative to them for an application to use when talking to the X server, most appropriate for applications which are themselves event-driven.</p>
|
