[Bug 105301] The big SKQP bug

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105301

--- Comment #47 from Tapani Pälli <lemody at gmail.com> ---
(In reply to Kenneth Graunke from comment #46)
> (In reply to Dongseong Hwang from comment #45)
> > On the other hands, from implementation side, I think Aditya's change makes
> > sense and this change would be safe because
> > 1. it passes Piglit and deqp
> > 2. it restricts available functionality.
> 
> How does removing a restriction "restrict available functionality"?

I guess what he means is that when using TEXTURE_EXTERNAL_OES handle, there is
less functionality exposed. Of course at that at same time client can still use
the TEXTURE_2D handle with all functionality. So we are not really restricting
any functionality here.

I'm not sure if we have fast clear and compression state stored so that one
could do resolve then switch them off (and never turn on again). If we allow
this then this is something we should probably do in this use case? From client
perspective this will result in un-optimal performance I'm not sure if there
are sensible options here :/

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20181106/c915440b/attachment.html>