02:02 <wlb> wayland Issue #375 opened by Cahal Dallett (Doorknob4746) Wayland resolution options for Sony A8H TV https://gitlab.freedesktop.org/wayland/wayland/-/issues/375

05:22 <slattann> test Msg

07:52 <pq> bluebugs, libwayland-client simply has no event loop machinery, so it has not add_idle either.

07:53 <pq> slattann, test ok.

07:53 <pq> bluebugs, sorry, I meant bl4ckb0ne

07:59 <wlb> wayland Issue #375 closed \o/ (Wayland resolution options for Sony A8H TV https://gitlab.freedesktop.org/wayland/wayland/-/issues/375)

09:42 <slattann> @pq: Explicit Synchronization MR: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90

09:42 <slattann> What are the next tasks pending on this get merged ?

09:51 <emersion> get the kernel folks to decide whether they want to throw away drm_syncobj

09:52 <MrCooper> slattann: out of curiosity, why do you want this?

10:00 <pq> slattann, sorry, I try hard to concentrate on color management, so I don't want to spread to that topic for now. Or VRR or...

10:39 <wlb> weston/main: Leandro Ribeiro * tests/color-icc-output: differentiate test name based on ICC profile type https://gitlab.freedesktop.org/wayland/weston/commit/7ea4075d777c tests/color-icc-output-test.c

10:39 <wlb> weston/main: Leandro Ribeiro * tests/color-icc-output: assert that dimension is not zero when creating clut https://gitlab.freedesktop.org/wayland/weston/commit/722d7f8c3f27 tests/color-icc-output-test.c

10:39 <wlb> weston/main: Leandro Ribeiro * tests/color-icc-output: add ICC VCGT tests https://gitlab.freedesktop.org/wayland/weston/commit/8c9dd4febbe1 tests/ reference/output-icc-decorations-03.png reference/output-icc-decorations-04.png reference/output_icc_alpha_blend-03.png reference/output_icc_alpha_blend-04.png reference/shaper_matrix-03.png reference/shaper_matrix-04.png color-icc-output-test.c col

10:40 <wlb> weston Merge request !1226 merged \o/ (Add ICC VCGT tests https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1226)

11:10 <pq> emersion, did you have anything in mind I should comment about of the series https://lore.kernel.org/dri-devel/20230411222931.15127-2-ville.syrjala@linux.intel.com/ ? It seems ok to me, but I wouldn't know if e.g. the row-major layout is correct.

11:11 <emersion> pq, ah, i was hoping you would know that

11:13 <pq> I've never used a KMS CTM before.

11:13 <emersion> i see

11:13 <emersion> JoshuaAshton: have you by any chance? ^

11:13 <pq> I do like the layout documented very very much if it's correct. :-)

11:14 <pq> and would probably be one of the first reviee comments if I was reviewing a patch adding that API now

11:15 <pq> btw. you might like https://github.com/mm2/Little-CMS/issues/377

11:26 <emersion> nice!

12:17 <zamundaaa[m]> pq: I'm using the CTM and the order is correct

12:21 <pq> zamundaaa[m], would you like to send a R-b to that patch?

12:33 <zamundaaa[m]> sure

12:35 <pq> thanks!

13:16 <bl4ckb0ne> pq yeah i understand the reasons behind that choice

13:17 <bl4ckb0ne> but having a way to add idle tasks from the client side could save me some headache

13:17 <pq> bl4ckb0ne, that requires an implementation of an event loop, so.

13:18 <pq> FWIW, weston's clients/window.c has a simple one IIRC. But maybe it would be better to use an actual library.

13:18 <pq> next you want a timer

13:18 <pq> then to watch some other fd

13:21 <bl4ckb0ne> ill take a look at that file, thanks

13:23 <pq> display_run() has the loop, display_defer() is the idle task

13:26 <pq> there is even toytimer_*(), but that is wasting timer fds

13:37 <bl4ckb0ne> the deferred task list might be what i need

13:38 <kennylevinsen> that reminds me of the "unentangle libwayland-server from wl_event_loop" task...

18:50 <any1> libevent, libev, libuv, aml. Why not just pick one? :)

18:55 <kennylevinsen> I'd rather have the compositor (or at least compositor lib) have the freedom to pick...

18:56 <kennylevinsen> it's not like libwayland needs deep event loop integration just to poll a few client sockets

18:57 <emersion> yea

18:57 <emersion> i have a MR but pq doesn't like it too much

18:59 <kennylevinsen> The issue was the complete removal of wl_event_loop, right?

19:01 <kennylevinsen> Maybe we could convince him by starting softer, keeping it but not using it.

19:02 <kennylevinsen> Better than nothing, and I imagine it wouldn't be used by compositors for *too* long after that as there are much nicer options out there. Easier to go for the kill then than while everyone still use it...

19:11 <bl4ckb0ne> i really like that display defer idea

21:27 <JoshuaAshton> emersion, pq: This is what it looks like:

21:28 <JoshuaAshton> https://github.com/ValveSoftware/gamescope/blob/297245cd7ecc8cde53aba06d439825024d002541/src/drm.cpp#L2408

21:28 <JoshuaAshton> (CTM is currently not hooked up in main branch of Gamescope yet, pending me merging some kernel stuff for per-plane CTM for my scRGB stuff)

21:28 <JoshuaAshton> but that from the last proper release should explain it

21:31 <JoshuaAshton> pq: Re. scRGB I was saying to clip to 2020 before doing color mgmt like a typical HDR10 plane.

21:31 <JoshuaAshton> and as for HLG monitors, ngl I really don't care about supporting those, and given my discussions with movie + vfx people, neither does the rest of the industry anymore.

21:32 <JoshuaAshton> and yeah I would use the content primaries in metadata to determine what I do for color mgmt for scRGB content, same as HDR10.