[Bug 105496] Using a single-plane imageview from a multi-plane image is broken

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Mar 16 17:17:34 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=105496

--- Comment #10 from Lionel Landwerlin <lionel.g.landwerlin at linux.intel.com> ---
(In reply to atomnuker from comment #9)
> (In reply to Lionel Landwerlin from comment #8)
> > 
> > We don't support storage on multiplanar formats indeed.
> > 
> > But R8_UNORM should be reported as supporting storage.
> > 
> 
> The latter (and RGBA) does indeed but since you're attaching the original
> multiplane image to the descriptor (albeit indirectly though a derived
> imageview) its that VkFormat that needs to have STORAGE bit supported. It
> already supports the SAMPLE bit (needed for YUV->RGB converting samplers) so
> I guess its just a matter of flagging STORAGE as well.

It's more or less luck that it works for this particular couple of formats.
For something like G8B8G8R8_422_UNORM the hardware really can't do it.
So I don't think we want to enable storage on anything ycbcr.


Rereading the shader from your repo : 

#version 460

layout (local_size_x = 16, local_size_y = 16) in;
layout (set = 0, binding = 0, rgba8) uniform readonly image2D input_img;
layout (set = 0, binding = 1, rgba8) uniform writeonly image2D output_img;

void main()
{
    vec4 result = imageLoad(input_img, ivec2(gl_GlobalInvocationID.xy));
    imageStore(output_img, ivec2(gl_GlobalInvocationID.xy), result);
}

I'm not sure I understand what is going on here. Is that you're reading from
one texture and writing to the same one?

Regardless of what texture you access, I think what would work is to have a
sampler for the ycbcr texture as input, then you can store to anything that
supports storage.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180316/89f9e94a/attachment.html>


More information about the intel-3d-bugs mailing list