05:43 i509vcb: I'm confused, EGL states the default sync status unsignalled, but piglit allows unsignalled or signalled before a glFinish: https://gitlab.freedesktop.org/mesa/piglit/-/blob/main/tests/egl/spec/egl_khr_fence_sync/egl_khr_fence_sync.c?ref_type=heads#L807-808
05:43 i509vcb: That specific test behavior seems to be in violation of the spec
06:04 HdkR: i509vcb: Oh, I think egl sync objects behave like GL fences. So it's a misunderstanding about how they work.
06:05 HdkR: `When a fence sync object is created, eglCreateSync also inserts a fence command into the command stream of the bound client API's current context (i.e., the context returned by eglGetCurrentContext), and associates it with the newly created sync object.`
06:05 HdkR: If the command stream is empty then it is going to immediately signal.
06:10 HdkR: Reading a bit more of the documentation that seems to be the case. Basically GL fences but tied to egl instead
06:15 i509vcb: Hmm okay, so I guess the semantics I was trying to test are more related to EGL_SYNC_REUSABLE_KHR?
06:19 HdkR: Seems to be the case
06:34 HdkR: One thing about reading the spec of the reusable sync objects is I can't tell if eglSignalSyncKHR inserts the command in to the stream and does the signal once the command stream gets to that point, or if it signals immediately on the client side.
06:39 HdkR: I assume it is server side since it doesn't have client in the name
12:43 xq: heya o/
12:44 xq: can i create several framebuffers per GEM buffer?
13:23 MrCooper: yes
13:24 xq: thanks! this makes things easy for me :)
15:20 mivanchev: Hey, author of static-wine32 here. I wonder if someone from the Mesa team would be interested in merging some stuff from my patch I use to compile the project. I know it's mostly my own problem, but I think Mesa can profit from some stuff, especially the redundant prefixing in anv/anv_hasvk
15:21 mivanchev: there are prefxing stuff also in the intel driver
15:21 mivanchev: generally, in the long run, static linking might be something Mesa wants to support because it's just so convenient
15:25 mivanchev: there are also stuff in the meson files like needlessly specifying 'shared_library' vs just 'library' and also name_suffix : 'so'
17:51 dunnj: hello, I am interested in linux gpu development, is there a guide or tutorial that introduces me on the topic?
18:13 FLHerne: dunnj: If you're interested in userspace drivers, there's some documentation under 'Developer Topics' on https://docs.mesa3d.org/
18:14 dunnj: thanks
18:15 FLHerne: Kernel driver notes here https://www.kernel.org/doc/html/latest/gpu/
18:15 FLHerne: I'm sure I've seen something more introductory on someone's blog, but can't remember whose blog :p
18:17 FLHerne: blogs I can't find it on include https://www.supergoodcode.com/ , https://www.gfxstrand.net/faith/blog/ , https://rosenzweig.io/
19:40 Company: dunnj: if you find anything good, please tell me
19:40 Company: I'm trying to get more familiar with the code and I'd very much like a good overview doc