1. 17 Nov, 2015 3 commits
  2. 16 Nov, 2015 3 commits
  3. 06 Nov, 2015 3 commits
  4. 04 Nov, 2015 4 commits
  5. 29 Oct, 2015 1 commit
  6. 26 Oct, 2015 2 commits
  7. 21 Oct, 2015 1 commit
    • Derek Foreman's avatar
      shm: Add shm_buffer ref and shm_pool unref functions · eba83cd5
      Derek Foreman authored
      Sometimes the compositor wants to make sure a shm pool doesn't disappear
      out from under it.
      
      For example, in Enlightenment, rendering happens in a separate thread
      while the main thread can still dispatch events.  If a client is destroyed
      during rendering, all its resources are cleaned up and its shm pools are
      unmapped.  This causes the rendering thread to segfault.
      
      This patch adds a way for the compositor to increment the refcount of the
      shm pool so it can't disappear, and decrement it when it's finished.
      
      The ref/unref are asymmetrical (ref returns the pool) because it's
      possible the buffer itself will be gone when you need to unref the pool.
      Reviewed-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Signed-off-by: default avatarDerek Foreman <derekf@osg.samsung.com>
      eba83cd5
  8. 09 Oct, 2015 2 commits
  9. 08 Oct, 2015 2 commits
  10. 06 Oct, 2015 4 commits
  11. 05 Oct, 2015 1 commit
  12. 22 Sep, 2015 2 commits
  13. 21 Sep, 2015 1 commit
  14. 16 Sep, 2015 1 commit
  15. 01 Sep, 2015 1 commit
  16. 24 Aug, 2015 1 commit
  17. 16 Aug, 2015 1 commit
  18. 14 Aug, 2015 1 commit
    • Dima Ryazanov's avatar
      client: require WAYLAND_DISPLAY to be set · fb7e1302
      Dima Ryazanov authored
      Although defaulting to wayland-0 seems convenient, it has an undesirable
      side effect: clients may unintentionally connect to the wrong compositor.
      Generally, it's safer to fail instead. Here's a real example:
      
      In Fedora 22, Gtk+ prefers Wayland over X11, though the default session is still
      a normal X11 Gnome session. When you launch a Gtk+ app, it will try Wayland,
      fail, then try X11, and succesfully start up. That works fine.
      
      Now suppose you launch Weston while running the Gnome session. Suddenly, all
      of the Gtk+ apps launched from Gnome will show up inside Weston instead.
      That's unexpected. There's also no good way to prevent that from happening
      (other than perhaps setting WAYLAND_DISPLAY to an invalid value when launching
      an app).
      
      Not using wayland-0 as the default will solve that problem: an app launched
      from the X11 Gnome session will use the X11 backend regardless of whether
      there's a wayland compositor running at the same time.
      
      Everything else should work as before. The compositor already sets
      the WAYLAND_DISPLAY when starting the session, so the lack of the default value
      should not make a difference to the user.
      Signed-off-by: Dima Ryazanov's avatarDima Ryazanov <dima@gmail.com>
      Acked-by: Pekka Paalanen's avatarPekka Paalanen <ppaalanen@gmail.com>
      Acked-by: default avatarGiulio Camuffo <giuliocamuffo@gmail.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Acked-by: Jasper St. Pierre's avatarJasper St. Pierre <jstpierre@mecheye.net>
      Reviewed-by: default avatarRyo Munakata <ryomnktml@gmail.com>
      
      [Pekka: dropped the wayland-server.c hunk, adjusted summary]
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      fb7e1302
  19. 06 Aug, 2015 1 commit
  20. 31 Jul, 2015 5 commits