ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
<zmike> ajax: !17149 should be good to go
<zmike> I think once the glxdrawable refcount thing is resolved that should fix > 0 piglit glx tests
lygstate has quit [Remote host closed the connection]
lygstate has joined #zink
lygstate_ has joined #zink
lygstate has quit [Read error: Connection reset by peer]
orbea1 has joined #zink
lygstate_ has quit [Read error: Connection reset by peer]
<zmike> ajax: do you happen to recall the exact mechanics of ST_ATTACHMENT_BACK_LEFT+ST_ATTACHMENT_FRONT_LEFT in the frontend?
<zmike> i.e., how this ultimately gets processed in the driver
<zmike> specifically trying to determine if it's working as a sequential double buffer (i.e., one is rendering and one is presenting and they flip) or if both can be rendering/presenting at the same time
<zmike> cc daniels maybe
<daniels> hard nope
<zmike> yeah that's what I figured
orbea1 has quit []
orbea has joined #zink
Akari has quit [charon.oftc.net helix.oftc.net]
omegatron has quit [charon.oftc.net helix.oftc.net]
xroumegue has quit [charon.oftc.net helix.oftc.net]
Soroush_ has quit [charon.oftc.net helix.oftc.net]
bnieuwenhuizen has quit [charon.oftc.net liquid.oftc.net]
bnieuwenhuizen has joined #zink
Soroush has joined #zink
unevenrhombus[m] has joined #zink
Akari has joined #zink
xroumegue has joined #zink
omegatron has joined #zink
ced117 has joined #zink