1. 02 Nov, 2020 1 commit
  2. 05 Oct, 2020 3 commits
  3. 28 Aug, 2020 1 commit
  4. 17 Jul, 2020 2 commits
  5. 10 Jul, 2020 1 commit
  6. 29 May, 2020 1 commit
  7. 11 May, 2020 1 commit
  8. 09 May, 2020 1 commit
  9. 29 Apr, 2020 1 commit
  10. 07 Apr, 2020 1 commit
  11. 31 Mar, 2020 3 commits
    • Lubosz Sarnecki's avatar
      meson: Raise default warning level. · 79b739d5
      Lubosz Sarnecki authored
      Increases the default warning level to 3, which includes pedantic
      errors. Disable them on C++, which is the way it was done before.
      
      To resolve most pedantic warnings on C++ either the compiler standard
      would need to be increased to c++2a or the remaining copositor backends
      would require porting to plain C. One of each or both should happen in
      the future.
      79b739d5
    • Lubosz Sarnecki's avatar
      meson: Don't specify warning level manually. · a81b7e17
      Lubosz Sarnecki authored
      Since we already specify a `warning_level` in the project settings, it
      is redundant to manually specify it as compiler parameters.
      
      This patch resolves the following meson warning:
      ```
      meson.build:25: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
      meson.build:25: WARNING: Consider using the built-in warning_level option instead of using "-Wextra".
      ```
      a81b7e17
    • Lubosz Sarnecki's avatar
      comp/window_direct_mode: Use XCB/Xlib interop. · 4d0c4909
      Lubosz Sarnecki authored
      Since there currently is no Vulkan extension that takes XCB handles to
      aqcuire the display Xlib interop needs to be used.
      
      Before this patch Monado was opening connections for both APIs, which
      introduced overhead.
      
      Even though all XCB handles can be casted to Xlib ones, this cannot be
      done with the main xcb_connection_t / Display. In it's design the
      interop between both APIs can create a xcb_connection_t from a XCB
      handle, but not the other way round. So in an interop case the Xlib
      connection is the main one, since it's on a higher level.
      More information on this can be found here:
      https://xcb.freedesktop.org/MixingCalls/
      
      Unfortunately the clean solution for this would be to specify a Vulkan
      extension that takes XCB handles. This would make sense since Vulkan
      is aware of XCB in other parts of the API as well. In Mesa the Xlib
      structs will be ultimately casted to XCB.
      4d0c4909
  12. 03 Mar, 2020 1 commit
  13. 02 Mar, 2020 1 commit
  14. 10 Feb, 2020 1 commit
  15. 25 Jan, 2020 2 commits
  16. 14 Jan, 2020 1 commit
  17. 06 Nov, 2019 1 commit
  18. 05 Nov, 2019 2 commits
  19. 02 Nov, 2019 3 commits
  20. 31 Oct, 2019 1 commit
  21. 22 Oct, 2019 1 commit
    • Lubosz Sarnecki's avatar
      d/vive: Add native driver for the Vive. · e063e824
      Lubosz Sarnecki authored
      This adds a driver for the Vive family of devices based on Philipp
      Zabel's ouvrt.
      The driver currently only handles the IMU and main board report streams,
      but is able to acquire the JSON configuration and utilize it for IMU
      calibration as well as distortion configuration.
      e063e824
  22. 29 Sep, 2019 1 commit
  23. 26 Sep, 2019 6 commits