1. 14 Aug, 2020 1 commit
  2. 28 Nov, 2019 1 commit
    • 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
      simple-dmabuf-egl.
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
      0a4f6e7d
  3. 25 Jun, 2019 2 commits
  4. 28 Mar, 2019 1 commit
  5. 11 Feb, 2019 1 commit
  6. 06 Feb, 2019 1 commit
  7. 07 Aug, 2018 1 commit
  8. 11 Jun, 2018 1 commit
  9. 15 Aug, 2016 2 commits
  10. 02 Aug, 2016 1 commit
  11. 07 Jul, 2016 1 commit
  12. 06 Jul, 2016 1 commit
  13. 05 Jul, 2016 2 commits
  14. 23 Jun, 2016 1 commit
  15. 03 Jun, 2016 1 commit
    • Pekka Paalanen's avatar
      Remove Raspberry Pi backend and renderer · ca52b31d
      Pekka Paalanen authored
      This patch completely removes the Raspberry Pi backend and the renderer.
      
      The backend and the renderer were written to use the proprietary
      DispmanX API available only on the Raspberry Pi, to demonstrate what the
      tiny computer is capable of graphics wise. They were also used to
      demonstrate how Wayland and Weston in particular could leverage hardware
      compositing capabilities that are not OpenGL. The backend was first
      added in e8de35c9, in 2012.
      
      Since then, the major point has been proven. Over time, support for the
      rpi-backend diminished, it started to deteriorate and hinder Weston
      development. On May 11, I tried to ask if anyone actually cared about
      the rpi-backend, but did not get any votes for keeping it:
      https://lists.freedesktop.org/archives/wayland-devel/2016-May/028764.html
      
      The rpi-backend is a good example of how using an API that is only
      available for specific hardware, even more so as it is only available
      with a proprietary driver stack, is not maintainable in the long run.
      Most developers working on Weston either just cannot, or cannot bother
      to test things also on the RPi. Breakage creeps in without anyone
      noticing. If someone actually notices it, fixing it will require a very
      specific environment to be able to test. Also the quality of the
      proprietary implementation fluctuated. There are reports that RPi
      firmware updates randomly broke Weston, and that nowadays it is very
      hard to find a RPi firmware version that you could expect to work with
      Weston if Weston itself was not broken. We are not even sure what is
      broken nowadays.
      
      This removal does not leave Raspberry Pi users cold (for long), though.
      There is serious work going on in implementing a FOSS driver stack for
      Raspberry Pi, including modern kernel DRM drivers and Mesa drivers. It
      might not be fully there yet, but the plan is to be able to use the
      standard DRM-backend of Weston on the RPis. See:
      http://dri.freedesktop.org/wiki/VC4/
      
      The rpi-backend had its moments. Now, it needs to go. Good riddance!
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: default avatarDerek Foreman <derekf@osg.samsung.com>
      Acked-by: default avatarBryce Harrington <bryce@osg.samsung.com>
      Acked-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      ca52b31d
  16. 17 Jul, 2015 1 commit
  17. 16 Jul, 2015 1 commit
  18. 06 Feb, 2014 1 commit
  19. 20 Jul, 2012 1 commit
  20. 15 Feb, 2011 1 commit
  21. 10 Nov, 2010 1 commit
  22. 08 Nov, 2010 1 commit
  23. 14 Sep, 2010 2 commits
  24. 06 Nov, 2008 2 commits