<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body bgcolor="white" lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> >> We have a dependency on gralloc in the EGL layer so that is why I don't see it as a problem for Vulkan WSI.<o:p></o:p> <o:p> </o:p> It’s true. In Android O dessert (not released yet), all HALs except for OpeGL and Vulcan need to be wrapped by HIDL and binderized now. While I guess Google wants to avoid this kind of usage and tries to solve it.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Palli, Tapani Sent: Wednesday, March 1, 2017 1:33 PM To: Xu, Randy <randy.xu@intel.com>; Jason Ekstrand <jason@jlekstrand.net> Cc: mesa-dev@lists.freedesktop.org Subject: Re: [Mesa-dev] [PATCH] Vulkan: Add VK_ANDROID_native_buffer to device extension list<o:p></o:p> </div> </div> <o:p> </o:p> <div> On 03/01/2017 07:21 AM, Xu, Randy wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Hi, Tapani<o:p></o:p> <o:p></o:p> According to <a href="https://source.android.com/devices/graphics/implement-vulkan.html" target="_blank">https://source.android.com/devices/graphics/implement-vulkan.html</a> "Window System Integration (WSI) extensions are exported by the loader and primarily implemented in it rather than the driver.". Also, Google provides the stubhal.c in frameworks/native/vulkan/libvulkan, the VK_ANDROID_native_buffer functions are implemented there as a sample.<o:p></o:p> The reason I guess is that VK_ANDROID_native_buffer implementation needs to access Gralloc HAL data structure, but mesa driver should have no dependency to Android HAL, which is required by HAL Binderization.<o:p></o:p> <o:p></o:p> </blockquote> We have a dependency on gralloc in the EGL layer so that is why I don't see it as a problem for Vulkan WSI. I'm OK with having it in HAL but maybe we should still spend some time to figure out a way to expose extension from there (inject string to extensions list in a way or another). Loader wraps extension list and exposes different one to applications than it has from driver, maybe should take some look there how it does all this. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> This patch doesn’t expose VK_ANDROID_native_buffer extension in driver (as the function is not implemented here), but avoid screening it when create device.<o:p></o:p> <o:p></o:p> Thanks,<o:p></o:p> Randy<o:p></o:p> <o:p></o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Palli, Tapani Sent: Wednesday, March 1, 2017 1:03 PM To: Jason Ekstrand <a href="mailto:jason@jlekstrand.net"><jason@jlekstrand.net></a>; Xu, Randy <a href="mailto:randy.xu@intel.com"><randy.xu@intel.com></a> Cc: <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a> Subject: Re: [Mesa-dev] [PATCH] Vulkan: Add VK_ANDROID_native_buffer to device extension list<o:p></o:p> </div> </div> <o:p></o:p> <div> On 03/01/2017 06:17 AM, Jason Ekstrand wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> <div> <div> On Tue, Feb 28, 2017 at 7:52 PM, Randy Xu <<a href="mailto:randy.xu@intel.com" target="_blank">randy.xu@intel.com</a>> wrote:<o:p></o:p> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"> The VK_ANDROID_native_buffer is implemented in Android Vulkan HAL, not driver, but must be claimed in device extension list. Otherwise, this extension will be screened off in framework and driver.<o:p></o:p> </blockquote> <div> <o:p></o:p> </div> <div> This seems rather odd. Can't the Vulkan HAL just hook into vkEnumerateDeviceExtensionProperties and add it to the list there? It seems a bit odd to advertise an extension but not actually provide any of the functionality.<o:p></o:p> </div> </div> </div> </div> </blockquote> This was my question as well. I proposed Randy to include functionality, at the moment it would be along these lines: <a href="https://github.com/android-ia/external-mesa/commit/8b6b2fc4de933c03feba33e5b57c20262e7983cc">https://github.com/android-ia/external-mesa/commit/8b6b2fc4de933c03feba33e5b57c20262e7983cc</a> I don't have a strong preference where functionality exists but it seems like ideally the whole thing would exist in one single component. If the extension list cannot be modified in HAL then this becomes harder to achieve in HAL. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> <div> <div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"> Test: Pass Vulkan dEQP-VK.wsi.android.swapchain.* on Android platform Signed-off-by: Randy Xu <<a href="mailto:randy.xu@intel.com">randy.xu@intel.com</a>> --- <a href="http://Android.common.mk" target="_blank">Android.common.mk</a> | 3 +++ src/intel/vulkan/anv_device.c | 9 +++++++++ 2 files changed, 12 insertions(+) diff --git a/<a href="http://Android.common.mk" target="_blank">Android.common.mk</a> b/<a href="http://Android.common.mk" target="_blank">Android.common.mk</a> index 611162a..f49189b 100644 --- a/<a href="http://Android.common.mk" target="_blank">Android.common.mk</a> +++ b/<a href="http://Android.common.mk" target="_blank">Android.common.mk</a> @@ -116,6 +116,9 @@ else LOCAL_CFLAGS += -DDEFAULT_DRIVER_DIR=\"/system/lib/$(MESA_DRI_MODULE_REL_PATH)\" endif +# Enable VK_ANDROID_native_buffer +LOCAL_CFLAGS += -DVK_USE_PLATFORM_ANDROID_KHR + # uncomment to keep the debug symbols #LOCAL_STRIP_MODULE := false diff --git a/src/intel/vulkan/anv_device.c b/src/intel/vulkan/anv_device.c index 0db96f2..478d753 100644 --- a/src/intel/vulkan/anv_device.c +++ b/src/intel/vulkan/anv_device.c @@ -258,6 +258,15 @@ static const VkExtensionProperties device_extensions[] = { .extensionName = VK_KHR_MAINTENANCE1_EXTENSION_NAME, .specVersion = 1, }, +#ifdef VK_USE_PLATFORM_ANDROID_KHR + { + // Refer <a href="https://source.android.com/devices/graphics/implement-vulkan.html" target="_blank"> https://source.android.com/devices/graphics/implement-vulkan.html</a> + // "Window System Integration (WSI) extensions are exported by the loader + // and primarily implemented in it rather than the driver." + .extensionName = "VK_ANDROID_native_buffer",<o:p></o:p> </blockquote> <div> <o:p></o:p> </div> <div> In the other places, we use the EXTENSION_NAME #define<o:p></o:p> </div> <div> <o:p></o:p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"> + .specVersion = 1, + }, +#endif { .extensionName = VK_KHR_SHADER_DRAW_PARAMETERS_EXTENSION_NAME, .specVersion = 1, -- 2.7.4 _______________________________________________ mesa-dev mailing list <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><o:p></o:p> </blockquote> </div> <o:p></o:p> </div> </div> <o:p></o:p> <pre>_______________________________________________<o:p></o:p></pre> <pre>mesa-dev mailing list<o:p></o:p></pre> <pre><a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><o:p></o:p></pre> <pre><a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><o:p></o:p></pre> </blockquote> <o:p></o:p> </blockquote> <o:p> </o:p> </div> </body> </html>