<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sorry – at the time I was unable to get git send-email working with NVIDIA’s mail server. It’s fine now.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I resent the patch with the subject ‘[PATCH] winsys-framework Default to showing window’ using git send-email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Alex<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ibmirkin@gmail.com [mailto:ibmirkin@gmail.com]
<b>On Behalf Of </b>Ilia Mirkin<br>
<b>Sent:</b> Wednesday, August 12, 2015 8:56 PM<br>
<b>To:</b> James Jones<br>
<b>Cc:</b> Alexander Goins; piglit@lists.freedesktop.org<br>
<b>Subject:</b> Re: [Piglit] Issue with Piglit pixel ownership assumptions<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Unfortunately the patches were attached, which greatly increases the effort required to review. Could you send this out inline using git send-email or equivalent mechanism?<o:p></o:p></p>
<div>
<p class="MsoNormal">On Aug 12, 2015 8:54 PM, "James Jones" <<a href="mailto:jajones@nvidia.com">jajones@nvidia.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">The PIGLIT_NO_WINDOW patch seems like the way to go to me, since defaulting to unreliable behavior seems bad, but allowing users to fall back to it to test on drivers that don't enforce pixel ownership seems fine.  I'd prefer if someone
 outside NVIDIA could review as well, but for:<br>
<br>
0001-winsys-framework-Default-to-showing-window.patch<br>
<br>
Reviewed-by: James Jones <<a href="mailto:jajones@nvidia.com" target="_blank">jajones@nvidia.com</a>><br>
<br>
I'll commit this soon if no one objects.<br>
<br>
Thanks,<br>
-James<br>
<br>
On 07/20/2015 02:44 PM, Alexander Goins wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello all,<br>
<br>
During some recent debugging, I seem to have discovered  an issue with<br>
Piglit that could cause problems with some drivers. With -auto, and<br>
without -fbo or PIGLIT_FORCE_WINDOW=1, Piglit defaults to rendering to<br>
the default framebuffer without mapping a window. This means that it<br>
doesn't take pixel ownership, which could cause a problem with some<br>
drivers, particularly NVIDIA's with Unified Back Buffer enabled. The<br>
OpenGL spec requires that pixel ownership be established in order to<br>
guarantee that the window system doesn't clobber the output. There are<br>
more details in the patch descriptions.<br>
<br>
It would probably be best to deprecate the functionality of not showing<br>
a window altogether, making users use FBOs if they want offscreen<br>
rendering. I made a patch that simply removes that functionality. As a<br>
softer solution, however, I also made a patch that makes displaying the<br>
window the default, and replaced PIGLIT_FORCE_WINDOW with<br>
PIGLIT_NO_WINDOW, a flag that allows tests to run without mapping a<br>
window. This way, users that have been relying on the existing<br>
functionality can continue using it.<br>
<br>
Both patches are included.<br>
<br>
Thanks,<br>
<br>
Alex<o:p></o:p></p>
<p class="MsoNormal">_______________________________________________<br>
Piglit mailing list<br>
<a href="mailto:Piglit@lists.freedesktop.org" target="_blank">Piglit@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/piglit" target="_blank">http://lists.freedesktop.org/mailman/listinfo/piglit</a><o:p></o:p></p>
</div>
</div>
</body>
</html>