is available) from the perspective of
performance or maybe format support (early, or maybe actually all, I
don't know for sure yet, AMD R8xx hardware, for instance, hangs with
linear storage images according to one comment in R800AddrLib, and
that's why a quad with a color target may be preferable for copying —
and it also has fast resolves inside its color buffer hardware, as well
as a DMA engine).
— Triang3l
tch via a different packet sequence on the
existing kernel versions, and later, when the involved command
parsing is
fixed in the kernel, using actual INDIRECT_DISPATCH type-3 packets.
— Triang3l
um2, but also in the Gallium2 interface itself in addition.
• Breaking changes to the meta-specific interface would only require
adjusting meta handling in affected drivers.
Breaking changes to something used by everyone across a vast code
surface… Maybe you, Faith, are already well used to doing them, but
that's still a very special kind of fun 😜
— Triang3l
on hardware with root-signature-based binding.
• Inside a VkCommandPool, separate pooling of entities allocated at
different frequencies: hardware command buffer portions, command
encoders (containing things like the current state that is pretty large
due to fixed binding slots, relocation hash maps), BOs with push
constants and dynamic vertex fetch subroutines.
— Triang3l
Hello Faith and everyfrogy!
I've been developing a new Vulkan driver for Mesa — Terakan, for AMD
TeraScale Evergreen and Northern Islands GPUs — since May of 2023. You can
find it in amd/terascale/vulkan on the Terakan branch of my fork at
Triang3l/mesa. While it currently lacks many o
