1. 16 Aug, 2011 1 commit
  2. 23 Jun, 2011 1 commit
  3. 08 Jun, 2011 1 commit
  4. 06 May, 2011 1 commit
  5. 07 Feb, 2011 1 commit
  6. 03 Feb, 2011 1 commit
  7. 28 Jan, 2011 1 commit
  8. 09 Jan, 2011 1 commit
    • zjuan's avatar
      dri2: release texture image. · e59fa4c4
      zjuan authored
      Add release function for texture_from_pixmap extension.
      Some platform need to release texture image for texture_from_pixmap
      extension, add this interface for those platforms.
      e59fa4c4
  9. 23 Sep, 2010 1 commit
  10. 22 Sep, 2010 1 commit
  11. 25 Aug, 2010 1 commit
  12. 20 Jul, 2010 1 commit
  13. 11 May, 2010 1 commit
  14. 28 Apr, 2010 1 commit
  15. 22 Apr, 2010 1 commit
  16. 27 Mar, 2010 1 commit
  17. 21 Mar, 2010 1 commit
  18. 24 Feb, 2010 1 commit
  19. 16 Feb, 2010 1 commit
    • Francisco Jerez's avatar
      dri2: Event driven buffer validation. · 61d26bc8
      Francisco Jerez authored
      
      
      When a buffer invalidation event is received from the X server, the
      "invalidate" hook of the DRI2 flush extension is executed: A generic
      implementation (dri2InvalidateDrawable) is provided that just bumps
      the "pStamp" sequence number in __DRIdrawableRec.
      
      For old servers not supporting buffer invalidation events, the
      invalidate hook will be called before flushing the fake front/back
      buffer (that's typically once per frame -- not a lot worse than the
      situation we were in before).
      
      No effort has been made on preserving backwards compatibility with
      version 2 of the flush extension, but I think it's acceptable because
      AFAIK no released stack is making use of it.
      
      Signed-off-by: default avatarKristian Høgsberg <krh@bitplanet.net>
      61d26bc8
  20. 09 Feb, 2010 1 commit
  21. 08 Jan, 2010 1 commit
    • Jesse Barnes's avatar
      DRI2: add SwapBuffers support · a35f6bb2
      Jesse Barnes authored
      
      
      Support the new DRI2 protocol request, DRI2SwapBuffers, in both direct
      and indirect rendering context.  This request allows the display server
      to optimize back->front swaps (e.g. through page flipping) and allows us
      to more easily support other GLX features like swap interval and the OML
      sync extension in DRI2.
      
      Signed-off-by: Jesse Barnes's avatarJesse Barnes <jbarnes@virtuousgeek.org>
      a35f6bb2
  22. 25 Apr, 2009 1 commit
  23. 24 Apr, 2009 1 commit
  24. 09 Apr, 2009 1 commit
  25. 20 Mar, 2009 1 commit
    • Emma Anholt's avatar
      Fix DRI2 accelerated EXT_texture_from_pixmap with GL_RGB format. · 66175aac
      Emma Anholt authored
      
      
      This requires upgrading the interface so that the argument to
      glXBindTexImageEXT isn't just dropped on the floor.  Note that this only
      fixes the accelerated path on Intel, as Mesa's texture format support is
      missing x8r8g8b8 support (right now, GL_RGB textures get uploaded as a8r8gb8,
      but in this case we're not doing the upload so we can't really work around it
      that way).
      
      Fixes bugs with compositors trying to use shaders that use alpha channels, on
      windows without a valid alpha channel.  Bug #19910 and likely others as well.
      
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      66175aac
  26. 23 Feb, 2009 1 commit
  27. 19 Jan, 2009 2 commits
  28. 18 Dec, 2008 2 commits
  29. 29 Aug, 2008 1 commit
  30. 08 Aug, 2008 1 commit
  31. 11 Jun, 2008 2 commits
  32. 20 May, 2008 1 commit
  33. 31 Mar, 2008 1 commit
    • Kristian Høgsberg's avatar
      DRI interface changes and DRI2 direct rendering support. · e82dd8c6
      Kristian Høgsberg authored
      Add DRI2 direct rendering support to libGL and add DRI2 client side
      protocol code.  Extend the GLX 1.3 create drawable functions in
      glx_pbuffer.c to call into the DRI driver when possible.
      
      Introduce __DRIconfig, opaque struct that represents a DRI driver
      configuration.  Get's rid of the open coded __GLcontextModes in the
      DRI driver interface and the context modes create and destroy
      functions that the loader was requires to provide.  glcore.h is no
      longer part of the DRI driver interface.  The DRI config is GL binding
      agnostic, that is, not specific to GLX, EGL or other bindings.
      
      The core API is now also an extension, and the driver exports a list
      of extensions as the symbol __driDriverExtensions, which the loader
      must dlsym() for.  The list of extension will always include the DRI
      core extension, which allows creating and manipulating DRI screens,
      drawables and contexts.  The DRI legacy extension, when available,
      provides alternative entry points for creating the DRI objects that
      work with the XF86DRI infrastructure.
      
      Change DRI2 client code to not use drm drawables or contexts.  We
      never used drm_drawable_t's and the only use for drm_context_t was as
      a unique identifier when taking the lock.  We now just allocate a
      unique lock ID out of the DRILock sarea block.  Once we get rid of the
      lock entirely, we can drop this hack.
      
      Change the interface between dri_util.c and the drivers, so that the
      drivers now export the DriverAPI struct as driDriverAPI instead of the
      InitScreen entry point.  This lets us avoid dlsym()'ing for the DRI2
      init screen function to see if DRI2 is supported by the driver.
      e82dd8c6
  34. 10 Mar, 2008 2 commits
    • Kristian Høgsberg's avatar
      DRI2: Make setTexBuffer take a __DRIdrawable instead of a BO handle. · dcbe215c
      Kristian Høgsberg authored
      This fixes a problem where texturing from the same Pixmap more than
      once per batchbuffer would hang the DRI driver.  We just use the region
      associated with the front left renderbuffer of the __DRIdrawable for
      texturing, which avoids creating different regions for the same BO.
      
      This change also make GLX_EXT_texture_from_pixmap work for direct
      rendering, since tracking the __DRIdrawable -> BO handle now uses
      the standard DRI2 event buffer.  Of course, DRI2 direct rendering
      doesn't exist yet.
      
      Finally, this commit bumps the DRI interface version again, accounting
      for the change in the DRI_TEX_BUFFER extension and the change in
      commit 0bba0e5b to pass in the
      event buffer head index on drawable creation.
      dcbe215c
    • Kristian Høgsberg's avatar
      DRI2: Add event buffer head as an argument to driCreateNewDrawable(). · 0bba0e5b
      Kristian Høgsberg authored
      The DRI driver needs to know where in the buffer to start reading.
      0bba0e5b
  35. 04 Mar, 2008 1 commit
    • Kristian Høgsberg's avatar
      [dri2] Add tail pointer to reemitDrawableInfo callback. · 3d608c7a
      Kristian Høgsberg authored
      When the DRI doesn't parse the event buffer for a while, the X server
      may overwrite data that the driver didn't get a chance to look at.  The
      reemitDrawableInfo callback requests that the X server reemit all info
      for the specified drawable.  To make use of this, the drive needs to know
      the new tail pointer so it know where to start reading from.
      3d608c7a
  36. 29 Feb, 2008 1 commit