1. 09 Mar, 2018 1 commit
  2. 20 Jan, 2018 1 commit
  3. 08 Nov, 2017 1 commit
  4. 16 Oct, 2017 1 commit
  5. 15 Sep, 2017 1 commit
  6. 01 Aug, 2017 1 commit
  7. 12 Jul, 2017 2 commits
  8. 06 Jul, 2017 1 commit
  9. 30 Jun, 2017 1 commit
  10. 15 Jun, 2017 1 commit
    • Eric Anholt's avatar
      gallium: Add renderonly-based support for pl111+vc4. · 7029ec05
      Eric Anholt authored
      This follows the model of imx (display) and etnaviv (render): pl111 is a
      display-only device, so when asked to do GL for it, we see if we have a
      vc4 renderer, make the vc4 screen, and have vc4 call back to pl111 to do
      scanout allocations.
      The difference from etnaviv is that we share the same BO between vc4 and
      pl111, rather than having a vc4 bo and a pl11 bo and copies between the
      two.  The only mismatch between their requirements is that vc4 requires
      4-pixel (at 32bpp) stride alignment, while pl111 requires that stride
      match width.  The kernel will reject any modesets to an incorrect stride,
      so the 3D driver doesn't need to worry about that.
      v2: Rebase on Android rework, drop unused include.
      v3: Fix another Android bug, from Rob Herring's build-testing.
      Reviewed-by: Christian Gmeiner's avatarChristian Gmeiner <christian.gmeiner@gmail.com>
  11. 17 Apr, 2017 1 commit
  12. 10 Feb, 2017 1 commit
    • Emil Velikov's avatar
      configure.ac: supersede --enable-gallium-llvm over --enable-llvm · b3b41560
      Emil Velikov authored
      Currently we have extra (somewhat questionable) modularity, such that
      one could build some parts with LLVM while others w/o.
      That is extremely fragile, error prone and requires quite noticable
      amount of code throughout.
      Thus lets deprecate the gallium toggle in faviour of the generic one.
      The former will throw a warning when set, and it will be overwritten by
      the latter. This will allow gradual transition w/o breaking people's
      v2: Rebase, document in release notes.
      Cc: Dave Airlie <airlied@redhat.com>
      Signed-off-by: default avatarEmil Velikov <emil.velikov@collabora.com>
      Reviewed-by: Tobias Droste <tdroste@gmx.de> (v1)
  13. 03 Feb, 2017 1 commit
  14. 12 Jan, 2017 2 commits
  15. 24 Oct, 2016 1 commit
    • Emil Velikov's avatar
      automake: don't forget to pick wglext.h in the tarball · 3511a861
      Emil Velikov authored
      Earlier commit reworked the header install rules, to ensure that the
      correct ones are installed only as needed.
      By doing so it dropped a wildcard which was effectively including the
      wglext.h header in the tarball.
      Add the header to the top-level noinst_HEADERS, since the it is not
      meant to be installed (autoconf is not used on Windows plaforms).
      Fixes: a89faa20 ("autoconf: Make header install distinct for various
      APIs (v2)")
      Cc: "12.0 13.0" <mesa-stable@lists.freedesktop.org>
      Cc: Chuck Atkins <chuck.atkins@kitware.com>
      Signed-off-by: default avatarEmil Velikov <emil.velikov@collabora.com>
      Reviewed-by: Matt Turner's avatarMatt Turner <mattst88@gmail.com>
  16. 14 Oct, 2016 1 commit
  17. 13 Jun, 2016 1 commit
  18. 01 May, 2016 1 commit
  19. 29 Feb, 2016 2 commits
  20. 25 Feb, 2016 1 commit
  21. 11 Feb, 2016 1 commit
  22. 20 Nov, 2015 1 commit
  23. 22 Aug, 2015 1 commit
  24. 24 Mar, 2015 1 commit
  25. 18 Feb, 2015 1 commit
  26. 18 Dec, 2014 2 commits
  27. 12 Dec, 2014 5 commits
  28. 03 Sep, 2014 1 commit
    • Carl Worth's avatar
      build: Rename md5 to checksums as part of .PHONY target · 7528f6fd
      Carl Worth authored
      In commit 46d03d37 I renamed a Makefile target
      from md5 to checksums, (as we switched from MD5 checksums to SHA-256
      checksums, so the more general name is more future proof).
      But that commit missed one mention of "md5" as a dependency of the .PHONY
      target. Rename that here as well.
  29. 02 Sep, 2014 1 commit
  30. 31 Aug, 2014 1 commit
    • Emil Velikov's avatar
      mesa: fix make tarballs · 88cbe390
      Emil Velikov authored
      Current method of generating distribution tar-balls involves manually
      invoking make + target name in the appropriate places. This temporary
      solution is used until we get 'make dist' working.
      Currently it does not work, as in order to have the target (which is
      also a filename) available in the final Makefile we need to add a PHONY
      target + use the correct target name.
      Cc: "10.2 10.3" <mesa-stable@lists.freedesktop.org>
      Signed-off-by: Emil Velikov's avatarEmil Velikov <emil.l.velikov@gmail.com>
  31. 21 Aug, 2014 1 commit
    • Carl Worth's avatar
      Makefile: Switch from md5sums to sha256sums · 46d03d37
      Carl Worth authored
      We switched to these several stable releases ago, (since the MD5 algorithm has
      been broken for some time), but only now did I get around to fixing this in
      the Makefile rather than just performing this step manually.
      CC: "10.2 10.3" <mesa-stable@lists.freedesktop.org>
  32. 13 Dec, 2013 1 commit
    • Carl Worth's avatar
      Makefile: Add bin/test-driver to EXTRA_FILES · 93e399f6
      Carl Worth authored
      I'm not sure why this change is necessary. When I've built previous tar files
      (such as 9.2.4) with the "make tarballs" target, they include the
      bin/test-driver file. But at my first attempt to build the tar files for the
      10.0.1 release this file was not being included and the build failed.
      (cherry picked from commit d573899b)
      [The cherry pick is because I original applied this on the 10.0 branch while
      working on the 10.0.1 release. But if we don't have this on master as well,
      this issue will trip us up again the next time we make a new major-release
      branch off of master.]