On Tue, Aug 23, 2016 at 2:17 AM, Emil Velikov
wrote:
> On 23 August 2016 at 02:11, Jason Ekstrand wrote:
> > The only reason we should throw INITIALIZATION_FAILED is if we have found
> > useable intel hardware but have failed to bring it up for some reason.
> > Otherwise, we should just throw IN
On 23 August 2016 at 02:11, Jason Ekstrand wrote:
> The only reason we should throw INITIALIZATION_FAILED is if we have found
> useable intel hardware but have failed to bring it up for some reason.
> Otherwise, we should just throw INCOMPATIBLE_DRIVER which will turn into
> successfully advertisi
This patch is
Reviewed-by: Bas Nieuwenhuizen
Tested-by: Bas Nieuwenhuizen
Thanks.
On Tue, Aug 23, 2016 at 3:11 AM, Jason Ekstrand wrote:
> The only reason we should throw INITIALIZATION_FAILED is if we have found
> useable intel hardware but have failed to bring it up for some reason.
> Other
The only reason we should throw INITIALIZATION_FAILED is if we have found
useable intel hardware but have failed to bring it up for some reason.
Otherwise, we should just throw INCOMPATIBLE_DRIVER which will turn into
successfully advertising 0 physical devices
---
src/intel/vulkan/anv_device.c |