1. 18 Jul, 2019 2 commits
  2. 18 Apr, 2019 1 commit
    • Pekka Paalanen's avatar
      Rename compositor.h to libweston/libweston.h · 3d5d9476
      Pekka Paalanen authored
      The main idea is to make libweston users use the form
      
       #include <libweston/libweston.h>
      
      instead of the plain
      
       #include <compositor.h>
      
      which is prone to name conflicts. This is reflected both in the installed
      files, and the internal header search paths so that Weston would use the exact
      same form as an external project using libweston would.
      
      The public headers are moved under a new top-level directory include/ to make
      them clearly stand out as special (public API).
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.com>
      3d5d9476
  3. 24 May, 2018 2 commits
    • Pekka Paalanen's avatar
      pixman: make shadow buffer optional · 26ded94a
      Pekka Paalanen authored
      Add a flag to pixman-renderer for initializing the output with a shadow
      framebuffer. All backends were getting the shadow implcitly, so all
      backends are modified to ask for the shadow explicitly.
      
      Using a shadow buffer is usually beneficial, because read-modify-write
      cycles (blending) into a scanout-capable buffer may be very slow. The
      scanout framebuffer may also have reduced color depth, making blending
      and read-back produce inferior results.
      
      In some use cases though the shadow buffer might be just an extra copy
      hurting more than it helps. Whether it helps or hurts depends on the
      platform and the workload. Therefore let the backends control whether
      pixman-renderer uses a shadow buffer for an output or not.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Signed-off-by: default avatarFabien Lahoudere <fabien.lahoudere@collabora.com>
      Reviewed-by: default avatarIan Ray <ian.ray@ge.com>
      26ded94a
    • Pekka Paalanen's avatar
      pixman,drm: do not composite previous damage · acf50c3d
      Pekka Paalanen authored
      Pixman-renderer uses a single internal shadow buffer. It is enough to
      composite the current damage into shadow, but the copy to hw buffer
      needs to include the previous damage because of double-buffering in
      DRM-backend.
      
      This patch lets pixman-renderer do exactly that without compositing also
      the previous damage on DRM-renderer.
      
      Arguably weston_output should not have field previous_damage to begin
      with, because it implies double-buffering, which e.g. EGL does not
      guarantee. It would be better for each backend explicitly always provide
      any extra damage that should be copied to hw.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Signed-off-by: default avatarFabien Lahoudere <fabien.lahoudere@collabora.com>
      Reviewed-by: default avatarIan Ray <ian.ray@ge.com>
      acf50c3d
  4. 23 Jun, 2016 1 commit
  5. 15 Jun, 2015 1 commit
  6. 16 Aug, 2013 1 commit
  7. 08 Jan, 2013 1 commit
  8. 07 Jan, 2013 1 commit
  9. 06 Apr, 2012 1 commit
    • Benjamin Franzke's avatar
      Introduce weston-launch · bfeda130
      Benjamin Franzke authored
      weston-launch starts weston and provides mechanism
      for weston to set/drop drm master, open a tty,
      and read input devices without being root.
      
      Execution is allowed for local-active sessions
      or users in the group weston-launch.
      bfeda130
  10. 03 Jan, 2012 1 commit
    • Kristian H. Kristensen's avatar
      Rename wayland-compositor to weston · 8334bc1e
      Kristian H. Kristensen authored
      This rename addresses a few problems around the split between core
      Wayland and the wayland-demos repository.
      
      1) Initially, we had one big repository with protocol code, sample
      compositor and sample clients.  We split that repository to make it
      possible to implement the protocol without pulling in the sample/demo
      code.  At this point, the compositor is more than just a "demo" and
      wayland-demos doesn't send the right message.  The sample compositor
      is a useful, self-contained project in it's own right, and we want to
      move away from the "demos" label.
      
      2) Another problem is that the wayland-demos compositor is often
      called "the wayland compsitor", but it's really just one possible
      compositor.  Existing X11 compositors are expected to add Wayland
      support and then gradually phase out/modularize the X11 support, for
      example.  Conversely, it's hard to talk about the wayland-demos
      compositor specifically as opposed to, eg, the wayland protocol or a
      wayland compositor in general.
      
      We are also renaming the repo to weston, and the compositor
      subdirectory to src/, to emphasize that the main "output" is the
      compositor.
      8334bc1e
  11. 18 Dec, 2011 1 commit