yusisamerican-tmp98123821 has quit [Remote host closed the connection]
soxrok2212 has quit []
Daanct12 has quit [Quit: WeeChat 4.3.5]
Daanct12 has joined #panfrost
soxrok2212 has joined #panfrost
___ has joined #panfrost
___ has quit []
yusisamerican-tmp98123821 has joined #panfrost
rasterman has joined #panfrost
sally has quit [Ping timeout: 480 seconds]
sally has joined #panfrost
simon-perretta-img_ has quit []
simon-perretta-img has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
Daanct12 has quit [Quit: WeeChat 4.3.5]
rellla_ has quit []
rellla has joined #panfrost
soxrok2212 has quit []
soxrok2212 has joined #panfrost
<tortoise>
I saw this in the Mesa 24.1.0 release notes. "panvk: Kill panvk_{Create,Destroy}SamplerYcbcrConversion()"
<tortoise>
What does this note mean exactly by Kill? I'm trying to learn a bit about how a driver implements vulkan extensions and I'm still quite new and lost.
<tortoise>
Is the hardware capable of doing this but for now Mesa is killing the effort to support it in the driver for now?
<robmur01>
tortoise: AFAICS from that commit, it just removed some dummy function implementations which did nothing, where the common code was already capable of doing nothing by default
<robmur01>
(or maybe the default implementation does even more than nothing, I'm not familiar with the details)
<tortoise>
I read a blog post that stats "The act of converting YUV to RGB is very simple as it’s just a color space transform with a 3×3 matrix, but YUV means many things. " Which leads me to believe that pretty much any GPU would be able to support SamplerYcbcrConversion extension if implemented in the vulkan driver? Is that basically correct?
<yusisamerican-tmp98123821>
Uhhh theres a lot of other things around the whole driver that need to be plumbed for YCBCR IIRC
<yusisamerican-tmp98123821>
tortoise: If there is no hardware support, you need to plumb the sampler, and I think (?) requires multiple sampler planes for VK_CONVERSION_SEPARATE_RECONSTRUCTION_FILTER_BIT.