1. 30 Aug, 2013 3 commits
  2. 19 Aug, 2013 4 commits
  3. 15 Aug, 2013 1 commit
  4. 13 Aug, 2013 1 commit
  5. 12 Aug, 2013 2 commits
  6. 09 Aug, 2013 8 commits
  7. 08 Aug, 2013 1 commit
  8. 07 Aug, 2013 4 commits
  9. 06 Aug, 2013 3 commits
  10. 29 Jul, 2013 2 commits
  11. 13 Jul, 2013 4 commits
  12. 09 Jul, 2013 6 commits
    • Kristian Høgsberg's avatar
      Bump version to 1.1.91 · 3f3671e9
      Kristian Høgsberg authored
      3f3671e9
    • Kristian Høgsberg's avatar
    • Kristian Høgsberg's avatar
      wayland-server: Don't close display fd in fatal error handler · 93d888ae
      Kristian Høgsberg authored
      We can't do that there, we have to make sure it stays a valid fd until
      the application calls wl_display_disconnect().  Otherwise the application
      may end up poll()ing on a stale or wrong fd in case another part of the
      application (or another thread) triggered a fatal error.
      93d888ae
    • Kristian Høgsberg's avatar
      wayland-server: Return 0 from read_events() in case of EAGAIN · becca5fc
      Kristian Høgsberg authored
      Getting no data from the socket is not an error condition.  This may
      happen in case of calling prepare_read() and then read_events() with
      no other pending readers and no data in the socket.  In general,
      read_events() may not queue up events in the given event queue.  From
      a given threads point of view it doesn't matter whether events were
      read and put in a different event queue or no events were read at all.
      becca5fc
    • Neil Roberts's avatar
      wayland-client: Treat EOF when reading the wayland socket as an error · 12cea955
      Neil Roberts authored
      If EOF is encountered while reading from the Wayland socket, make
      wl_display_read_events() return -1 so that it will be treated as an
      error. The documentation for this function states that it will set
      errno when there is an error so it additionally makes up an errno of
      EPIPE.
      
      If we don't do this then when the compositor quits the Wayland socket
      will be become ready for reading but wl_display_dispatch will do
      nothing which typically makes the application take up 100% CPU. In
      particular eglSwapBuffers will likely get stuck in an infinite busy
      loop because it repeatedly calls wl_display_dispatch_queue while it
      waits for the frame callback.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=703892
      12cea955
    • Kristian Høgsberg's avatar
      wayland-server: Add wl_global_create/destroy() · 4cffa0fd
      Kristian Høgsberg authored
      This patch introduces wl_global_create() and wl_global_destroy() as
      replacements for wl_display_add_global() and wl_display_remove_global().
      The add/remove_global API did not allow a compositor to indicate
      the implemented version of a global, it just took the version from
      the interface meta data.  The problem is that the meta data
      (which lives in libwayland-server.so) can get out of sync with a
      compositor implementation.  The compositor will then advertise a
      higher version of a global than what it actually implements.
      
      The new API lets a compositor pass in a version when it registers
      a global, which solves the problem.  The add/remove API is deprecated
      with this patch and will be removed.
      4cffa0fd
  13. 03 Jul, 2013 1 commit
    • Daiki Ueno's avatar
      build: Add wayland-scanner.pc. · 40fc79d5
      Daiki Ueno authored
      To allow user program to include wayland-scanner.m4 in tarball, move
      the path variables from it into wayland-scanner.pc.
      40fc79d5