1. 17 Dec, 2018 1 commit
  2. 03 Dec, 2018 1 commit
  3. 28 Nov, 2018 2 commits
  4. 26 Nov, 2018 1 commit
  5. 22 Nov, 2018 1 commit
  6. 21 Nov, 2018 1 commit
    • Bas Nieuwenhuizen's avatar
      vulkan: Allow storage images in the WSI. · 33b2f74e
      Bas Nieuwenhuizen authored
      Since apps also have to follow the ImageFormatProperties query,
      we can disallow formats that don't allow image stores (for AMD
      that would be SRGB formats).
      
      Note that this only affects anything if the app actually decides
      to use the flag.
      
      Had someone ask for this on IRC and at least on the AMD side we
      can support it.
      Reviewed-by: Jason Ekstrand's avatarJason Ekstrand <jason@jlekstrand.net>
      33b2f74e
  7. 06 Nov, 2018 1 commit
  8. 05 Nov, 2018 2 commits
  9. 31 Oct, 2018 1 commit
  10. 30 Oct, 2018 1 commit
  11. 29 Oct, 2018 2 commits
  12. 26 Oct, 2018 1 commit
  13. 25 Oct, 2018 1 commit
  14. 18 Oct, 2018 3 commits
  15. 13 Oct, 2018 1 commit
  16. 01 Oct, 2018 1 commit
  17. 27 Sep, 2018 1 commit
  18. 24 Sep, 2018 2 commits
  19. 21 Sep, 2018 1 commit
  20. 10 Sep, 2018 1 commit
  21. 28 Aug, 2018 1 commit
  22. 24 Aug, 2018 1 commit
  23. 23 Aug, 2018 2 commits
  24. 22 Aug, 2018 1 commit
  25. 18 Aug, 2018 1 commit
  26. 10 Aug, 2018 1 commit
  27. 07 Aug, 2018 1 commit
  28. 25 Jul, 2018 1 commit
  29. 10 Jul, 2018 1 commit
  30. 09 Jul, 2018 1 commit
  31. 06 Jul, 2018 1 commit
  32. 27 Jun, 2018 1 commit
  33. 23 Jun, 2018 1 commit
    • Keith Packard's avatar
      vulkan: add VK_EXT_display_control [v10] · 86c8d93e
      Keith Packard authored
      This extension provides fences and frame count information to direct
      display contexts. It uses new kernel ioctls to provide 64-bits of
      vblank sequence and nanosecond resolution.
      
      v2: Remove DRM_CRTC_SEQUENCE_FIRST_PIXEL_OUT flag. This has
          been removed from the proposed kernel API.
      
          Add NULL parameter to drmCrtcQueueSequence ioctl as we
          don't care what sequence the event was actually queued to.
      
      v3: Adapt to pthread clock switch to MONOTONIC
      
      v4: Fix scope for wsi_display_mode andwsi_display_connector allocs
      Suggested-by: Jason Ekstrand's avatarJason Ekstrand <jason@jlekstrand.net>
      
      v5: Adopt Jason Ekstrand's coding conventions
      
          Declare variables at first use, eliminate extra whitespace between
          types and names. Wrap lines to 80 columns.
      
          Use wsi_rel_to_abs_time helper function to convert relative
          timeouts to absolute timeouts without causing overflow.
      Suggested-by: Jason Ekstrand's avatarJason Ekstrand <jason.ekstrand@intel.com>
      
      v6:
          Change WSI fence wait function to return VkResult instead of
          bool. This makes the meaning of the return value easier to
          understand, and allows for the indication of failure.
      
          Also change the WSI fence wait function to take only absolute
          timeouts and not provide an option for a relative timeout. No
          users wanted relative timeouts, and it's simpler if that option
          isn't available.
      
          Terminate the DPMS property loop once we've found the property.
      
          Assert that the fence hasn't already been destroyed in
          wsi_display_fence_destroy.
      
          Rearrange the event handler function order in the file to place
          routines in an easier to find order.
      Suggested-by: Jason Ekstrand's avatarJason Ekstrand <jason.ekstrand@intel.com>
      
      v7:
          Adapt to API changes for surface_get_capabilities
      
      v8:
          Use wsi->alloc in register_display_event so that callers
          don't have to dig out an allocator for us.
      
      v9:
          Fix a few minor formatting issues
      Suggested-by: Jason Ekstrand's avatarJason Ekstrand <jason.ekstrand@intel.com>
      
      v10:
          Use wsi->alloc if none provided in wsi_display_fence_alloc.
      
          Now that drivers are expected to pass the allocator argument
          straight through from the application, we need to check those
          for NULL everywhere.
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Reviewed-by: Jason Ekstrand's avatarJason Ekstrand <jason.ekstrand@intel.com>
      86c8d93e