On Wed 12 Jul 2017, Jason Ekstrand wrote:
> On Wed, Jul 12, 2017 at 11:05 AM, Chad Versace <[1]chadvers...@chromium.org>
> wrote:
>
> On Thu 29 Jun 2017, Jason Ekstrand wrote:
> Why require that aux_offset > 0? Why reject images where the aux surface
> precedes the primary surface? T
On Wed, Jul 12, 2017 at 11:05 AM, Chad Versace
wrote:
> On Thu 29 Jun 2017, Jason Ekstrand wrote:
> > From: Ben Widawsky
> >
> > This code will disable actually creating these buffers for the scanout,
> > but it puts the allocation in place.
> >
> > Primarily this patch is split out for review,
On Thu 29 Jun 2017, Jason Ekstrand wrote:
> From: Ben Widawsky
>
> This code will disable actually creating these buffers for the scanout,
> but it puts the allocation in place.
>
> Primarily this patch is split out for review, it can be squashed in
> later if preferred.
>
> v2:
> assert(mt->offse
From: Ben Widawsky
This code will disable actually creating these buffers for the scanout,
but it puts the allocation in place.
Primarily this patch is split out for review, it can be squashed in
later if preferred.
v2:
assert(mt->offset == 0) in ccs creation (as requested by Topi)
Remove bogus
