Hi Marek,

Thanks for the quick review.

I do not think I understand the sharing semantics. We currently have
fast clear for scanout surfaces with the CMASK and eliminate it on
flush resource. I would think we could do that similarly with DCC fast
clear. Both require a flush_resource after modifying the resource
before other applications can use it.

Furthermore, if we disable DCC for image stores, we also need to
communicate that. We could leave DCC enabled for sampling as long as
the DCC buffer stays in decompressed state. But we would need to
communicate that DCC should not be used anymore for rendering.

Do we still want patch 6 and 7 or should I drop them until we have an
actual user?

Yours sincerely,
Bas Nieuwenhuizen
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to