GL framebuffer fetch behavior

[Faith Ekstrand]

NVIDIA is a texelFetch, so (x, 0, 0, 1)
Intel is a TexelFetch pre-SKL.  I'm not sure what it is for SKL+.  Probably
(x, 0, 0, 1) but it's been a while.

~Faith

On Wed, Apr 23, 2025 at 1:11 PM Marek Olšák <maraeo at gmail.com> wrote:

> AMD lowers it to an image load, which follows the rules for image views,
> so (x, 0, 0, 1) for R8_UNORM.
>
> Marek
>
> On Wed, Apr 23, 2025 at 12:25 PM Mike Blumenkrantz <
> michael.blumenkrantz at gmail.com> wrote:
>
>> Hi,
>>
>> An issue recently came up in the GL working group: what is the robustness
>> behavior of framebuffer fetch? For example, if a framebuffer attachment
>> format is R8_UNORM, what are the YZW components which get read back?
>>
>> If people from all the drivers (besides panfrost) which support this
>> extension could reply with the expected behavior on their hardware, that
>> would be helpful.
>>
>>
>> Thanks,
>> Mike
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20250423/7eaada76/attachment.htm>