- Jun 13, 2011
-
-
Ian Romanick authored
-
Ian Romanick authored
-
Ian Romanick authored
-
Emma Anholt authored
Tested by piglit ati_draw_buffers-arbfp. Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Ian Romanick <ian.d.romanick@intel.com> (cherry picked from commit fb6e3973)
-
Emma Anholt authored
Fixes fbo-drawbuffers-arbfp. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=34321 Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Ian Romanick <ian.d.romanick@intel.com> (cherry picked from commit 28cec9e8)
-
- Jun 12, 2011
-
-
Certain applications (e.g., Bernina My Label, and the Windows implementation of Processing language) destroy the device context used when creating the frame-buffer, causing presents to fail because we were still referring to the old device context internally. This change ensures we always use the same HDC passed to the ICD entry-points when available, or our own HDC when not available (necessary only when flushing on single buffered visuals).
-
The assertion is wrong, now that state tracker can cope with a window with zero width or height.
-
We use a hidden window for pbuffer contexts, but Windows limits window sizes to the desktop size by default. This means that creating a big pbuffer on a small resolution single monitor would truncate the pbuffer size to the desktop. This change overrides the windows maximum size, allow to create windows arbitrarily large.
-
While ensuring the framebuffer area is never zero.
-
When the window is minimized GetClientRect will return zeros. Instead of creating a 1x1 framebuffer, simply preserve the current window size, until the window is restored or maximized again.
-
-
Thanks to Brian Paul for diagnosing the issue.
-
This prevents the error prog: for the -disable-mmx option: may only occur zero or one times! when creating a new context after XCloseDisplay with DRI drivers linked with a shared LLVM 2.8 library.
-
Fixes fdo 36738.
-
Jeremy Huddleston Sequoia authored
When GLX_INDIRECT_RENDERING is defined, some symbols are used in libglapi.a but are not defined. Define them through the help of glapitemp.h. Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> Signed-off-by: Chia-I Wu <olvaffe@gmail.com> (cherry picked from commit 0e8d045b)
-
Marek Olšák authored
(cherry picked from commit a674ef78)
-
Marek Olšák authored
RenderTexture doesn't have to be called in invalidate_rb, I guess. (cherry picked from commit df818d57)
-
Marek Olšák authored
This was probably missed when implementing luminance and luminance alpha render targets. _mesa_get_format_bits checks for both GL_*_BITS and GL_TEXTURE_*_SIZE. This fixes: main/framebuffer.c:892: _mesa_source_buffer_exists: Assertion `....' failed. (cherry picked from commit c0110d54)
-
If the underlying transfer had a stride wider for hw alignment reasons, the mipmap generation would generate badly strided images. this fixes a few problems I found while testing r600g with s3tc Signed-off-by: Dave Airlie <airlied@redhat.com> (cherry picked from commit fdb4373a by Marek) This fixes the DXT1 tests from fbo-generatemipmap-formats on some drivers.
-
The EXT_framebuffer_object spec (and later specs) say: "If a buffer is specified in <mask> and does not exist in both the read and draw framebuffers, the corresponding bit is silently ignored." Check for color, depth, and stencil that the source and destination FBOs have the specified buffers. If the buffer is missing, remove the bit from the blit request mask and continue. Fixes the crash in piglit test 'fbo-missing-attachment-blit from', and fixes 'fbo-missing-attachment-blit es2 from'. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=37739 Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Eric Anholt <eric@anholt.net> NOTE: This is a candidate for the stable branches. (cherry picked from commit bb475866 by Marek)
-
In an ES2 context (or if GL_ARB_ES2_compatibility) is supported, the framebuffer can be complete with some attachments be missing. In this case the _ColorDrawBuffers pointer will be NULL. Fixes the crash in piglit test fbo-missing-attachment-clear. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=37739 Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Eric Anholt <eric@anholt.net> NOTE: This is a candidate for the stable branches. (cherry picked from commit 7f9c17aa by Marek)
-
- Jun 11, 2011
-
-
Marek Olšák authored
This is for 7.10 only. The fix in master looks too complex to be cherry-picked. The assertions fail when generating mipmaps for NPOT textures. This fixes: - fbo-generatemipmap-formats Reviewed-by: Brian Paul <brianp@vmware.com>
-
- Jun 10, 2011
-
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
See https://bugs.freedesktop.org/show_bug.cgi?id=36238 NOTE: This is a candidate for the 7.10 branch.
-
Brian Paul authored
-
Brian Paul authored
See piglit dlist-fdo31590.c test and http://bugs.freedesktop.org/show_bug.cgi?id=31590 In this case we had node->prim_count=1 but node->count==0 because the display list started with glBegin() but had no vertices. The call to glEvalCoord1f() triggered the DO_FALLBACK() path. When replaying the display list, the old condition basically no-op'd the call to vbo_save_playback_vertex_list call(). That led to the invalid operation error being raised in glEnd(). NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit 62811057)
-
Brian Paul authored
See the piglit dlist-fdo31590.c test NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit f1cdce95)
-
Brian Paul authored
Previously, we were errantly drawing some interior edges of clipped polygons and quads. Also, we were introducing extra edges where polygons intersected the view frustum clip planes. The main problem was that we were ignoring the edgeflags encoded in the primitive header's 'flags' field which are set during polygon/quad ->tri decomposition. We need to observe those during clipping. Since we can't modify the existing vert's edgeflag fields, we need to store them in a parallel array. Edge flags also need to be handled differently for view frustum planes vs. user-defined clip planes. In the former case we don't want to draw new clip edges but in the later case we do. This matches NVIDIA's behaviour and it just looks right. Finally, note that the LLVM draw code does not properly set vertex edge flags. It's OK on the regular software path though. (cherry picked from commit f6572017)
-
Brian Paul authored
If we use FBOs to access mipmap levels with glRead/Draw/CopyPixels() we need to be sure to access the correct mipmap level/face/slice. Before, we were just passing zero in quite a few places. This fixes the new piglit fbo-mipmap-copypix test. NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit bf14ab41) Conflicts: src/mesa/state_tracker/st_cb_drawpixels.c
-
Brian Paul authored
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=36651 NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit de1df26b)
-
Brian Paul authored
NOTE: this is a candidate for the 7.10 branch. (cherry picked from commit 35594408)
-
Marek Olšák authored
Fixes piglit: - NV_conditional_render/clear (cherry picked from commit 76056510) Conflicts: src/gallium/drivers/r300/r300_blit.c
-
Marek Olšák authored
From now on, depth test is always enabled in hardware. If depth test is disabled in Gallium, the hardware Z function is set to ALWAYS. If there is no zbuffer set, the colorbuffer0 memory is set as a zbuffer to silence the CS checker. This fixes piglit: - occlusion-query-discard - NV_conditional_render/bitmap - NV_conditional_render/drawpixels - NV_conditional_render/vertex_array (cherry picked from commit f76787b3) Conflicts: src/gallium/drivers/r300/r300_state.c Squashed with cherry-picked b1246cf1.
-
- Jun 09, 2011
-
-
Marek Olšák authored
If the wrap R (3rd) mode is set to CLAMP or CLAMP_TO_BORDER and the texture isn't 3D, r300 always samples the border color regardless of texture coordinates. I HATE THIS HARDWARE. NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit da8b4c07) Conflicts: src/gallium/drivers/r300/r300_state_derived.c
-
- Jun 08, 2011
-
-
Marek Olšák authored
NOTE: This is a candidate for the 7.10 branch. (cherry picked from commit 578d4539) Conflicts: src/gallium/drivers/r300/r300_render.c
-
- Jun 07, 2011
-
-
Jeremy Huddleston Sequoia authored
Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> (cherry picked from commit 6ea70600)
-
Jeremy Huddleston Sequoia authored
Everything should be resolved through glapi. Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> (cherry picked from commit cebdffaa)
-
- Jun 06, 2011
-
-
Jeremy Huddleston Sequoia authored
Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> (cherry picked from commit 22c320aa)
-
Jeremy Huddleston Sequoia authored
Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> (cherry picked from commit e5d241dd)
-