10:34 <pq> JoshuaAshton, the need for a display quirk database has come up before in various contexts. Recognizing HMDs was patched into the kernel, but that could have been a userspace db - and I think it should, with userspace console. There was another much more recent thing, maybe related to the new KMS color pipeline, but I forgot the details. libdisplay-info was mentioned as a potential host and API for the db.

10:34 <pq> emersion, what's your opinion?

10:37 <pq> btw. I've started writing Weston code to extract colorimetry from EDID, and then move that as new high-level API in libdisplay-info, but protocol discussions have taken much of my time lately.

10:40 <zamundaaa[m]> The other thing was about vrr flicker

10:44 <pq> ah

10:47 <MrCooper> right, things like whether or not the display has VESA Adaptive Sync certification, or how quickly it can ramp the refresh rate without flickering

10:55 <emersion> pq, i wouldn't mind

11:19 <swick[m]> we really need to find a way to influence display standards and certification in the long run

11:25 <mjt> devices requiring quirks will be released anyway. Just like CPUs which needs microcode updates

11:34 <pq> Reminds me of display calibration. I suppose the goal of calibration would be to make a monitor describable with a simple parametric profile that can leverage as much of the hardware capability as possible but ideally none of in-range of that profile would produce unexpected output.

11:36 <pq> Maybe that's a goal of MHC (MCH?) ICC extensions too.

11:37 <pq> particularly a simple *arbitrary* parametric profile, and not a specific standard profile

12:25 <pq> swick[m], did you check that google docs link? It's the broadcast vs. compute HDR presentation.

12:26 <pq> https://lists.w3.org/Archives/Public/public-colorweb/2023Jun/0001.html

12:38 <ofourdan> heya, I would like to release wayland-utils 1.2.0 as there've been several improvements since 1.1.0 since last September, any objection?

12:45 <swick[m]> pq: yes, your comments on !44 as well but I'm still trying to make my mind up

12:45 <pq> I'm sure of nothing either :-)

12:48 <emersion> jadahl: some GNOME person wanted to embed a wlroots compositor in a GTK app, do you remember who?

12:48 <emersion> if so, can you forward them this link? https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4182

14:02 <jadahl> emersion: I might have a clue, will forward just in case

14:03 <emersion> it was for a login screen with a web auth form iirc

14:03 <jadahl> yea, suspected that

14:54 <wlb> weston Merge request !1259 opened by Philipp Zabel (pH5) gl-renderer: remove pbuffer dummy surface https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1259

14:56 <akallabeth[m]> Hey, would need some wayland specific code for a sdl2 program (custom clipboard)

14:56 <akallabeth[m]> Do you have any examples on how to do that?

15:00 <wlb> weston Merge request !1260 opened by Philipp Zabel (pH5) gl-renderer: use dummy renderbuffer structures for damage tracking https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1260

21:39 <daniels> pq: as a pbuffer/FBO enthusiast, do you want to review the patch stack in https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1106 which is split out into (bottom-to-top order) 1260 -> 1106 -> 1259?