1. 26 Apr, 2019 1 commit
  2. 14 Feb, 2019 2 commits
  3. 19 Nov, 2018 1 commit
  4. 17 Nov, 2018 1 commit
    • Emma Anholt's avatar
      loader: Factor out the common driver opening logic from each loader. · d971a423
      Emma Anholt authored
      I copied the code from egl_dri2.c, but the functionality was equivalent
      between all the loaders other than their particular environment variables.
      v2: Drop the logging function equivalent to loader_default_logger()
          (requested by Eric, Emil).  Move the SCons workaround across.  Drop
          the now-unused driGetDriverExtensions() declaration that was lost in a
      Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> (v1)
      Reviewed-by: Emil Velikov <emil.velikov@collabora.com> (v1)
  5. 12 Nov, 2018 1 commit
  6. 09 Oct, 2018 1 commit
  7. 01 Aug, 2018 1 commit
  8. 23 Feb, 2018 1 commit
  9. 15 Feb, 2018 1 commit
  10. 09 Feb, 2018 2 commits
  11. 16 Jan, 2018 1 commit
  12. 02 Nov, 2017 1 commit
  13. 14 Sep, 2017 1 commit
  14. 12 Sep, 2017 1 commit
  15. 18 Jul, 2017 4 commits
  16. 30 Jun, 2017 1 commit
  17. 29 Jun, 2017 1 commit
  18. 15 Jun, 2017 1 commit
  19. 29 May, 2017 4 commits
  20. 02 May, 2017 1 commit
  21. 09 Apr, 2017 1 commit
  22. 31 Mar, 2017 1 commit
  23. 29 Mar, 2017 1 commit
    • Thomas Hellstrom's avatar
      gbm/dri: Flush after unmap · ba8df228
      Thomas Hellstrom authored
      Drivers may queue dma operations on the context at unmap time so we need
      to flush to make sure the data gets to the bo. Ideally the application
      would take care of this, but since there appears to be no exported gbm
      flush functionality we need to explicitly flush at unmap time.
      This fixes a problem where kmscube on vmwgfx in rgba textured mode would
      render using an uninitialized texture rather than the intended
      rgba pattern.
      Signed-off-by: default avatarThomas Hellstrom <thellstrom@vmware.com>
      Reviewed-by: Emma Anholt's avatarEric Anholt <eric@anholt.net>
  24. 23 Mar, 2017 1 commit
    • Daniel Stone's avatar
      gbm: Use unsigned for BO offset getter · 378025ca
      Daniel Stone authored
      The actual offset returned is uint32_t, however int64_t was used as the
      return type from gbm_bo_get_offset to allow negative returns to signal
      errors to the caller.
      In case of an error getting the offset, the user will also be unable to
      get the handle/FD, and thus have nothing to offset into. This means that
      returning 0 as an error value is harmless, allowing us to change the
      return type to uint32_t in order to avoid signed/unsigned confusion in
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Cc: Ben Widawsky <ben@bwidawsk.net>
      Cc: Jason Ekstrand <jason@jlekstrand.net>
  25. 21 Mar, 2017 1 commit
  26. 15 Mar, 2017 2 commits
    • Ben Widawsky's avatar
      gbm: Export a get modifiers · 8378c576
      Ben Widawsky authored
      This patch originally had i965 specific code and was named:
      commit 61cd3c52b868cf8cb90b06e53a382a921eb42754
      Author: Ben Widawsky <ben@bwidawsk.net>
      Date:   Thu Oct 20 18:21:24 2016 -0700
          gbm: Get modifiers from DRI
      To accomplish this, two new query tokens are added to the extension:
      The query extension only supported 32b queries, and modifiers are 64b,
      so we needed two of them.
      NOTE: The extension version is still set to 13, so none of this will
      actually be called.
      v2: Error handling of queryImage (Emil)
      Signed-off-by: Ben Widawsky's avatarBen Widawsky <ben@bwidawsk.net>
      Reviewed-by: Jason Ekstrand's avatarJason Ekstrand <jason@jlekstrand.net>
      Reviewed-by: Emil Velikov's avatarEmil Velikov <emil.velikov@collabora.com>
    • Ben Widawsky's avatar
      gbm: Introduce modifiers into surface/bo creation · 63bd2ae7
      Ben Widawsky authored
      The idea behind modifiers like this is that the user of GBM will have
      some mechanism to query what properties the hardware supports for its BO
      or surface. This information is directly passed in (and stored) so that
      the DRI implementation can create an image with the appropriate
      A getter() will be added later so that the user GBM will be able to
      query what modifier should be used.
      Only in surface creation, the modifiers are stored until the BO is
      actually allocated. In regular buffer allocation, the correct modifier
      can (will be, in future patches be chosen at creation time.
      v2: Make sure to check if count is non-zero in addition to testing if
      calloc fails. (Daniel)
      v3: Remove "usage" and "flags" from modifier creation. Requested by
      v4: Take advantage of the "INVALID" modifier added by the GET_PLANE2
      v5: Don't bother with storing modifiers for gbm_bo_create because that's
      a synchronous operation and we can actually select the correct modifier
      at create time (done in a later patch) (Jason)
      v6: Make modifier condition outside the check so that dri_use will work
      properly (Jason)
      Cc: Kristian Høgsberg <krh@bitplanet.net>
      References (v4): https://lists.freedesktop.org/archives/intel-gfx/2017-January/116636.html
      Signed-off-by: Ben Widawsky's avatarBen Widawsky <ben@bwidawsk.net>
      Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> (v1)
      Reviewed-by: Jason Ekstrand's avatarJason Ekstrand <jason@jlekstrand.net>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
  27. 09 Mar, 2017 5 commits