evadot has quit [Remote host closed the connection]
evadot has joined #dri-devel
YuGiOhJCJ has joined #dri-devel
mszyprow has joined #dri-devel
fab has quit [Quit: fab]
Company has quit [Quit: Leaving]
vliaskov has joined #dri-devel
yuq825 has joined #dri-devel
frieder has joined #dri-devel
fab has joined #dri-devel
jsa has joined #dri-devel
luc has joined #dri-devel
glennk has joined #dri-devel
<luc>
hi, is there any particular reason why "for gallium we only support combined Z+stencil, not separate buffers" in mesa::do_validate_framebuffer?
gnuiyl has quit [Remote host closed the connection]
gnuiyl has joined #dri-devel
deoal^ has quit [Read error: Connection reset by peer]
sghuge has quit [Remote host closed the connection]
coldfeet has joined #dri-devel
sghuge has joined #dri-devel
digetx has joined #dri-devel
warpme has joined #dri-devel
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #dri-devel
kasper93 has joined #dri-devel
Mary4 has joined #dri-devel
alethkit_ has joined #dri-devel
pitust_ has joined #dri-devel
ifreund_ has joined #dri-devel
ella-0_ has joined #dri-devel
kuruczgy_ has joined #dri-devel
nucfreq_ has joined #dri-devel
hummer12007_ has joined #dri-devel
bl4ckb0ne_ has joined #dri-devel
rosefromthedead_ has joined #dri-devel
emersion_ has joined #dri-devel
mainiomano_ has joined #dri-devel
cmarcelo_ has joined #dri-devel
atiltedtree_ has joined #dri-devel
kchibisov_ has joined #dri-devel
sigmaris_ has joined #dri-devel
rpigott_ has joined #dri-devel
bbhtt- has joined #dri-devel
kj2 has quit [Read error: No route to host]
Mary has quit [Read error: Connection reset by peer]
llyyrr has quit [Read error: Connection reset by peer]
vjaquez has quit [Read error: Connection reset by peer]
cmarcelo has quit [Read error: Connection reset by peer]
nucfreq has quit [Write error: connection closed]
bbhtt has quit [Read error: Connection reset by peer]
ella-0 has quit [Read error: Connection reset by peer]
hummer12007 has quit [Read error: No route to host]
vjaquez has joined #dri-devel
mainiomano has quit [Read error: No route to host]
kchibisov has quit [Read error: No route to host]
atiltedtree has quit [Write error: connection closed]
alethkit has quit [Write error: connection closed]
ifreund has quit [Read error: No route to host]
llyyr has joined #dri-devel
kuruczgy has quit [Read error: No route to host]
coldfeet has quit [Remote host closed the connection]
rpigott has quit [Read error: No route to host]
bl4ckb0ne has quit [Ping timeout: 480 seconds]
rosefromthedead has quit [Ping timeout: 480 seconds]
pitust has quit [Ping timeout: 480 seconds]
kj2 has joined #dri-devel
mvlad has joined #dri-devel
emersion has quit [Ping timeout: 480 seconds]
kasper93_ has quit [Ping timeout: 480 seconds]
<MrCooper>
luc: it was a design decision, which simplifies some things; when Gallium was created some 15 years ago, there was already a trend for hardware to support only combined depth/stencil
sigmaris has quit [Ping timeout: 480 seconds]
digetx has quit [Ping timeout: 480 seconds]
digetx has joined #dri-devel
jsa has quit []
jsa has joined #dri-devel
<luc>
MrCooper: does that mean most of modern hardwares do not support separate z/s buffers?
luc has quit [Quit: Page closed]
<MrCooper>
I suspect so, not sure though
<MrCooper>
I have vague recollection Direct3D >= 10 might not support separate depth/stencil buffers at all, again not sure though
luc has joined #dri-devel
<luc>
MrCooper: thanks a lot for your explanation
<dj-death>
maybe someone remember what NIR pass optimizes things like : if (true) { some_code... }
kts has joined #dri-devel
<glehmann>
nir_opt_dead_cf
<dj-death>
glehmann: thanks :)
warpme has quit []
digetx has quit [Ping timeout: 480 seconds]
chamlis has quit [Remote host closed the connection]
chamlis has joined #dri-devel
digetx has joined #dri-devel
rasterman has joined #dri-devel
tango_ is now known as Guest1706
tango_ has joined #dri-devel
Guest1706 has quit [Ping timeout: 480 seconds]
apinheiro has joined #dri-devel
digetx has quit [Read error: Connection reset by peer]
digetx has joined #dri-devel
emersion_ has quit [Remote host closed the connection]
emersion has joined #dri-devel
emersion has left #dri-devel [#dri-devel]
DavidHeidelberg has quit [Remote host closed the connection]
DavidHeidelberg has joined #dri-devel
warpme has joined #dri-devel
Mary4 has quit []
aljazmc has joined #dri-devel
Mary4 has joined #dri-devel
aljazmc has quit []
Mary4 has quit []
Mary4 has joined #dri-devel
Mary4 has quit []
Mary has joined #dri-devel
aljazmc has joined #dri-devel
heat has joined #dri-devel
aljazmc has quit [Remote host closed the connection]
aljazmc has joined #dri-devel
aljazmc has quit []
kts has quit [Quit: Konversation terminated!]
Dark-Show has quit [Quit: Leaving]
gnuiyl has quit [Remote host closed the connection]
gnuiyl has joined #dri-devel
pcercuei has joined #dri-devel
feaneron has quit [Ping timeout: 480 seconds]
coldfeet has joined #dri-devel
azerov has quit []
azerov has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
Vanfanel has joined #dri-devel
jkrzyszt has joined #dri-devel
meltq has joined #dri-devel
<meltq>
could someone point me to documentation about the possible return values for regulator_enable()? is it always 0 if no error, negative on error?
coldfeet has quit [Remote host closed the connection]
nerdopolis has joined #dri-devel
meltq has quit [Ping timeout: 480 seconds]
i-garrison has quit []
i-garrison has joined #dri-devel
jkrzyszt has quit [Ping timeout: 480 seconds]
jkrzyszt has joined #dri-devel
siak has joined #dri-devel
imre has quit [Ping timeout: 480 seconds]
Schrostfutz has joined #dri-devel
<Schrostfutz>
Hi, I'm running into a segfault in rockchip_dri.so. The stacktrace is less than helpful so I want to build a debug version of the mesa present on my system. Where can I find documentation on how to do this?
bmodem has joined #dri-devel
feaneron has joined #dri-devel
ella-0_ has quit [Remote host closed the connection]
rosefromthedead_ has quit [Remote host closed the connection]
atiltedtree_ has quit [Remote host closed the connection]
kchibisov_ has quit [Remote host closed the connection]
pitust_ has quit [Remote host closed the connection]
sumoon has quit [Remote host closed the connection]
kennylevinsen has quit [Remote host closed the connection]
nucfreq_ has quit [Remote host closed the connection]
kuruczgy_ has quit [Remote host closed the connection]
rpigott_ has quit [Remote host closed the connection]
cmarcelo_ has quit [Remote host closed the connection]
mainiomano_ has quit [Write error: connection closed]
ifreund_ has quit [Write error: connection closed]
alethkit_ has quit [Write error: connection closed]
hummer12007_ has quit [Remote host closed the connection]
kennylevinsen has joined #dri-devel
ifreund has joined #dri-devel
rosefromthedead has joined #dri-devel
Schrostfutz has quit [Read error: Connection reset by peer]
atiltedtree has joined #dri-devel
kchibisov has joined #dri-devel
sumoon has joined #dri-devel
mainiomano has joined #dri-devel
rpigott has joined #dri-devel
davispuh has joined #dri-devel
ella-0 has joined #dri-devel
pitust has joined #dri-devel
nucfreq has joined #dri-devel
kuruczgy has joined #dri-devel
kasper93 has quit [Ping timeout: 480 seconds]
hummer12007 has joined #dri-devel
cmarcelo has joined #dri-devel
bolson has joined #dri-devel
yuq825 has left #dri-devel [#dri-devel]
alethkit has joined #dri-devel
Calandracas has quit [Ping timeout: 480 seconds]
Kayden has quit [Quit: Leaving]
Calandracas has joined #dri-devel
Kayden has joined #dri-devel
sravn has joined #dri-devel
<DavidHeidelberg>
eric_engestrom: btw. for the 24.2.1, would you be ok dropping sha512 into docs too? I always find it in the announcement, but in docs is only sha256
<DavidHeidelberg>
eric_engestrom: do I get it right, that the checksum is manually pasted there?
<eric_engestrom>
yes, although in practice I have a script that greps it out of the generated announcement email and seds it into the release note and then commits that, because if I had to actually do it by hand I'd mess it up half the time 😅
<DavidHeidelberg>
eric_engestrom: so "s/SHA256 checksum/SHA checksums/" would do it for you? (as the checksum has different lenghts)
Company has joined #dri-devel
<eric_engestrom>
dcbaker was working on a better release script but I think he never finished it, and I've been too busy/lazy to take over as I already have this locally anyway, but it's not great if we were to onboard a new release manager as I'd need to give them my dozen or so tiny scripts automating the various parts
<eric_engestrom>
DavidHeidelberg: yeah that's fine
<dcbaker>
eric_engestrom: I should really get that rebased and sent out again…
vliaskov has quit [Read error: Connection reset by peer]
dsimic is now known as Guest1732
dsimic has joined #dri-devel
Guest1732 has quit [Ping timeout: 480 seconds]
fab has quit [Quit: fab]
<mareko>
luc: AMD doesn't support separate z/s; even though they are separate in memory, there are certain attributes between them that must be identical
<eric_engestrom>
yeah I don't think the power consumption is any relevant here, but the CI time taken away from someone else would be
epoch101 has joined #dri-devel
<zmike>
we should have a label for marge weekend queue
<zmike>
and then a cron job assigns everything with that label to marge saturday afternoon
<DavidHeidelberg>
zmike: damn. So you want make my weekends waiting longer? :D
<eric_engestrom>
zmike: yeah that's not a bad idea
<DavidHeidelberg>
No, no, it isn't. Weekends is only time, when I can happily merge what the f I want without waiting :D don't ruin it for me.... no seriously, having tag "Merge-when-Marge-is-free" would be cool
<eric_engestrom>
mind creating an issue with that so we don't forget? 🫣
<DavidHeidelberg>
^^^ :)
<eric_engestrom>
thx!
mbrost has quit [Ping timeout: 480 seconds]
<Company>
zmike, MrCooper: so https://gitlab.freedesktop.org/mesa/mesa/-/issues/11784 sounds to me like an issue with sizing when GTK creates the egl_window/egl_surface waaaay before actually creating doing any wl_surface setup?
<MrCooper>
the "first frame doesn't show up" part, yeah possibly
<MrCooper>
GTK needs to set the window size before calling eglMakeCurrent with non-NULL surface
<Company>
we set the "window size"
<Company>
in the sense that there isn't one yet
<Company>
we create the egl_window shortly after calling wl_compositor_create_surface()
<MrCooper>
specifically wl_egl_window::width/height is what matters
<Company>
can GTK manually resize the window?
<MrCooper>
how is the initial window size determined?
<Company>
we just hardcode 1x1 I guess
<Company>
because we don't have any size at that point
<MrCooper>
I mean the size of the first frame
<MrCooper>
it was working fine somehow before the 2 gtk commits I bisected
<Company>
previously we bound to EGL_NO_SURFACE first
<Company>
which meant we didn't need to create the egl_window
<Company>
and then later did a 2nd make_current()
<MrCooper>
still needed to MakeCurrent the actual surface at some point though, and the egl_window size had to be correct at that point
<Company>
yes, but that happened after we negotiated a proper size with the compositor
<MrCooper>
then that seems required
<Company>
and now the code seems to crea the egl_window with 1x1 size and then resizes it to the proper size later
<Company>
this is not an issue on other platforms like X11 because X11 windows always have a size
<Company>
XCreateWindow() needs one while wl_compositor_create_surface() doesn't
<Company>
so that's a thing to make code fall over I guess
<Company>
I think that's a bug in Mesa (or EGL) still, that it's unclear what the initial size of an egl_window() should be or if it's illegal to create one until the first configure
nerdopolis has quit [Ping timeout: 480 seconds]
<Company>
but I can deal with this in GTK I think
<Company>
now that I know what the issue is
<MrCooper>
I don't think it's illegal per se (there's no error), EGL just needs to know the intended window size to choose the back buffer size
<MrCooper>
the EGL Wayland platform does, specifically
<Company>
yeah, but we give it the right one via wl_egl_window_resize() later
<MrCooper>
too late
<MrCooper>
the back buffer is locked in MakeCurrent
<MrCooper>
meaning it can't change until SwapBuffers
mbrost has joined #dri-devel
<Company>
do I need to re-MakeCurrent() after every resize?
<MrCooper>
no, per my comment on the issue
<Company>
or do I even need to SwapBuffers()
<Company>
so this is only for the first frame?
<MrCooper>
you need to wl_egl_window_resize before querying the buffer age or doing the first drawing operation
<Company>
we do that
LeviYun has quit [Ping timeout: 480 seconds]
<MrCooper>
k, then I guess the question is: does Mesa really need to lock the back buffer in MakeCurrent? Not sure offhand
aljazmc has joined #dri-devel
<Company>
create 1x1, makeCurrent, resize 828x629, query buffer age (which returns 0 as it should), render full frame, SwapBuffers()
aljazmc has quit [Remote host closed the connection]
aljazmc has joined #dri-devel
aljazmc has quit [Remote host closed the connection]
aljazmc has joined #dri-devel
kts has joined #dri-devel
<MrCooper>
Company: though I'm afraid you'll have to deal with it for existing Mesa releases anyway
<Company>
yeah
<daniels>
yeah, I don't like those semantics, but those are the semantics we have ...
<daniels>
by the time it came up, it felt like it was too late to change it, since breaking API is ... not great ... and the way you find out that resize semantics have changed from under you is catching a fatal client error
mbrost has quit [Ping timeout: 480 seconds]
<MrCooper>
daniels: specifically, I wonder if the back buffer really needs to be locked already in MakeCurrent
epoch101_ has joined #dri-devel
epoch101 has quit [Ping timeout: 480 seconds]
coldfeet has joined #dri-devel
warpme has quit []
alanc has quit [Remote host closed the connection]
<daniels>
all things being equal, I think it would be better if it weren't
alanc has joined #dri-devel
<daniels>
however, if we make it not be locked in MakeCurrent, then we change visible semantics
<daniels>
and I'm not sure whether or not that's safe at this point
tobiasjakobi has quit [Remote host closed the connection]
jkrzyszt has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
anujp has quit [Ping timeout: 480 seconds]
LeviYun has quit [Ping timeout: 480 seconds]
raki has joined #dri-devel
raki has quit [Remote host closed the connection]
LeviYun has joined #dri-devel
anujp has joined #dri-devel
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit []
<DavidHeidelberg>
Mary: Heya, I ran OpenCL piglit set (I was thinking about adding it as nightly, to keep consistent check how the CL works) and it looks kinda brutal, if you're interested in seeing it https://gitlab.freedesktop.org/dh/mesa/-/jobs/62875796 if you see some low hanging fruit to reduce crashes, I'm happy to run the CI branch against it
epoch101 has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
epoch101_ has quit [Ping timeout: 480 seconds]
feaneron has joined #dri-devel
kaiwenjon has quit [Quit: WeeChat 3.8]
epoch101 has quit []
LeviYun has joined #dri-devel
<daniels>
DavidHeidelberg: heh yeah, midgard is pretty wild-west for CL, but last we saw CSF/bifrost are in better shape
LeviYun has quit [Remote host closed the connection]
<DavidHeidelberg>
daniels: nice to hear, thou T860 is very important, as it's inside the PinePhone Pro :) Let's not talk about the glorious Mali 450 in PinePhone 1 which can do hardly 3D
<daniels>
ahhh yes, sorry, have been sidetracked by other things :\
<DavidHeidelberg>
np I pushed it yesterday, mentioning it since we talkin
LeviYun has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
kaiwenjon has quit [Ping timeout: 480 seconds]
kaiwenjon has joined #dri-devel
alatiera has quit []
LeviYun has joined #dri-devel
alatiera has joined #dri-devel
alatiera is now known as Guest1755
Guest1755 is now known as alatiera
guludo has quit [Ping timeout: 480 seconds]
guludo has joined #dri-devel
luc has quit [Remote host closed the connection]
Schrostfutz has joined #dri-devel
mbrost has joined #dri-devel
mszyprow has quit [Ping timeout: 480 seconds]
mbrost has quit [Ping timeout: 480 seconds]
LeviYun has quit [Ping timeout: 480 seconds]
gouchi has quit [Quit: Quitte]
mvlad has quit [Remote host closed the connection]
Duke`` has quit [Ping timeout: 480 seconds]
<jenatali>
eric_engestrom: You might have opinions on !30877. I'm just looking for someone to give me a thumbs up/down :)
anujp has quit [Ping timeout: 481 seconds]
mszyprow has joined #dri-devel
coldfeet has quit [Remote host closed the connection]
glennk has quit [Ping timeout: 480 seconds]
sassefa has joined #dri-devel
jsa1 has quit [Ping timeout: 480 seconds]
rz has quit [Remote host closed the connection]
rz has joined #dri-devel
LeviYun has joined #dri-devel
<eric_engestrom>
jenatali: ack (although I see you already got two acks), but I'm a bit surprised by the `14.29 -> 14` change; does it mean `14.*`?
<jenatali>
Yeah it does
<eric_engestrom>
ok
<eric_engestrom>
not sure if you want to pin it to the next version instead?
<jenatali>
We were already installing both sets of build tools and we had tried to upgrade a while ago, but ran into NaN issues that I recently diagnosed and fixed unrelated to the version bump
<eric_engestrom>
on the linux side that's what we do, so that a re-gen of the image for another reason doesn't randomly pick a new version of one component
<jenatali>
I guess we could? I'm not entirely sure what the actual version is :)
<jenatali>
I think it's 14.40 currently
<eric_engestrom>
hehe
<eric_engestrom>
I'll leave that as a comment on the MR as well, for posterity
<jenatali>
Yeah, I think I have a slight preference to keep rolling forward and only pin when there's problems
LeviYun has quit [Ping timeout: 480 seconds]
<eric_engestrom>
ack
<eric_engestrom>
I posted my comment, I guess you can reply that there too :P