On Tue 27 Jun 2017, Jason Ekstrand wrote:
> On Tue, Jun 27, 2017 at 12:19 PM, Chad Versace <[1]chadvers...@chromium.org>
> wrote:
>
> On Mon 26 Jun 2017, Pohjolainen, Topi wrote:
> > On Fri, Jun 16, 2017 at 03:41:34PM -0700, Jason Ekstrand wrote:
> > > From: Ben Widawsky <[2]b...@bwida
On Tue, Jun 27, 2017 at 12:19 PM, Chad Versace
wrote:
> On Mon 26 Jun 2017, Pohjolainen, Topi wrote:
> > On Fri, Jun 16, 2017 at 03:41:34PM -0700, Jason Ekstrand wrote:
> > > From: Ben Widawsky
> > >
> > > Allows us to continue utilizing common miptree creation using
> __DRIimage
> > > without c
On Mon 26 Jun 2017, Pohjolainen, Topi wrote:
> On Fri, Jun 16, 2017 at 03:41:34PM -0700, Jason Ekstrand wrote:
> > From: Ben Widawsky
> >
> > Allows us to continue utilizing common miptree creation using __DRIimage
> > without creating a new DRIimage (for the intel_process_dri2_buffer()
> > case)
On Mon, Jun 26, 2017 at 09:36:34PM +0300, Pohjolainen, Topi wrote:
> On Fri, Jun 16, 2017 at 03:41:34PM -0700, Jason Ekstrand wrote:
> > From: Ben Widawsky
> >
> > Allows us to continue utilizing common miptree creation using __DRIimage
> > without creating a new DRIimage (for the intel_process_d
On Fri, Jun 16, 2017 at 03:41:34PM -0700, Jason Ekstrand wrote:
> From: Ben Widawsky
>
> Allows us to continue utilizing common miptree creation using __DRIimage
> without creating a new DRIimage (for the intel_process_dri2_buffer()
> case).
Just looking this patch locally I don't really underst
From: Ben Widawsky
Allows us to continue utilizing common miptree creation using __DRIimage
without creating a new DRIimage (for the intel_process_dri2_buffer()
case).
This is a bit ugly, but I think it's the best one can do.
v2: This patch let's us remove the temporary no_aux variable since mt
