ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
Akari has joined #zink
italove has quit [Quit: Ping timeout (120 seconds)]
italove has joined #zink
pendingchaos_ has joined #zink
pendingchaos has quit [Ping timeout: 480 seconds]
pendingchaos has joined #zink
pendingchaos_ has quit [Ping timeout: 480 seconds]
Akari has quit [Quit: segmentation fault (core dumped)]
<anholt> what do I need to do to get vkCmdDebugMarkerBeginEXT set up in zink?
<zmike> I don't think anything?
<zmike> debug is already hooked up
<anholt> (gdb) p ((zink_screen *)$2)->vk.CmdDebugMarkerBeginEXT
<anholt> $6 = (PFN_vkCmdDebugMarkerBeginEXT) 0x0
<zmike> oh
<zmike> gotta hook up VK_EXT_debug_marker in zink_device_info.py
<zmike> I thought it was part of the other debug ext
<zmike> my b
<zmike> hm
<zmike> it is
<zmike> ah I think maybe vkCmdBeginDebugUtilsLabelEXT ?
<anholt> I was looking for a list of needed exts in zink_extensions.py
<anholt> so this is it
<zmike> yeah device exts are in zink_device_info.py
<zmike> instance in zink_instance.py
<zmike> vkCmdBeginDebugUtilsLabelEXT should work fine though
<anholt> don't suppose there's a nice tool in zink for logging why render passes get split?