ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
hikiko has joined #zink
turol has joined #zink
kusma has joined #zink
hikiko has quit [Ping timeout: 480 seconds]
turol has quit [Ping timeout: 480 seconds]
bnieuwenhuizen_ has quit [reticulum.oftc.net liquid.oftc.net]
FernandoMonteiro[m] has quit [reticulum.oftc.net liquid.oftc.net]
xroumegue has quit [reticulum.oftc.net liquid.oftc.net]
ced117 has quit [reticulum.oftc.net liquid.oftc.net]
Plagman_ has quit [reticulum.oftc.net liquid.oftc.net]
italove6 has quit [reticulum.oftc.net liquid.oftc.net]
ced117 has joined #zink
hikiko has joined #zink
Ristovski has joined #zink
Akari has joined #zink
Plagman_ has joined #zink
xroumegue has joined #zink
bnieuwenhuizen has joined #zink
FernandoMonteiro[m] has joined #zink
JoshuaAshton has joined #zink
pendingchaos has joined #zink
Venemo has joined #zink
italove6 has joined #zink
kusma has quit [charon.oftc.net helix.oftc.net]
turol has joined #zink
italove6 has quit [Read error: Connection reset by peer]
ced117 has quit [Ping timeout: 480 seconds]
turol has quit [Ping timeout: 480 seconds]
Venemo has quit [Ping timeout: 480 seconds]
Thermi_ has quit [Ping timeout: 480 seconds]
Venemo has joined #zink
turol has joined #zink
ced117 has joined #zink
FernandoMonteiro[m] has quit [reticulum.oftc.net liquid.oftc.net]
Akari has quit [reticulum.oftc.net liquid.oftc.net]
bnieuwenhuizen has quit [reticulum.oftc.net liquid.oftc.net]
xroumegue has quit [reticulum.oftc.net liquid.oftc.net]
Plagman_ has quit [reticulum.oftc.net liquid.oftc.net]
Akari has joined #zink
bnieuwenhuizen has joined #zink
FernandoMonteiro[m] has joined #zink
xroumegue has joined #zink
Plagman has joined #zink
Venemo has quit [Killed (charon.oftc.net (Nick collision (new)))]
Venemo has joined #zink
Thermi has joined #zink
<cheako> Perhaps the ppl here would know, I was watching Travis Vroman and he seemed to be saying updates to a UBO from host needed to be followed by a write to descriptor? I don't think that's correct.
<airlied> would think you might need a barrier
<cheako> I'm not sure, access would be controlled by a fence or timeline.
<cheako> I got it he had two ubo and one image. Three descriptors, but he had three buffers so each frame would have it's own. So the write is to point to that present image ubo buffer.
<cheako> Can you write to a descriptor set that's part of a running queue?
<zmike> with EXT_descriptor_indexing and update-after-bind sometimes
Venemo has quit [charon.oftc.net helix.oftc.net]
Plagman has quit [charon.oftc.net helix.oftc.net]
ced117 has quit [charon.oftc.net helix.oftc.net]
turol has quit [charon.oftc.net helix.oftc.net]
bnieuwenhuizen_ has joined #zink
Plagman has joined #zink
bnieuwenhuizen has quit [Ping timeout: 480 seconds]
ced117 has joined #zink
Venemo has joined #zink
turol has joined #zink
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #zink
lygstate has joined #zink
unevenrhombus[m] has joined #zink
lygstate has quit [Remote host closed the connection]
neobrain[m] has joined #zink
lygstate has joined #zink
lygstate_ has joined #zink
lygstate is now known as Guest7672
lygstate_ is now known as lygstate
Guest7672 has quit [Read error: Connection reset by peer]
anholt__ has quit [Remote host closed the connection]
omegatron has joined #zink
<cheako> That led me to this article: https://zeux.io/2020/02/27/writing-an-efficient-vulkan-renderer/ where `It’s the responsibility of the application to manage the descriptor sets to make sure that CPU doesn’t update a descriptor set that’s in use by the GPU, ...`
<cheako> I don't know if that means "write", but that's how I understood things.
hch12907 has joined #zink
JulianGro[m] has joined #zink
eukara has quit []
Soroush has joined #zink
kusma has joined #zink
eukara has joined #zink
omegatron has quit [Quit: What happened? You quit!]