| 24 Mar 2024 |
 K900 | The WSI plumbs the HDR metadata from the application to gamescope | 08:19:54 |
 @elvishjerricco:matrix.org | There is a FROG layer thing in my /run/opengl-driver | 08:20:02 |
| K900 | And the VK_HDR layer plumbs it from gamescope to kwin | 08:20:07 |
| K900 | Because gamescope stable can't do it by itself yet | 08:20:21 |
| @elvishjerricco:matrix.org | I see. So both is necessary | 08:20:40 |
| @elvishjerricco:matrix.org | Even if you use a bleeding edge gamescope from got? | 08:21:01 |
| @elvishjerricco:matrix.org | * Even if you use a bleeding edge gamescope from git? | 08:21:08 |
| K900 | If you use gamescope from git, it does its own windowing | 08:21:09 |
| K900 | So it can propagate its own metadata | 08:21:23 |
| @elvishjerricco:matrix.org | Got it | 08:21:46 |
| K900 | (gamescope stable uses SDL) | 08:22:02 |
| @elvishjerricco:matrix.org | So where will this stuff be implemented when everything is done right? Mesa? | 08:22:02 |
| K900 | Everywhere | 08:22:11 |
| K900 | That's the fun part | 08:22:13 |
| K900 | It needs to be plumbed through the entire stack | 08:22:23 |
| @elvishjerricco:matrix.org | Oh I just figured a vulkan layer would be all that's truly needed and then applications using the proper vulkan extension would just work | 08:23:05 |
| @elvishjerricco:matrix.org | (I don't actually understand vulkan's architecture and what layers or extensions really are) | 08:23:43 |
| K900 | Extensions are the same thing as in OpenGL, just extra APIs added on top of the core spec | 08:24:00 |
| K900 | Layers are basically LD_PRELOAD | 08:24:08 |
| K900 | But somewhat more controlled | 08:24:16 |
| @elvishjerricco:matrix.org | So why is gamescope needed at all for this? Why isn't it just a game using vulkan apis and then plasma doing all the plumbing | 08:25:27 |
| K900 | It's not going to be necessary | 08:25:56 |
| K900 | In the end | 08:25:57 |
| @elvishjerricco:matrix.org | Why is it necessary right now though? | 08:27:07 |
| K900 | But right now it provides a WSI implementation that can actually use the HDR metadata | 08:27:10 |
| K900 | But the WSI implementation speaks a private protocol to Gamescope itself | 08:27:25 |
| K900 | And then Gamescope itself speaks another private protocol to Kwin | 08:27:34 |
| K900 | Eventually it'll be one stable protocol | 08:27:44 |
| K900 | And the WSI code will just talk directly to whatever compositor | 08:27:58 |
| @elvishjerricco:matrix.org | And what is wsi exactly? Obviously it's some kind of vulkan layer thing but what's it for? | 08:29:15 |
