ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel driver has landed in mainline, userspace driver is part of mesa - Logs at https://oftc.irclog.whitequark.org/lima/
uis_ has joined #lima
uis has quit [Ping timeout: 480 seconds]
dsimic is now known as Guest23412
dsimic has joined #lima
Guest23412 has quit [Ping timeout: 480 seconds]
<enunes> sarbes: cool, did you get that from GLES 1 or from guessing at the hardware description?
<enunes> anarsoul: do you have thoughts on setting the mixed_framebuffer_sizes cap to enable GL_ARB_framebuffer_object (in addition to EXT_framebuffer_object)? I feel like this was already considered before?
<anarsoul> enunes: it's not supported by the hardware
<enunes> perhaps we were too strict if there is some corner case, but lima already implements all the "multiple disjoint extensions into a single ARB extension" listed in https://registry.khronos.org/OpenGL/extensions/ARB/ARB_framebuffer_object.txt
<anarsoul> i.e. color and z buffers cannot have different dimensions
<enunes> it prevents hundreds of piglit tests from running based on saying that glBlitFramebuffer is not supported
<enunes> lima is the only driver which does not set it, vc4 does with the reason to enable those piglit tests
<enunes> and the GL 2.1 support is kind of a lie anyway, so... maybe we don't have to be that strict for that particular case
<anarsoul> it is supported in vc4 though
<anarsoul> we'd have to do 2x draws (if color widthxheight doesn't match z widthxheight) if we want to support it
<anarsoul> i.e. utgard cannot do that:
<anarsoul> - Where appropriate, relax some of the constraints expressed by previous
<anarsoul> implementations the freedom to support more flexible usages where
<anarsoul> FBO-related extensions. In particular the requirement of matching
<anarsoul> possible.
<anarsoul> attachment dimensions and component sizes has been relaxed, to allow
<enunes> oops, thats my local gitlab
<enunes> I meant it more like this, so that we can allow all those piglit tests to run
<anarsoul> well, sure
<enunes> I worked on the srgb stuff and when trying to test it, most tests don't actually run because of this
<enunes> on my run thats around 400 tests
<enunes> not sure how many actually test the multiple sizes part though
<sarbes> It had to be implemented in hardware, or so I thought. And the "hole" in the blend func was pretty telling.
<sarbes> Logicops, that is.
<enunes> sarbes: yeah, nice. so just a hint don't know if you had considered it, but this is also in GLES 1 which is also implemented by the blob driver, GLES 1 is a bit of a forgotten source of info for these older features
<sarbes> Are there more GLES 1 features missing? I'm not very knowledgeable in this area.
<enunes> one time I started this https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7825 , apparently it's been 4 years... probably wont realistically finish that myself any time soon, so if anyone is ever interested I guess it would be free to get :)
<enunes> this one might be more relevant though being useful for more real applications https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16136 , same situation