<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 - Drivers, Gallium/legacy swrast glDrawPixels differences"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89624">89624</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Drivers, Gallium/legacy swrast glDrawPixels differences
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Other
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>daniel.sebald@ieee.org
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>In the following two bug reports:
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Drivers/DRI/swrast"
href="show_bug.cgi?id=89586">https://bugs.freedesktop.org/show_bug.cgi?id=89586</a>
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Drivers/Gallium/swrast: Pixel image limited to GL_MAX_TEXTURE_SIZE"
href="show_bug.cgi?id=89622">https://bugs.freedesktop.org/show_bug.cgi?id=89622</a>
I discussed some artifacts concerning pixels at or beyond GL_MAX_TEXTURE_SIZE
in the input image. In the first bug report I attached a patch that fixes the
vertical lines in legacy swrast. In the second I simply noted that Gallium
swrast limits the image, and I think it wouldn't be too difficult to correct
that.
Here I want to point out the subtle difference between legacy swrast (post
patch in <a class="bz_bug_link
bz_status_NEW "
title="NEW - Drivers/DRI/swrast"
href="show_bug.cgi?id=89586">bug #89586</a>) and the Gallium swrast using images with only 20 x 20
input pixels.
For legacy swrast, the attached image
Screenshot-differences_legacy_swrast-annotated.png shows how the scaled image
can extend past the edge of the boundary in the x-dimension, or not (and it
never falls short of the boundary). On the other hand, the image will fall
short of boundary in the y-dimension, or not (and it never extends past). I'm
guessing this behavior has to do with xfactor > 0 and yfactor < 0.
For Gallium swrast, the attached image
Screenshot-differences_gallium-annotated.png illustrates that scaled image
aligns with the x-dimension edge (an it always seems to do so). However, the
image can extend past the bottom in the y-dimension, or not (and it seems to
never fall short).
Since these two behaviors are different, as subtle as it may be, at least one
of them has a bug. I suspect that both of them might have a flaw as far as
precisely following OpenGl standard. It's interesting that the x-dimension for
the Gallium driver seems most consistent.
Granted, the axis box itself may not be exact, so to say exactly what the bug
is at this stage is premature, but at least the behavior of the axis box should
be the same when all that is varied is the graphics driver and not the
application binary.</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>