On Tue 06 Jun 2017, Jason Ekstrand wrote: > On Tue, Jun 6, 2017 at 1:32 PM, Jason Ekstrand <ja...@jlekstrand.net> wrote: > > > On Tue, Jun 6, 2017 at 1:22 PM, Chad Versace <chadvers...@chromium.org> > > wrote: > > > >> On Fri 26 May 2017, Jason Ekstrand wrote:
> > How about a section after the auxiliary compression ops section which goes > > into detail on each of the compression types and discusses which states are > > valid etc. > > > > How does this look: > > https://cgit.freedesktop.org/~jekstrand/mesa/commit/?h=wip/i965-resolve-rework-v3&id=8478b102c99e3ec43ec687b3f4e52acb9acbd5ba > > I'll squash it in if you like it. Please squash that in, with fixes :) I don't believe the pass-through state is impossible with MCS, because there is no single surface for write to "pass through" to. The aux surface can never be ignored with MCS. Another bit of evidence for this is that there exists no MCS ambiguate op, and therefore no arrow can exist in the diagram that carries the "resolved" box to the pass-through" box. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
