<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [softpipe] piglit fcc-front-buffer-distraction regression"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92946">92946</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[softpipe] piglit fcc-front-buffer-distraction regression
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Keywords</th>
<td>bisected, regression
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Mesa core
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>vlee@freedesktop.org
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>airlied@freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>mesa: 3694d58e6c4a39bd84e8aef0d8e67c3ae9447f33 (maser 11.1.0-devel)
$ ./bin/fcc-front-buffer-distraction -auto
Probe color at (0,0)
Expected: 1.000000 0.000000 0.000000 1.000000
Observed: 1.000000 0.000000 0.000000 0.000000
PIGLIT: {"result": "fail" }
2b676570960277d47477822ffeccc672613f9142 is the first bad commit
commit 2b676570960277d47477822ffeccc672613f9142
Author: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>>
Date: Fri Oct 9 01:38:08 2015 +0100
gallium/swrast: fix front buffer blitting. (v2)
So I've known this was broken before, cogl has a workaround
for it from what I know, but with the gallium based swrast
drivers BlitFramebuffer from back to front or vice-versa
was pretty broken.
The legacy swrast driver tracks when a front buffer is used
and does the get/put images when it is mapped/unmapped,
so this patch attempts to add the same functionality to the
gallium drivers.
It creates a new context interface to denote when a front
buffer is being created, and passes a private pointer to it,
this pointer is then used to decide on map/unmap if the
contents should be updated from the real frontbuffer using
get/put image.
This is primarily to make gtk's gl code work, the only
thing I've tested so far is the glarea test from
<a href="https://github.com/ebassi/glarea-example.git">https://github.com/ebassi/glarea-example.git</a>
v2: bump extension version,
check extension version before calling get image. (Ian)
Bugzilla: <a class="bz_bug_link
bz_status_NEW "
title="NEW - Program with GtkGLArea widget does not redraw"
href="show_bug.cgi?id=91930">https://bugs.freedesktop.org/show_bug.cgi?id=91930</a>
Cc: <<a href="mailto:mesa-stable@lists.freedesktop.org">mesa-stable@lists.freedesktop.org</a>>
Signed-off-by: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>>
:040000 040000 1726a5f7f01d9ae1fc76de431bb24cce16cf69ee
75f18ded95766bac58d0c37c96ffa071a4a32071 M include
:040000 040000 ee333146b90c837460ceab252445e3b38fc528d5
dc0656326c3fb9750fda1f6d3e75aeed99003bc6 M src
bisect run success</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>