https://bugs.freedesktop.org/show_bug.cgi?id=27628
Summary: glxgears prints bogus swap interval information
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=27628
Michal Schmidt mschm...@redhat.com changed:
What|Removed |Added
Attachment #34997|0 |1
is
https://bugs.freedesktop.org/show_bug.cgi?id=27628
Kristian Høgsberg k...@bitplanet.net changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=27628
--- Comment #3 from Jesse Barnes jbar...@virtuousgeek.org 2010-04-14 09:10:27
PDT ---
On Wed, 14 Apr 2010 17:57:07 +0200
Mario Kleiner mario.klei...@tuebingen.mpg.de wrote:
Hmm. The patch inits mesa's local cached copy of swap_interval to
On Wed, 14 Apr 2010 17:57:07 +0200
Mario Kleiner mario.klei...@tuebingen.mpg.de wrote:
Hmm. The patch inits mesa's local cached copy of swap_interval to
zero. The DRI2CreateDrawable() function inside the xserver's xserver/
hw/xfree86/dri2/dri2.c implementation inits its own copy of
Hmm. The patch inits mesa's local cached copy of swap_interval to
zero. The DRI2CreateDrawable() function inside the xserver's xserver/
hw/xfree86/dri2/dri2.c implementation inits its own copy of
swap_interval to 1, at least in the DRI2 patch series of Jesse and
mine that is supposed be
Arpad Borsos wrote:
Sorry about my last mail which was empty except for the attached patch.
The patch fixes a division by zero crash which is triggered when I run
the cairo test-suite using its gl backend and the gallium softpipe driver.
The test-suite still crashes when I'm using llvmpipe,
It looks like the piglit tests use an image comparison to determine
pass/fail, right?
That may not be too reliable since different drivers will produce
slightly different results.
Is there any way that the rendering can be checked for correctness
without relying on an exact image comparison?
Suppose a ray just barely hits/misses a sphere. Depending on the GPU
arithmetic and whether the outcome is a hit or miss, the resulting
pixel color could be completely different.
A per-pixel error margin won't account for this. But as you
suggested, if you allow a certain number or percent
Brian,
you are right, maybe more freedom should be allowed, but
piglit_probe_pixel_rgb() already uses 0.01 as threshold which should
be enough if the ray directions do not have large FP differences.
As a short term goal with the test vsraytrace was, that it should not
take my GM4500 down.
As a
On Sun, 28 Mar 2010 17:52:16 -0400, RALOVICH, Kristóf
kristof.ralov...@gmail.com wrote:
Eric,
please see the attached patch for piglit. The patch includes 2 new
tests based on the demos I provided for mesa.
Let me know if I can further help!
The main thing I'm concerned about is that you
On Wed, Apr 14, 2010 at 17:49, Eric Anholt e...@anholt.net wrote:
On Sun, 28 Mar 2010 17:52:16 -0400, RALOVICH, Kristóf
kristof.ralov...@gmail.com wrote:
Eric,
please see the attached patch for piglit. The patch includes 2 new
tests based on the demos I provided for mesa.
Let me know if I
12 matches
Mail list logo
