summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorPekka Paalanen <pekka.paalanen@collabora.co.uk>2016-06-01 11:22:51 +0300
committerPekka Paalanen <pekka.paalanen@collabora.co.uk>2016-06-03 10:23:52 +0300
commitca52b31d3f867d9a14b2a3b9fcd4f21aa5fb0a3d (patch)
tree0f62c82235cd2079198b975716b689e2ee76e0cb /README
parente57056f55c5659eba28c69c31ac89bc9b1e0240e (diff)
downloadweston-ca52b31d3f867d9a14b2a3b9fcd4f21aa5fb0a3d.tar.gz
weston-ca52b31d3f867d9a14b2a3b9fcd4f21aa5fb0a3d.tar.bz2
weston-ca52b31d3f867d9a14b2a3b9fcd4f21aa5fb0a3d.zip
Remove Raspberry Pi backend and renderer
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 e8de35c922871bc5b15fbf0436efa233a6db8e41, 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 <pekka.paalanen@collabora.co.uk> Reviewed-by: Derek Foreman <derekf@osg.samsung.com> Acked-by: Bryce Harrington <bryce@osg.samsung.com> Acked-by: Jonas Ã…dahl <jadahl@gmail.com> Acked-by: Daniel Stone <daniels@collabora.com>
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 0 insertions, 2 deletions
diff --git a/README b/README
index 3fdfb37f..110a14bb 100644
--- a/README
+++ b/README
@@ -138,8 +138,6 @@ would be roughly like this:
- xwayland (depends on X11/xcb libs)
-- rpi-backend (depends on DispmanX, libudev, ...)
-
- fbdev-backend (depends on libudev...)
- rdp-backend (depends on freerdp)