11:54 <mps> anyone can tell what is now better to use, mesa 24.3 mainline or mesa-asashi

12:03 <cy8aer> For asahi? mesa-asahi

12:04 <mps> yes, for asahi kernel

12:05 <chadmed> still the asahi fork

12:05 <chadmed> mainline does not have the uapi

12:05 <mps> charmed: thanks

12:06 <mps> I thought so but got this https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/54926#note_459030 for alpine

12:06 <mps> cy8aer: also thanks

12:07 <chadmed> the upstream mesa has all the driver logic etc but the drivers will not build and upstream mesa cannot talk to the kernel driver, so it would not work

12:08 <chadmed> the uapi is ~done aiui so hopefully that will settle down and get merged soonish

12:09 <mps> thanks again

12:10 <j`ey> presumably we'll still have a fork for quicker releases?

12:11 <jannau> the uapi is not done and will be merged with the kernel driver. that's at least several months out

12:14 <j`ey> jannau: 'will be merged with the kernel driver' you mean merged into mesa when the drm/asahi driver is upstream?

12:15 <chadmed> jannau: i meant the mesa patches which implement the uapi

12:15 <chadmed> i know the uapi itself is a kernel thing

12:16 <chadmed> mps: no the uapi itself is part of the kernel driver, but mesa needs to speak it. the patches to implement this are applied to mesa-asahi separately to the driver logic, which gets integrated with upstream regularly

12:17 <chadmed> the reason being that once the uapi is merged into the kernel, thats it. we have to support it forever

12:17 <chadmed> so it has to be damn good and correct first

12:18 <mps> chadmed: yes, I understand this. Just asked to be sure

12:18 <chadmed> oops tagged the wrong person :p

12:18 <chadmed> meant to tag j`ey

12:19 <mps> I knew that you and other will give good answer

12:19 <j`ey> chadmed: Oh, I see

12:19 <jannau> the mesa uapi changes will only be merged in in mesa once the the kernel driver with uapi is on its way to linux mainline

12:20 <j`ey> that's clearer, ty