On Mon 04 Sep 2017, Tapani Pälli wrote:
>
>
> On 09/04/2017 08:37 AM, Tapani Pälli wrote:
> >
> >
> > On 09/02/2017 11:17 AM, Chad Versace wrote:
> > > NOT FOR UPSTREAM.
> > >
> > > To get the driver's build-id, anv_physical_device_init_uuids() searches
> > > the current process for an ELF phdr for filename "libvulkan_intel.so".
> > > However, Android requires that the library be named
> > > "vulkan.${board}.so".
> >
> > I don't think this requirement exists, we are using libvulkan_intel.so
> > on Android IA and running Vulkan aps. It's up to the HAL implementation
> > to choose what library it opens.
>
> OK, now reading further I understand why. You are including HAL module
> implementation in the driver itself and that is why the requirement. That is
> quite a big difference between our implementations, do other vendors include
> HAL in the driver?
At least one other vendor's driver embeds the HAL into its Vulkan driver
(a closed-source driver). I did not check any other vendor's source code. But,
considering some discussions I had with a different major unnamed
vendor, I strongly suspect that other vendor also embeds the HAL.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
