1. 11 Feb, 2014 1 commit
  2. 17 Jan, 2014 1 commit
    • Jose Fonseca's avatar
      s/Tungsten Graphics/VMware/ · 87712850
      Jose Fonseca authored
      Tungsten Graphics Inc. was acquired by VMware Inc. in 2008.  Leaving the
      old copyright name is creating unnecessary confusion, hence this change.
      This was the sed script I used:
          $ cat tg2vmw.sed
          # Run as:
          #   git reset --hard HEAD && find include scons src -type f -not -name 'sed*' -print0 | xargs -0 sed -i -f tg2vmw.sed
          # Rename copyrights
          s/Tungsten Gra\(ph\|hp\)ics,\? [iI]nc\.\?\(, Cedar Park\)\?\(, Austin\)\?\(, \(Texas\|TX\)\)\?\.\?/VMware, Inc./g
          /Copyright/s/Tungsten Graphics\(,\? [iI]nc\.\)\?\(, Cedar Park\)\?\(, Austin\)\?\(, \(Texas\|TX\)\)\?\.\?/VMware, Inc./
          # Rename emails
          # Remove dead links
          s@Tungsten Graphics (http://www.tungstengraphics.com)@Tungsten Graphics@g
          # C string src/gallium/state_trackers/vega/api_misc.c
          s/"Tungsten Graphics, Inc"/"VMware, Inc"/
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
  3. 03 Dec, 2013 1 commit
  4. 11 May, 2013 1 commit
  5. 24 Apr, 2013 1 commit
  6. 18 Apr, 2013 1 commit
    • Christoph Bumiller's avatar
      st/mesa: optionally apply texture swizzle to border color v2 · 729abfd0
      Christoph Bumiller authored
      This is the only sane solution for nv50 and nvc0 (really, trust me),
      but since on other hardware the border colour is tightly coupled with
      texture state they'd have to undo the swizzle, so I've added a cap.
      The dependency of update_sampler on the texture updates was
      introduced to avoid doing the apply_depthmode to the swizzle twice.
      v2: Moved swizzling helper to u_format.c, extended the CAP to
      provide more accurate information.
  7. 23 Mar, 2013 1 commit
  8. 20 Mar, 2013 1 commit
    • Christoph Bumiller's avatar
      gallium: add TGSI_SEMANTIC_TEXCOORD,PCOORD v3 · 8acaf862
      Christoph Bumiller authored
      This makes it possible to identify gl_TexCoord and gl_PointCoord
      for drivers where sprite coordinate replacement is restricted.
      The new PIPE_CAP_TGSI_TEXCOORD decides whether these varyings
      should be hidden behind the GENERIC semantic or not.
      With this patch only nvc0 and nv30 will request that they be used.
      v2: introduce a CAP so other drivers don't have to bother with
      the new semantic
      v3: adapt to introduction gl_varying_slot enum
  9. 15 Mar, 2013 1 commit
  10. 18 Feb, 2013 1 commit
  11. 06 Feb, 2013 1 commit
  12. 15 Jan, 2013 1 commit
  13. 20 Dec, 2012 1 commit
  14. 12 Dec, 2012 2 commits
  15. 30 Oct, 2012 1 commit
    • Marek Olšák's avatar
      gallium: add start_slot parameter to set_vertex_buffers · e73bf3b8
      Marek Olšák authored
      This allows updating only a subrange of buffer bindings.
      set_vertex_buffers(pipe, start_slot, count, NULL) unbinds buffers in that
      range. Binding NULL resources unbinds buffers too (both buffer and user_buffer
      must be NULL).
      The meta ops are adapted to only save, change, and restore the single slot
      they use. The cso_context can save and restore only one vertex buffer slot.
      The clients can query which one it is using cso_get_aux_vertex_buffer_slot.
      It's currently set to 0. (the Draw module breaks if it's set to non-zero)
      It should decrease the CPU overhead when using a lot of meta ops, but
      the drivers must be able to treat each vertex buffer slot as a separate
      state (only r600g does so at the moment).
      I can imagine this also being useful for optimizing some OpenGL use cases.
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
  16. 23 Aug, 2012 1 commit
  17. 16 Aug, 2012 2 commits
    • Brian Paul's avatar
      st/mesa: combine vertex/fragment sampler state in arrays · 6c8a1321
      Brian Paul authored
      As with other recent changes, put the vertex and fragment sampler state
      into arrays indexed by the shader type.  This will let us easily add
      support for other types of shaders in the future.
    • Brian Paul's avatar
      gallium: remove PIPE_MAX_VERTEX/GEOMETRY_SAMPLERS #define · cab2fed1
      Brian Paul authored
      were all defined to the same value (16).
      In various places we're creating arrays such as
      sampler_views[PIPE_SHADER_TYPES][PIPE_MAX_SAMPLERS] so we were assuming
      the same number of max samplers for all shader stages anyway.
      Of course, drivers are still free to advertise different numbers of max
      samplers for different shaders.
  18. 06 Aug, 2012 1 commit
  19. 26 Jul, 2012 1 commit
  20. 23 Jul, 2012 1 commit
  21. 12 Jul, 2012 1 commit
  22. 15 Jun, 2012 1 commit
  23. 17 May, 2012 1 commit
  24. 08 May, 2012 1 commit
    • Marek Olšák's avatar
      mesa: add gl_context::NewDriverState and use it for vertex arrays · c5e473fb
      Marek Olšák authored
      The vbo module recomputes its states if _NEW_ARRAY is set, so it shouldn't use
      the same flag to notify the driver. Since we've run out of bits in NewState
      and NewState is for core Mesa anyway, we need to find another way.
      This patch is the first to start decoupling the state flags meant only
      for core Mesa and those only for drivers.
      The idea is to have two flag sets:
      - gl_context::NewState - used by core Mesa only
      - gl_context::NewDriverState - used by drivers only (the flags are defined
                                     by the driver and opaque to core Mesa)
      It makes perfect sense to use NewState|=_NEW_ARRAY to notify the vbo module
      that the user changed vertex arrays, and the vbo module in turn sets
      a driver-specific flag to notify the driver that it should update its vertex
      array bindings.
      The driver decides which bits of NewDriverState should be set and stores them
      in gl_context::DriverFlags. Then, Core Mesa can do this:
      ctx->NewDriverState |= ctx->DriverFlags.NewArray;
      This patch implements this behavior and adapts st/mesa.
      DriverFlags.NewArray is set to ST_NEW_VERTEX_ARRAYS.
      Core Mesa only sets NewDriverState. It's the driver's responsibility to read
      it whenever it wants and reset it to 0.
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
  25. 29 Apr, 2012 4 commits
  26. 23 Apr, 2012 1 commit
    • Marek Olšák's avatar
      gallium: make user vertex buffers optional · e0773da1
      Marek Olšák authored
      This couldn't be split because it would break bisecting.
      * r300g,r600g: stop using u_vbuf
      * r300g,r600g: also report that the FIXED vertex type is unsupported
      * u_vbuf: refactor for use in the state tracker
      * cso: wire up u_vbuf with cso_context
      * st/mesa: conditionally install u_vbuf
  27. 19 Apr, 2012 1 commit
  28. 18 Apr, 2012 4 commits
  29. 25 Jan, 2012 1 commit
    • Marek Olšák's avatar
      st/mesa: do vertex and fragment color clamping in shaders · bc1c8369
      Marek Olšák authored
      For ARB_color_buffer_float. Most hardware can't do it and st/mesa is
      the perfect place for a fallback.
      The exceptions are:
      - r500 (vertex clamp only)
      - nv50 (both)
      - nvc0 (both)
      - softpipe (both)
      We also have to take into account that r300 can do CLAMPED vertex colors only,
      while r600 can do UNCLAMPED vertex colors only. The difference can be expressed
      with the two new CAPs.
  30. 09 Jan, 2012 1 commit
    • Marek Olšák's avatar
      Squash-merge branch 'gallium-clip-state' · dc4c821f
      Marek Olšák authored
      commit d919791f
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Fri Jan 6 17:59:22 2012 +0100
          d3d1x: adapt to new clip state
      commit cfec82bc
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Fri Jan 6 14:16:51 2012 +0100
          gallium/docs: update for clip state changes
      commit c02bfeb8
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Fri Jan 6 14:21:43 2012 +0100
      commit d4e0a785
      Author: Brian Paul <brianp@vmware.com>
      Date:   Thu Jan 5 08:30:00 2012 -0700
          tgsi: consolidate TGSI string arrays in new tgsi_strings.h
          There was some duplication between the tgsi_dump.c and tgsi_text.c
          files.  Also use some static assertions to help catch errors when
          adding new TGSI values.
          v2: put strings in tgsi_strings.c file instead of the .h file.
      Reviewed-by: default avatarDave Airlie <airlied@redhat.com>
      commit c28584ce
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Fri Jan 6 12:48:09 2012 +0100
          gallium: extend user_clip_plane_enable to apply to clip distances
      commit f1d5016c
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Fri Jan 6 02:39:09 2012 +0100
          nvfx: adapt to new clip state
      commit 6f6fa1c2
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Fri Jan 6 01:41:39 2012 +0100
          st/mesa: fix DrawPixels with GL_DEPTH_CLAMP
      commit c86ad730
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Tue Jan 3 23:51:30 2012 +0100
          nv50: adapt to new clip state
      commit 3a8ae6ac
      Author: Christoph Bumiller <e0425955@student.tuwien.ac.at>
      Date:   Tue Jan 3 23:32:36 2012 +0100
          nvc0: adapt to new clip state
      commit 6243a824
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Thu Dec 29 01:32:51 2011 +0100
          draw: initalize pt.user.planes in draw_init
          This fixes a crash in glean/fpexceptions.
      commit e3056524
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Mon Dec 26 06:26:55 2011 +0100
          svga: adapt to new clip state
      commit c5bfa8b3
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 14:11:51 2011 +0100
          r600g: adapt to new clip state
      commit f1189090
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 14:10:26 2011 +0100
          r300g: adapt to new clip state
      commit e3746532
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 12:39:16 2011 +0100
          draw: adapt to new clip state
          This adds a regression in the LLVM clipping path. Can anybody see anything
          wrong with the code? It works for every other case, just glean/fpexceptions
          crashes when doing the "Infinite clip plane test".
      commit b474d2b1
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 13:14:59 2011 +0100
          u_blitter: don't save/set/restore clip state
      commit 9dd240ea
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 13:11:56 2011 +0100
          gallium: don't cso_save/set/restore clip state
          The enable bits are in the rasterizer state.
      commit a4f70311
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 12:58:55 2011 +0100
          gallium: default depth_clip to 1
          depth_clip = !depth_clamp
      commit fe21147a
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Mon Dec 26 06:14:19 2011 +0100
          trace,util: update state logging to new clip state
          Also dump the other missing flags.
      commit 2a3b96e8
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sun Dec 25 10:43:43 2011 +0100
          st/mesa: adapt to new clip state
      commit b7b656a4
      Author: Marek Olšák <maraeo@gmail.com>
      Date:   Sat Dec 17 15:45:19 2011 +0100
          gallium: move state enable bits from clip_state to rasterizer_state
  31. 19 Oct, 2011 1 commit
  32. 29 Jun, 2011 1 commit
    • Thomas Hellstrom's avatar
      st-api: Rework how drawables are invalidated v3. · ac8fdbc1
      Thomas Hellstrom authored
      The api and the state tracker manager code as well as the state tracker code
      assumed that only a single context could be bound to a drawable. That is not
      a valid assumption, since multiple contexts can bind to the same drawable.
      Fix this by making it the state tracker's responsibility to update all
      contexts binding to a drawable
      Note that the state trackers themselves don't use atomic stamps on
      frame-buffers. Multiple context rendering to the same drawable should
      be protected by the application.
      Signed-off-by: default avatarThomas Hellstrom <thellstrom@vmware.com>