1. 05 Sep, 2018 3 commits
  2. 04 Sep, 2018 2 commits
    • Eric Engestrom's avatar
      add gitlab-ci builds of libdrm · 4a9030dc
      Eric Engestrom authored
      It currently does 4 builds: 2 using Meson and 2 using Autotools, 2 using
      the latest dependencies on ArchLinux and 2 using very old dependencies
      on Debian (including manually building libpciaccess to have the oldest
      version supported, to make sure it keeps being supported).
      All the build options are turned on for both Meson and Autotools.
      Signed-off-by: Eric Engestrom's avatarEric Engestrom <eric.engestrom@intel.com>
      Reviewed-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Daniel Vetter's avatar
      Add basic CONTRIBUTING file · 4d87c2e2
      Daniel Vetter authored
      I picked up a bunch of the pieces from wayland's version:
      The weston one is fairly similar. Then I rather massively trimmed it
      down since in reality libdrm is a bit a dumping ground with very few
      real rules. The commit rights and CoC sections I've copied verbatim
      from igt respectively drm-misc. Weston/Wayland only differ in their
      pick of how many patches you need (10 instead of 5). I think for
      libdrm this is supremely relevant, since most everyone will get their
      commit rights by contributing already to the kernel or mesa and having
      commit rights there already.
      Anyway, I figured this is good to get the rules documented, even if
      there's mostly not many rules.
      Note: This references maintainers in a MAINTAINERS file, which needs
      to be created first.
      Note: With the gitlab migration the entire commit rights process is
      still a bit up in the air. But gitlab commit rights and roles are
      hierarchical, so we ca...
  3. 03 Sep, 2018 2 commits
  4. 01 Sep, 2018 1 commit
  5. 27 Aug, 2018 1 commit
  6. 24 Aug, 2018 1 commit
  7. 23 Aug, 2018 2 commits
  8. 17 Aug, 2018 3 commits
  9. 16 Aug, 2018 2 commits
  10. 15 Aug, 2018 1 commit
    • Michel Dänzer's avatar
      amdgpu: Use uint32_t i in amdgpu_find_bo_by_cpu_mapping · 1e12c16d
      Michel Dänzer authored
      The compiler points out that an int doesn't work as intended if
      dev->bo_handles.max_key > INT_MAX:
      ../../amdgpu/amdgpu_bo.c: In function ‘amdgpu_find_bo_by_cpu_mapping’:
      ../../amdgpu/amdgpu_bo.c:550:16: warning: comparison of integer expressions of different signedness: ‘int’ and ‘uint32_t’ {aka ‘unsigned int’} [-Wsign-compare]
        for (i = 0; i < dev->bo_handles.max_key; i++) {
      ../../amdgpu/amdgpu_bo.c:558:8: warning: comparison of integer expressions of different signedness: ‘int’ and ‘uint32_t’ {aka ‘unsigned int’} [-Wsign-compare]
        if (i < dev->bo_handles.max_key) {
      Fixes: 4d454424 ("amdgpu: add a function to find bo by cpu mapping
      Reviewed-by: Christian König's avatarChristian König <christian.koenig@amd.com>
      Reviewed-by: Junwei Zhang's avatarJunwei Zhang <Jerry.Zhang@amd.com>
  11. 14 Aug, 2018 1 commit
  12. 08 Aug, 2018 5 commits
  13. 07 Aug, 2018 9 commits
  14. 01 Aug, 2018 1 commit
  15. 30 Jul, 2018 5 commits
  16. 25 Jul, 2018 1 commit