<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301">bug 105301</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=105301#c46">comment #46</a>) > (In reply to Dongseong Hwang from <a href="show_bug.cgi?id=105301#c45">comment #45</a>) > > 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 :/</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>