[Mesa-dev] [PATCH v4] android: add vulkan build for intel

Jason Ekstrand jason at jlekstrand.net
Tue Jan 31 06:38:38 UTC 2017


On Jan 30, 2017 10:03 PM, "Tapani Pälli" <tapani.palli at intel.com> wrote:



On 01/30/2017 04:00 PM, Emil Velikov wrote:

> On 30 January 2017 at 11:37, Tapani Pälli <tapani.palli at intel.com> wrote:
>
>> fixes to issues spotted by Emil Velikov:
>>
>>    - set ANV_TIMESTAMP corretly
>>    - fix typo with VULKAN_GEM_FILES
>>
>> v2: update to use Makefile.sources under vulkan
>>     instead of having own
>>
>> v3: update to changes to generate from vk.xml
>>     (commit c7fc310)
>>
>> v4: remove 'hw' relative path
>>     cleanups, remove unnecessary cruft
>>
>>     review from Emil Velikov:
>>
>>     - move to vulkan folder
>>     - remove timestamp gen, no longer necessary
>>     - more cleanups
>>
>> Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
>
> Does one need the VK_USE_PLATFORM_ANDROID_KHR
> define/VK_KHR_ANDROID_SURFACE_EXTENSION_NAME/winsys implementation or
> the vulkan HAL is enough ?
>

We need some more implementation and probably the define but I wanted to
leave this enabling later as this needs some more investigation. We do
currently pass following tests:

dEQP-VK.wsi.android.surface.create
dEQP-VK.wsi.android.surface.create_custom_allocator
dEQP-VK.wsi.android.surface.query_support
dEQP-VK.wsi.android.surface.query_capabilities
dEQP-VK.wsi.android.surface.query_formats
dEQP-VK.wsi.android.surface.query_present_modes
dEQP-VK.wsi.android.surface.initial_size

but we get 'Duplicate extensions' failure from
dEQP-VK.api.info.instance.extensions and I can see that 'VK_KHR_surface'
and 'VK_KHR_android_surface' are 2 times in the extensions list, I don't
understand why but will try to figure this out.


No idea if this helps but there were some older versions of the loader that
had a bug where they would search some paths twice and accidentally have
duplicate extension names show up.  I'm not sure how android expects those
extensions to be implemented but it could be that both the driver and the
android loader are implementing them.  Just a drive-by thought.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170130/d28ca5fc/attachment.html>


More information about the mesa-dev mailing list