1. 17 Nov, 2011 1 commit
    • Kristian Høgsberg's avatar
      Add display event to acknowledge ID deletion · 3a1e6df3
      Kristian Høgsberg authored
      We need to make sure the client doesn't reuse an object ID until the
      server has seen the destroy request.  When a client destroys an ID
      the server will now respond with the display.delete_id event, which lets
      the client block reuse until it receives the event.
      3a1e6df3
  2. 15 Nov, 2011 2 commits
    • Kristian Høgsberg's avatar
      util: Add wl_list_insert_list() · 51f50b8c
      Kristian Høgsberg authored
      51f50b8c
    • Andrea Canciani's avatar
      hash: Improve double hashing · 3175e91e
      Andrea Canciani authored
      Instead of artificially introducing collisions in the step value by
      replacing 0 with 1 (which causes the value 1 to have twice the
      frequency of any other value), the step value can simply be computed
      as an uniformly distributed value in the range [1, rehash], extremes
      included.
      
      This is safe because any step value smaller than the hash modulus is
      co-prime with it, hence induces an orbit which includes every integer
      in [0, size - 1].
      3175e91e
  3. 31 Oct, 2011 2 commits
  4. 29 Oct, 2011 1 commit
    • Kristian Høgsberg's avatar
      event-loop: Fix idle handler dispatch corner case · f86338d6
      Kristian Høgsberg authored
      When the last idle handler queues another idle handler, we fail to
      dispatch that last handler.  The wl_list_for_each_safe loop looks up
      the next pointer before running the handler, and at that point it points
      to the head of the list and the loop terminates.
      
      Instead, just loop until the list is empty.
      f86338d6
  5. 24 Oct, 2011 3 commits
  6. 20 Oct, 2011 1 commit
  7. 12 Oct, 2011 2 commits
  8. 11 Oct, 2011 4 commits
  9. 06 Sep, 2011 1 commit
  10. 04 Sep, 2011 1 commit
  11. 01 Sep, 2011 1 commit
  12. 31 Aug, 2011 1 commit
    • Kristian Høgsberg's avatar
      Remove the wl_visual interface · c640571c
      Kristian Høgsberg authored
      The visual interface was meant to be a generic mechanism for
      specifying the content of a buffer.  It goes back to before we had the
      buffer factory interfaces (like wl_drm and wl_shm) and we wanted to
      keep it open-ended enough that yuv, png or even svg buffer or so would
      be possible.
      
      Now that we have the buffer abstraction, we can add different buffer
      types by introducing new interfaces that create buffers.  It only
      makes sense to leave it to those interfaces to specify the contents of
      the buffers.
      
      For wl_shm, this means that we now just specify the pixel format using
      an enum.  For EGL buffers, the exact pixel formats are controlled by
      the implementation (part of wl_drm and similar), and from the client
      point of view, everything is controlled using EGLConfigs.
      c640571c
  13. 29 Aug, 2011 3 commits
  14. 27 Aug, 2011 17 commits