OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vulkan/wsi: Take max extent into consideration for modifier selection.

Browse Source 
For AMD we kinda have some modifiers with a max size ... (Which is
really a compositor/kms issue, but getting them to try kinda falls
into the unsolved  "how to allocate/what pitch to use" bucket, so
we solve it on the allocating side)

Cc: mesa-stable
Tested-by: Michel Dänzer <mdaenzer@redhat.com>
Reviewed-by: Joshua Ashton <joshua@froggi.es>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18139>
This commit is contained in:
Bas Nieuwenhuizen
2022-08-19 14:17:28 +02:00
committed by Marge Bot
parent eb6ce47d4f
commit bb2a444324
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/vulkan/wsi/wsi_common_drm.c
View File

@@ -400,7 +400,9 @@ wsi_configure_native_image(const struct wsi_swapchain *chain,
result = wsi->GetPhysicalDeviceImageFormatProperties2(wsi->pdevice, result = wsi->GetPhysicalDeviceImageFormatProperties2(wsi->pdevice,
&format_info, &format_info,
&format_props); &format_props);
if (result == VK_SUCCESS) if (result == VK_SUCCESS &&
pCreateInfo->imageExtent.width <= format_props.imageFormatProperties.maxExtent.width &&
pCreateInfo->imageExtent.height <= format_props.imageFormatProperties.maxExtent.height)
info->modifier_props[info->modifier_prop_count++] = info->modifier_props[i]; info->modifier_props[info->modifier_prop_count++] = info->modifier_props[i];
} }