docs: add direct session validation runbook

This commit is contained in:
Samuel Onoja committed 2026-09-24 16:45:57 +01:00
1 parent a9c70b0c2d
commit dccf83c8fa
2 files changed
+25 -2

No files matched your search

+23
View File
@@ -22,3 +22,26 @@ cargo run -p ferese -- foot
```
Set `RUST_LOG=ferese=debug` for detailed compositor logging.
### Direct DRM session
Run the hardware backend from a spare TTY, outside another graphical session:
```bash
RUST_LOG=ferese=debug cargo run -p ferese -- --backend=drm -- foot
```
Do not run that command from a terminal inside the active desktop: the direct
backend requests control of the seat and primary DRM device. Use
Ctrl+Alt+F1–F12 to switch virtual terminals.
M4 validation requires the direct session to:
- start `foot` and render the same animated tiling workload as the nested path;
- retain keyboard and pointer input;
- pause when switching away and redraw after switching back; and
- log page-flip timing and any missed presentation deadlines on the reference
integrated GPU.
The direct path currently targets one connected output. Multi-output hotplug is
part of M5.
+2 -2
View File
@@ -49,7 +49,7 @@ fn spawn_client(mut args: Vec<std::ffi::OsString>) {
let program = args.remove(0);
match Command::new(&program).args(args).spawn() {
Ok(child) => info!(program = ?program, pid = child.id(), "spawned nested client"),
Err(error) => warn!(program = ?program, %error, "failed to spawn nested client"),
Ok(child) => info!(program = ?program, pid = child.id(), "spawned Wayland client"),
Err(error) => warn!(program = ?program, %error, "failed to spawn Wayland client"),
}
}