1. 17 Jan, 2020 2 commits
  2. 13 Jan, 2020 6 commits
  3. 20 Dec, 2019 1 commit
  4. 18 Dec, 2019 1 commit
  5. 17 Dec, 2019 1 commit
    • Leandro Ribeiro's avatar
      backend-rdp: report a zero physical size to compositor · db6b141b
      Leandro Ribeiro authored
      The RDP-backend is reporting a non-zero physical size
      value, and there are some clients that get the resolution
      in pixels directly from the physical size reported. This
      leads to a resolution of 25.4 PPI (or 1px/1mm), which is too
      But there's no need for that. The physical size is reported
      on enabling the output (in the case of RDP-backend we have
      no information about it before this), and the resolution is
      already set in this moment.
      Report a zero physical size to compositor, what makes frontend
      and clients use their default values and applications become
      Signed-off-by: Leandro Ribeiro's avatarLeandro Ribeiro <leandrohr@riseup.net>
  6. 13 Dec, 2019 2 commits
  7. 12 Dec, 2019 6 commits
  8. 11 Dec, 2019 6 commits
  9. 09 Dec, 2019 2 commits
    • Stefan Agner's avatar
      backend-drm: Define potentially missing aspect-ratio bit definitions · 723c6a12
      Stefan Agner authored
      The aspect ratio definitions for 64:27 and 256:135 have been added with
      libdrm 2.4.95. However, Weston currently depends on libdrm 2.4.89 or
      higher. Define the definitions in Weston to support libdrm older than
      Fixes: #332
      Fixes: 6093772f
       ("backend-drm: Use aspect-ratio bit definitions from libdrm")
      Signed-off-by: Stefan Agner's avatarStefan Agner <stefan@agner.ch>
    • Stefan Agner's avatar
      renderer: change all frame_signal emission to pass previous_damage · 0bb94476
      Stefan Agner authored
      Commit adaf8c74 ("renderer: change frame_signal emission to pass
      previous_damage as data argument") missed updating all frame_signal
      emissions. Later commit 2619bfe4 ("move frame_signal emission to
      weston_output_repaint()") fixed this deficency along with moving the
      location of the emission. Due to an issue of the location change, this
      commit had to be reverted again.
      This makes sure that the pixman as well as the GL renderer now also
      emits the damage region instead of the Weston output.
      Fixes: adaf8c74
       ("renderer: change frame_signal emission to pass previous_damage as data argument")
      Signed-off-by: Stefan Agner's avatarStefan Agner <stefan@agner.ch>
  10. 06 Dec, 2019 1 commit
  11. 04 Dec, 2019 1 commit
  12. 03 Dec, 2019 2 commits
  13. 02 Dec, 2019 1 commit
  14. 01 Dec, 2019 1 commit
  15. 28 Nov, 2019 4 commits
    • Daniel Stone's avatar
      option-parser: Make bools boolean · dd8219b3
      Daniel Stone authored
      When option-parser is confronted with a boolean option, have it write a
      bool rather than treating the value as a pointer to an int32.
      (lib)weston already heavily uses bool types internally, so this has the
      nice side effect of eliminating quite a few local variables which only
      existed as integer shadows of internal boolean variables.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Daniel Stone's avatar
      tests/config-parser: Remove useless duplicate test · b8c39264
      Daniel Stone authored
      test012 and test013 were exact duplicates of each other: asserting that
      they could successfully look up a single boolean value.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Daniel Stone's avatar
      config-parser: Make get_bool be bool · 51d995ad
      Daniel Stone authored
      Wayland innovated a lot of cool things, but non-binary boolean values is
      the great advances of our time.
      Make config_parser_get_bool() work on boolean values, and switch all its
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Simon Ser's avatar
      clients: drop simple-dmabuf-drm · 0a4f6e7d
      Simon Ser authored
      This client contains driver-specific code to allocate buffers. However clients
      shouldn't contain driver-specific code and should rely on e.g. mesa to allocate
      buffers via standard interfaces.
      Additionally, because the build system always tries to enable all features, some
      experimental drivers and drivers that aren't included in amd64 distribution
      packages were required. Users would need to manually disable some drivers.
      Releasers would need to install libdrm from source (because the release process
      forbids adding custom build flags). Dropping simple-dmabuf-drm simplifies both
      building and releasing.
      The functionality previously tested via simple-dmabuf-drm can now be tested with
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
  16. 27 Nov, 2019 3 commits