ANDROID: mesa: import gfxstream

Mega-change to support gfxstream.  We should really figure out a
history preserving method...

Common question: Why do we need to import gfxstream into Mesa, and
not have a transition period where we build parts of Mesa in Soong,
and have gfxstream depend on those built parts.

Answer: That may work right now for Android, but there are other
consumers of gfxstream (b:282968393) that have their own versions
of Mesa and gfxstream respectively.  We would break them if we
deleted version of Mesa in gfxstream immediately.

In addition, GfxstreamEnd2EndTests depends on a certain version
of vk.xml, but upstream Mesa uses a newer version.  But we can't
migrate to the newer version since upstream Vulkan.hpp (the vk.xml
dependent part of the code) hasn't migrated to the newer version.

In addition, this is exactly the upstream merge request here:

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27246

The goal AOSP Mesa is to test these MRs in production-like
environment.

Bug: 327408955
Test: compile
Change-Id: I7baa0474ce2b7b256e687784d5d324ee7cba7e0d

1 files changed, 72 insertions, 0 deletions

diff --git a/src/gfxstream/codegen/vulkan/vulkan-docs-next/scripts/reflow-tests/expect-new-vuid-noreflow-novuid.adoc b/src/gfxstream/codegen/vulkan/vulkan-docs-next/scripts/reflow-tests/expect-new-vuid-noreflow-novuid.adoc
new file mode 100644
index 00000000000..728e36ba1f6
--- /dev/null
+++ b/src/gfxstream/codegen/vulkan/vulkan-docs-next/scripts/reflow-tests/expect-new-vuid-noreflow-novuid.adoc
@@ -0,0 +1,72 @@
+// Copyright 2015-2023 The Khronos Group Inc.
+//
+// SPDX-License-Identifier: CC-BY-4.0
+
+[[clears]]
+= Clear Commands
+
+
+[[clears-outside]]
+== Clearing Images Outside A Render Pass Instance
+
+[open,refpage='vkCmdClearColorImage',desc='Clear regions of a color image',type='protos']
+--
+To clear one or more subranges of a color image, call:
+
+include::{generated}/api/protos/vkCmdClearColorImage.adoc[]
+
+.Valid Usage
+****
+ifdef::VK_VERSION_1_1,VK_KHR_maintenance1[]
+  * [[VUID-vkCmdClearColorImage-image-01993]]
+    The <<resources-image-format-features,format features>> of pname:image must: contain ename:VK_FORMAT_FEATURE_TRANSFER_DST_BIT
+endif::VK_VERSION_1_1,VK_KHR_maintenance1[]
+  * pname:image must: have been created with ename:VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flag
+ifdef::VK_VERSION_1_1,VK_KHR_sampler_ycbcr_conversion[]
+  * [[VUID-vkCmdClearColorImage-image-01545]]
+    pname:image must: not use any of the <<formats-requiring-sampler-ycbcr-conversion, formats that require a sampler {YCbCr} conversion>>
+endif::VK_VERSION_1_1,VK_KHR_sampler_ycbcr_conversion[]
+  * If pname:image is non-sparse then it must: be bound completely and contiguously to a single sname:VkDeviceMemory object
+  * [[VUID-vkCmdClearColorImage-imageLayout-00004]]
+    pname:imageLayout must: specify the layout of the image subresource ranges of pname:image specified in pname:pRanges at the time this command is executed on a sname:VkDevice
+ifndef::VK_KHR_shared_presentable_image[]
+  * [[VUID-vkCmdClearColorImage-imageLayout-00005]]
+    pname:imageLayout must: be ename:VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL or ename:VK_IMAGE_LAYOUT_GENERAL
+endif::VK_KHR_shared_presentable_image[]
+ifdef::VK_KHR_shared_presentable_image[]
+  * pname:imageLayout must: be ename:VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL, ename:VK_IMAGE_LAYOUT_GENERAL, or ename:VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR
+endif::VK_KHR_shared_presentable_image[]
+  * [[VUID-vkCmdClearColorImage-aspectMask-02498]]
+    The slink:VkImageSubresourceRange::pname:aspectMask members of the
+    elements of the pname:pRanges array must: each only include
+    ename:VK_IMAGE_ASPECT_COLOR_BIT
+  * [[VUID-vkCmdClearColorImage-baseMipLevel-01470]]
+    The slink:VkImageSubresourceRange::pname:baseMipLevel members of the
+    elements of the pname:pRanges array must: each be less than the
+    pname:mipLevels specified in slink:VkImageCreateInfo when pname:image
+    was created
+  * For each slink:VkImageSubresourceRange element of pname:pRanges, if the
+    pname:levelCount member is not ename:VK_REMAINING_MIP_LEVELS, then
+    [eq]#pname:baseMipLevel {plus} pname:levelCount# must: be less than or
+    equal to the pname:mipLevels specified in slink:VkImageCreateInfo when
+    pname:image was created
+  * [[VUID-vkCmdClearColorImage-baseArrayLayer-01472]]
+    The slink:VkImageSubresourceRange::pname:baseArrayLayer members of the elements of the pname:pRanges array must: each be less than the pname:arrayLayers specified in slink:VkImageCreateInfo when pname:image was created
+  * [[VUID-vkCmdClearColorImage-pRanges-01693]]
+    For each slink:VkImageSubresourceRange element of pname:pRanges, if the pname:layerCount member is not ename:VK_REMAINING_ARRAY_LAYERS, then
+    [eq]#pname:baseArrayLayer {plus} pname:layerCount# must: be less than or equal to the pname:arrayLayers specified in slink:VkImageCreateInfo when
+    pname:image was created
+  * pname:image must: not have a compressed or depth/stencil format
+  * pname:pColor must: be a valid pointer to a slink:VkClearColorValue union
+ifdef::VK_VERSION_1_1[]
+  * [[VUID-vkCmdClearColorImage-commandBuffer-01805]]
+    If pname:commandBuffer is an unprotected command buffer and <<limits-protectedNoFault, pname:protectedNoFault>> is not supported,
+    pname:image must: not be a protected image
+  * [[VUID-vkCmdClearColorImage-commandBuffer-01806]]
+    If pname:commandBuffer is a protected command buffer and <<limits-protectedNoFault, pname:protectedNoFault>> is not supported,
+    must: not be an unprotected image
+endif::VK_VERSION_1_1[]
+****
+
+include::{generated}/validity/protos/vkCmdClearColorImage.adoc[]
+--