1. 06 Jun, 2020 1 commit
  2. 15 Apr, 2020 1 commit
  3. 28 Feb, 2020 2 commits
  4. 24 Feb, 2020 1 commit
  5. 21 Feb, 2020 1 commit
  6. 19 Feb, 2020 1 commit
  7. 25 Jan, 2020 1 commit
  8. 23 Dec, 2019 1 commit
    • Roman Stratiienko's avatar
      Android: Fix build issue without LLVM · c411d489
      Roman Stratiienko authored
      Some of the latest changes are causing the following build error on Android:
      
      ```
      external/mesa3d/src/gallium/auxiliary/nir/nir_to_tgsi_info.c:403:6:
      error: redefinition of 'nir_tgsi_scan_shader'
      void nir_tgsi_scan_shader(const struct nir_shader *nir,
           ^
      external/mesa3d/src/gallium/auxiliary/nir/nir_to_tgsi_info.h:37:20:
      note: previous definition is here
      static inline void nir_tgsi_scan_shader(const struct nir_shader *nir,
                         ^
      ```
      
      Include nir_to_tgsi_info.c and nir_to_tgsi_info.h into the build
      only if LLVM is enabled.
      Signed-off-by: default avatarRoman Stratiienko <roman.stratiienko@globallogic.com>
      Reviewed-by: Tapani Pälli's avatarTapani Pälli <tapani.palli@intel.com>
      Tested-by: Marge Bot <!2978>
      Part-of: <!2978>
      c411d489
  9. 14 Dec, 2019 1 commit
  10. 02 Dec, 2019 1 commit
    • Alejandro Piñeiro's avatar
      mesa/main/util: moving gallium u_mm to util, remove main/mm · b6fd679a
      Alejandro Piñeiro authored
      Right now there are two copies of mm:
         * mesa/main/mm.[ch]
         * gallium/auxiliary/util/u_mm.[ch]
      
      At some point they splitted, and from the commit message it was not
      clear why it was not possible to have only one copy at a common place.
      
      Taking into account that was several years ago, Im assuming that it
      was not possible then.
      
      This change would allow to have one copy of the same code, and also
      being able to use that code out of mesa/main or gallium, if needed.
      
      This commit moves u_mm and removes mm, as u_mm has slightly more
      changes.
      Reviewed-by: Jose Fonseca's avatarJose Fonseca <jfonseca@vmware.com>
      b6fd679a
  11. 28 Nov, 2019 4 commits
  12. 14 Nov, 2019 1 commit
  13. 04 Sep, 2019 1 commit
  14. 17 Jun, 2019 1 commit
  15. 24 Apr, 2019 1 commit
  16. 23 Apr, 2019 4 commits
  17. 15 Feb, 2019 2 commits
  18. 20 Dec, 2018 1 commit
    • Roland Scheidegger's avatar
      gallivm: use llvm jit code for decoding s3tc · 6f408314
      Roland Scheidegger authored
      This is (much) faster than using the util fallback.
      (Note that there's two methods here, one would use a cache, similar to
      the existing code (although the cache was disabled), except the block
      decode is done with jit code, the other directly decodes the required
      pixels. For now don't use the cache (being direct-mapped is suboptimal,
      but it's difficult to come up with something better which doesn't have
      too much overhead.)
      Reviewed-by: Jose Fonseca's avatarJose Fonseca <jfonseca@vmware.com>
      6f408314
  19. 27 Nov, 2018 1 commit
  20. 30 Oct, 2018 5 commits
  21. 07 Sep, 2018 1 commit
    • Dylan Baker's avatar
      move u_math to src/util · 80825abb
      Dylan Baker authored
      Currently we have two sets of functions for bit counts, one in gallium
      and one in core mesa. The ones in core mesa are header only in many
      cases, since they reduce to "#define _mesa_bitcount popcount", but they
      provide a fallback implementation. This is important because 32bit msvc
      doesn't have popcountll, just popcount; so when nir (for example)
      includes the core mesa header it doesn't (and shouldn't) link with core
      mesa. To fix this we'll promote the version out of gallium util, then
      replace the core mesa uses with the util version, since nir (and other
      non-core mesa users) can and do link with mesautils.
      Acked-by: Eric Engestrom's avatarEric Engestrom <eric.engestrom@intel.com>
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      80825abb
  22. 04 Sep, 2018 1 commit
    • Eric Anholt's avatar
      gallium: Add a helper for implementing PIPE_CAP_* default values. · ad782a70
      Eric Anholt authored
      One of the pains of implementing a gallium driver is filling in a million
      pipe caps you don't know about yet when you're just starting out.  One of
      the pains of working on gallium is copy-and-pasting your new PIPE_CAP into
      each driver.  We can fix both of these by having each driver call into the
      default helper from their default case, so that both sides can ignore each
      other until they need to.
      
      v2: fix i915g build, revert swr change to avoid breaking scons build
          (https://travis-ci.org/anholt/mesa/jobs/419739857)
      v3: Rebase on 3 new gallium caps.
      
      Reviewed-by: Marek Olšák <marek.olsak@amd.com> (v1)
      Cc: Bruce Cherniak <bruce.cherniak@intel.com>
      Cc: George Kyriazis <george.kyriazis@intel.com>
      Cc: Kenneth Graunke <kenneth@whitecape.org>
      ad782a70
  23. 01 Jul, 2018 1 commit
  24. 13 Apr, 2018 1 commit
  25. 12 Apr, 2018 1 commit
  26. 15 Dec, 2017 1 commit
    • Rob Clark's avatar
      gallium/util: add u_transfer_helper · e94eb5e6
      Rob Clark authored
      Add a new helper that drivers can use to emulate various things that
      need special handling in particular in transfer_map:
      
       1) z32_s8x24.. gl/gallium treats this as a single buffer with depth
          and stencil interleaved but hardware frequently treats this as
          separate z32 and s8 buffers.  Special pack/unpack handling is
          needed in transfer_map/unmap to pack/unpack the exposed buffer
      
       2) fake RGTC.. GPUs designed with GLES in mind, but which can other-
          wise do GL3, if native RGTC is not supported it can be emulated
          by converting to uncompressed internally, but needs pack/unpack
          in transfer_map/unmap
      
       3) MSAA resolves in the transfer_map() case
      
      v2: add MSAA resolve based on Eric's "gallium: Add helpers for MSAA
          resolves in pipe_transfer_map()/unmap()." patch; avoid wrapping
          pipe_resource, to make it possible for drivers to use both this
          and threaded_context.
      Signed-off-by: Rob Clark's avatarRob Clark <robdclark@gmail.com>
      e94eb5e6
  27. 09 Nov, 2017 2 commits