<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#c53">Comment # 53</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 Aditya Swarup from <a href="show_bug.cgi?id=105301#c48">comment #48</a>) > Hi Tapani, > > I don't know the complexity of the task but definitely the spec doesn't say > to restrict external texture creation using dmabuf. This is a policy we are > introducing in our driver and other platforms don't exhibit this behavior. > > If you think what we are doing in the driver is confirming to specs, then > can you or somebody from the MESA team take up this discussion with Google > to resolve this Skqp failure by explaining to them what they are doing in > the test code is wrong. > > The problem over here is we are juggling the ball from one end to the other. > Google says there is no problem in their test code and if the driver is > written according to spec, it should pass. But you/Intel-MESA team have a > different opinion on this. As a result we are going nowhere wrt resolving > this issue :( My suggestion (in internal mail thread) was to use the patch for some time in our product trees and see if there's any smoke coming out in full validation or general usage with apps. This was also meant to unblock you guys, I'm sorry if this approach did not work out.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>