Re: [Mesa-dev] [PATCH v2] anv/cmd_buffer: check for NULL framebuffer

2019-02-11 Thread Juan A. Suarez Romero
On Fri, 2019-02-08 at 15:47 -0600, Jason Ekstrand wrote: > On Fri, Feb 8, 2019 at 7:15 AM Juan A. Suarez Romero > wrote: > > This can happen when we record a VkCmdDraw in a secondary buffer that > > > > was created inheriting from the primary buffer, but with the framebuffer > > > > set to NULL

Re: [Mesa-dev] [PATCH v2] anv/cmd_buffer: check for NULL framebuffer

2019-02-08 Thread Jason Ekstrand
On Fri, Feb 8, 2019 at 7:15 AM Juan A. Suarez Romero wrote: > This can happen when we record a VkCmdDraw in a secondary buffer that > was created inheriting from the primary buffer, but with the framebuffer > set to NULL in the VkCommandBufferInheritanceInfo. > > Vulkan 1.1.81 spec says that "the

[Mesa-dev] [PATCH v2] anv/cmd_buffer: check for NULL framebuffer

2019-02-08 Thread Juan A. Suarez Romero
This can happen when we record a VkCmdDraw in a secondary buffer that was created inheriting from the primary buffer, but with the framebuffer set to NULL in the VkCommandBufferInheritanceInfo. Vulkan 1.1.81 spec says that "the application must ensure (using scissor if neccesary) that all renderin