1. 15 Feb, 2013 9 commits
  2. 14 Feb, 2013 1 commit
  3. 13 Feb, 2013 5 commits
  4. 12 Feb, 2013 1 commit
  5. 11 Feb, 2013 4 commits
    • Roland Scheidegger's avatar
      texture-integer-glsl130: fix wrong expected G/B values for L/LA/I formats · b81148c6
      Roland Scheidegger authored
      
      
      The tests expects the green and blue values to be the same as the luminance
      (or intensity) value but it should be zero.
      (Mesa used to do the former for readpixels probably due to complex wording
      in earlier gl specs but this was considered an error and subsequently changed
      in ad897fff7730298c21289768d9b1b55f3d166ac5.)
      Tested-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      b81148c6
    • Paul Berry's avatar
      Remove BindBufferRange out-of-range tests. · be4c0df3
      Paul Berry authored
      
      
      In the documentation for BindBufferRange, OpenGL specs from 3.0
      through 4.1 contain this language:
      
          "The error INVALID_VALUE is generated if size is less than or
          equal to zero or if offset + size is greater than the value of
          BUFFER_SIZE."
      
      This text was dropped from OpenGL 4.2, and it does not appear in the
      GLES 3.0 spec.
      
      Presumably the reason for the change is because come clients change
      the size of the buffer after calling BindBufferRange.  Implementations
      shouldn't generate an error at the time of the BindBufferRange call
      just because the old size of the buffer was too small, when the buffer
      is about to be resized.
      
      Since this is a deliberate relaxation of error conditions in order to
      allow clients to work, it seems sensible to allow implementations to
      apply this change even if the GL version is less than 4.2.  This patch
      eliminates the checks that would have required the error condition to
      be flagged.
      
      See associated Mesa patch:
      
          mesa: Don't check (offset + size <= bufObj->Size) in BindBufferRange.
      Reviewed-by: default avatarChad Versace <chad.versace@linux.intel.com>
      
      v2: Replace the removed checks with a comment noting that we're
      explicitly not testing this language.
      be4c0df3
    • Tom Gall's avatar
      rm tests/glean/ttexrect.* · 2ee28e28
      Tom Gall authored and Brian Paul's avatar Brian Paul committed
      
      
      Remove ttexrect.* from glean as the previous patch ports the test
      to piglit.
      
      Remove texRect from all.tests.
      Signed-off-by: default avatarTom Gall <tom.gall@linaro.org>
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      2ee28e28
    • Tom Gall's avatar
      port ttexrect.cpp to piglit from glean · a001c6b1
      Tom Gall authored and Brian Paul's avatar Brian Paul committed
      
      
      This ported test goes into tests/spec/arb_texture_rectangle. It
      tests the ARB_texture_rectangle extension.
      
      Create a 255x127 texture of varying colors and bind it as a
      GL_ARB_texture_recangle target.  Draw that rectangle to the window, and
      check that the texture was drawn correctly.  The common failure to be
      caught with this test is not adjusting the non-normalized coordinates on
      hardware that expects normalized coordinates.
      
      To all.tests, add new texrect_simple_arb_texrect
      
      v2: add PIGLIT_GL_VISUAL_DOUBLE to the window_visual, move various
      setup bits to piglit_init and add forgotten all.tests change.
      v3: use piglit_present_results, and piglit_probe_image_rgb
      v4: use piglit_draw_rect_tex, piglit_ortho_projection and minor
      clean ups.
      Signed-off-by: default avatarTom Gall <tom.gall@linaro.org>
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      a001c6b1
  6. 08 Feb, 2013 5 commits
  7. 07 Feb, 2013 2 commits
  8. 06 Feb, 2013 12 commits
  9. 05 Feb, 2013 1 commit