On 4 November 2016 at 11:29, Dave Airlie wrote:
> From: Dave Airlie
>
> The spec doesn't seem to say this is illegal anywhere, it is
> unexpected, but I've got an app doing what appears to be this.
>
> This change splits out setting the base addresses to a separate
> function, if the image has no
Oh, this is definitely against the spec... From section 11.6 of the 1.0.32
spec:
> Non-sparse resources must be bound completely and contiguously to a single
> VkDeviceMemory object before the resource is passed as a parameter to any
> of the following operations:
>
>creating image or buffer
From: Dave Airlie
The spec doesn't seem to say this is illegal anywhere, it is
unexpected, but I've got an app doing what appears to be this.
This change splits out setting the base addresses to a separate
function, if the image has no memory bound we wait until
descriptor update time to bind th
