Wayland (display server protocol)

Wayland

Screenshot of a Wayland demonstration
Original author(s)	Kristian Høgsberg
Developer(s)	freedesktop.org et al.
Initial release	0.85 / 9 February 2012 (2012-02-09)[1]
Stable release	1.9.0 / 21 September 2015 (2015-09-21)[2]
Preview release	1.9.92 / 2 February 2016 (2016-02-02)[3]
Development status	Active
Written in	C
Operating system	Linux
Size	c. 100 KB
Type	Windowing system Display server
License	MIT Expat License[4][5][6]
Website	wayland.freedesktop.org

Wayland is a computer protocol that specifies the communication between a display server (called Wayland compositor) and its clients, as well as a reference implementation of the protocol in the C programming language.^[7]

Wayland is developed by a group of volunteers led by Kristian Høgsberg as a free and open-source software community-driven project with the aim of replacing the X Window System with a modern, simpler windowing system in Linux and Unix-like operating systems.^[8] The project's source code is published under the terms of the MIT Expat permissive free software licence.^[4]

As part of its efforts, the Wayland project also develops a reference implementation of a Wayland compositor called Weston.

Overview

① The evdev module of the Linux kernel gets an event and sends it to the Wayland compositor.
② The Wayland compositor looks through its scenegraph to determine which window should receive the event. The scenegraph corresponds to what's on screen and the Wayland compositor understands the transformations that it may have applied to the elements in the scenegraph. Thus, the Wayland compositor can pick the right window and transform the screen coordinates to window local coordinates, by applying the inverse transformations. The types of transformation that can be applied to a window is only restricted to what the compositor can do, as long as it can compute the inverse transformation for the input events.
③ As in the X case, when the client receives the event, it updates the UI in response. But in the Wayland case, the rendering happens by the client via EGL, and the client just sends a request to the compositor to indicate the region that was updated.
④ The Wayland compositor collects damage requests from its clients and then re-composites the screen. The compositor can then directly issue an ioctl to schedule a pageflip with KMS.

In recent years, Linux desktop graphics has moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. DRI, DRM) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance".^[9]

Kristian Høgsberg could have added an extension to X as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ:^[10]

What’s different now is that a lot of infrastructure has moved from the X server into the kernel (memory management, command scheduling, mode setting) or libraries (cairo, pixman, freetype, fontconfig, pango, etc.), and there is very little left that has to happen in a central server process. ... [An X server has] a tremendous amount of functionality that you must support to claim to speak the X protocol, yet nobody will ever use this. ... This includes code tables, glyph rasterization and caching, XLFDs (seriously, XLFDs!), and the entire core rendering API that lets you draw stippled lines, polygons, wide arcs and many more state-of-the-1980s style graphics primitives. For many things we've been able to keep the X.org server modern by adding extension such as XRandR, XRender and COMPOSITE ... With Wayland we can move the X server and all its legacy technology to an optional code path. Getting to a point where the X server is a compatibility option instead of the core rendering system will take a while, but we'll never get there if [we] don’t plan for it.

Wayland consists of a protocol and a reference implementation named Weston. The project is also developing versions of GTK+ and Qt that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application.

Wayland does not currently provide network transparency, but it may in the future.^[11] It was attempted as a Google Summer of Code project in 2011, but was not successful.^[12] Adam Jackson has envisioned providing remote access to a Wayland application by either 'pixel-scraping' (like VNC) or getting it to send a "rendering command stream" across the network (as in RDP, SPICE or X11).^[13] As of early 2013, Høgsberg is experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor.^[14]

Software architecture

Protocol architecture

In the Wayland protocol architecture, a client and a compositor communicate through the Wayland protocol using the reference implementation libraries.

Wayland protocol follows a client–server model in which clients are the graphical applications requesting the display of pixel buffers on the screen, and the server (compositor) is the service provider controlling the display of these buffers.

The Wayland reference implementation has been designed as a two-layer protocol:^[15]

• A low-level layer or wire protocol that handles the inter-process communication between the two involved processes—​​client and compositor—​​and the marshalling of the data that they interchange. This layer is message-based and usually implemented using the kernel IPC services, specifically Unix domain sockets in the case of Linux and Unix-like operating systems.^[16]
• A high-level layer built upon it, that handles the information that client and compositor need to exchange to implement the basic features of a window system. This layer is implemented as "an asynchronous object-oriented protocol".^[17]

While the low-level layer was written manually in C language, the high-level layer is automatically generated from a description of the elements of the protocol stored in XML format.^[18] Every time the protocol description of this XML file changes, the C source code that implements such protocol can be regenerated to include the new changes, allowing a very flexible, extensible and error-proof protocol.

The reference implementation of Wayland protocol is split in two libraries: a library to be used by Wayland clients called libwayland-client and a library to be used by Wayland compositors called libwayland-server.^[19]

Protocol overview

The Wayland protocol is described as an "asynchronous object-oriented protocol." Object-oriented means that the services offered by the compositor are presented as a series of objects living on the same compositor. Each object implements an interface which has a name, a number of methods (called requests) as well as several associated events. Every request and event has zero or more arguments, each one with a name and a data type.^[17] The protocol is asynchronous in the sense that requests do not have to wait for synchronized replies or ACKs, avoiding round-trip delay time and achieving improved performance.

The Wayland clients can make a request (a method invocation) on some object if the object's interface supports that request. The client must also supply the required data for the arguments of such request. This is the way the clients request services from the compositor. The compositor in turn sends information back to the client by causing the object to emit events (probably with arguments too). These events can be emitted by the compositor as a response to a certain request, or asynchronously, subject to the occurrence of internal events (such as one from an input device) or state changes. The error conditions are also signaled as events by the compositor.^[17]

For a client to be able to make a request to an object, it first needs to tell the server the ID number it will use to identify that object.^[17] There are two types of objects in the compositor: global objects and non-global objects. Global objects are advertised by the compositor to the clients when they are created (and also when they are destroyed), while non-global objects are usually created by other objects that already exist as part of their functionality.^[20]

The interfaces and their requests and events are the core elements that define the Wayland protocol. Each version of the protocol includes a set of interfaces, along with their requests and events, which are expected to be in any Wayland compositor. Optionally, a Wayland compositor may define and implement its own interfaces that support new requests and events, thereby extending functionality beyond the core protocol.^[21] To facilitate changes to the protocol, each interface contains a "version number" attribute in addition to its name; this attribute allows for distinguishing variants of the same interface. Each Wayland compositor exposes not only what interfaces are available, but also the supported versions of those interfaces.^[22]

Wayland core interfaces

The interfaces of the current version of Wayland protocol are defined in the file protocol/wayland.xml of the Wayland source code.^[18] This is an XML file that lists the existing interfaces in the current version, along with their requests, events and other attributes. This set of interfaces is the minimum required to be implemented by any Wayland compositor.

Some of the most basic interfaces of the Wayland protocol are:^[21]

• wl_display – the core global object, a special object to encapsulate the Wayland protocol itself
• wl_registry – the global registry object, in which the compositor registers all the global objects that it wants to be available to all clients
• wl_compositor – an object that represents the compositor, and is in charge of combining the different surfaces into one output
• wl_surface – an object representing a rectangular area on the screen, defined by a location, size and pixel content
• wl_buffer – an object that, when attached to a wl_surface object, provides its displayable content
• wl_output – an object representing the displayable area of a screen
• wl_pointer, wl_keyboard, wl_touch – objects representing different input devices like pointers or keyboards
• wl_seat – an object representing a seat (a set of input/output devices) in multiseat configurations

A typical Wayland client session starts by opening a connection to the compositor using the wl_display object. This is a special local object that represents the connection and does not live within the server. By using its interface the client can request the wl_registry global object from the compositor, where all the global object names live, and bind those that the client is interested in. Usually the client binds at least a wl_compositor object from where it will request one or more wl_surface objects to show the application output on the display.^[20]

Wayland extension interfaces

A Wayland compositor can define and export its own additional interfaces.^[21] This feature is used to extend the protocol beyond the basic functionality provided by the core interfaces, and has become the standard way to implement Wayland protocol extensions. Certain compositors can choose to add custom interfaces to provide specialized or unique features. The Wayland reference compositor, Weston, used them to implement new experimental interfaces as a testbed for new concepts and ideas, some of which later became part of the core protocol (such as wl_subsurface interface added in Wayland 1.4^[23]).

Extension protocols to the core protocol

XDG-Shell protocol

XDG-Shell protocol (see freedesktop.org for XDG) is an extended way to manage surfaces under Wayland compositors (not only Weston). The traditional way to manipulate (maximize, minimize, fullscreen, etc.) surfaces is to use the wl_shell_*() functions, which are part of the core Wayland protocol and live in libwayland-client. An implementation of the xdg-shell protocol, on the contrary, is supposed to be provided by the Wayland compositor. So you will find the xdg-shell-client-protocol.h header in the Weston source tree. Each Wayland compositor is supposed to provide its own implementation.

As of June 2014, XDG-Shell protocol was not versioned and still prone to changes.

xdg_shell is a protocol aimed to substitute wl_shell in the long term, but will not be part of the Wayland core protocol. It starts as a non-stable API, aimed to be used as a development place at first, and once features are defined as required by several desktop shells, it can be finally made stable. It provides mainly two new interfaces: xdg_surface and xdg_popup. The xdg_surface interface implements a desktop-style window that can be moved, resized, maximized, etc.; it provides a request for creating child/parent relationship. The xdg_popup interface implements a desktop-style popup/menu; an xdg_popup is always transient for another surface, and also has implicit grab.^[24]

IVI-Shell protocol

IVI-Shell protocol is an extension protocol to the Wayland core protocol by the IVI-people.

WRandR

WRandR is an extension to Wayland intended to facilitate the ability to resize, rotate and reflect the root window of a screen.

Rendering model

Wayland compositor and its clients use EGL to draw directly into the framebuffer; X.Org Server with XWayland and Glamor.

The Wayland protocol does not include a rendering API.^{[25][26][27][28]} Instead, Wayland follows a direct rendering model, in which the client must render the window contents to a buffer shareable with the compositor.^[26] For that purpose, the client can choose to do all the rendering by itself, use a rendering library like Cairo or OpenGL, or rely on the rendering engine of high-level widget libraries with Wayland support, such as Qt or GTK+. The client can also optionally use other specialized libraries to perform specific tasks, such as Freetype for font rendering.

The resulting buffer with the rendered window contents are stored in a wl_buffer object. The internal type of this object is implementation dependant. The only requirement is that the content data must be shareable between the client and the compositor. If the client uses a software (CPU) renderer and the result is stored in the system memory, then client and compositor can use shared memory to implement the buffer communication without extra copies. The Wayland protocol already provides natively this kind of shared memory buffers through wl_shm and wl_shm_pool interfaces .^[21] The drawback of this method is that the compositor may need to do additional work (usually to copy the shared data to the GPU) to display it, which leads to slower graphics performance.

The most typical case is for the client to render directly into a video memory buffer using a hardware (GPU) accelerated API such as OpenGL or OpenGL ES. Client and compositor can share this GPU-space buffer using a special handler to reference it.^[29] This method allows the compositor to avoid additional copies of data to the GPU, resulting in faster graphics performance than using shm buffers, and therefore the preferred one. The compositor can further optimize the composition of the final scene to show on the display by using the same hardware acceleration API that the client.

When the rendering is done and the buffer shared, the Wayland client should instruct the compositor to present the rendered contents of the buffer on the display. For this purpose, the client binds the buffer object that stores the rendered contents to the surface object, and sends a "commit" request to the surface, transferring the effective control of the buffer to the compositor.^[15] Then, the client waits for the compositor to release the buffer (signaled by an event) if it wants to reuse the buffer to render another frame, or it can use another buffer to render the new frame and, when the rendering is finished, to bind this new buffer to the surface and commit its contents.^[26] The procedure used for rendering, including the number of buffers involved and their management, is entirely under the client control.^[26]

Comparison with other window systems

Differences between Wayland and X

There are several differences between Wayland and X in regards to performance, code maintainability, and security:^[30]

• Architecture: the composition manager is a separate, additional feature in X, while Wayland merges display server and compositor as a single function. Also, it incorporates some of the tasks of the window manager, which in X is a separate client-side process.^[31]
• Composition: compositing is optional in X, but mandatory in Wayland. Compositing in X is "active"; that is, the compositor must fetch all pixel data, which introduces latency. In Wayland, compositing is "passive", which means the compositor receives pixel data directly from clients.^[32]
• Rendering: the X server itself is able to perform rendering, although it can also be instructed to display a rendered window sent by a client. In contrast, Wayland does not expose any API for rendering, instead delegating to a client all such responsibilities (including the rendering of fonts, widgets, etc.). Window decorations can be rendered on the client side (e.g., by a graphics toolkit) or on the server side (by the compositor).^[33]
• Security: Wayland isolates the input and output of every window, achieving confidentiality, integrity and availability in both cases; X lacks these important security features.^[34] Also, with the vast majority of the code running in the client, less code needs to run with root privileges, improving security.^[35]
• Inter-process communication: the X server provides a basic communication method between X clients, later extended by ICCCM conventions. This X client-to-client communication is used by window managers and also to implement X sessions, selections and drag-and-drop, and other features. Wayland core protocol does not support communication between wayland clients at all, and the corresponding functionality (if needed) should be implemented by the desktop environments (like KDE or GNOME), or by a third party (for example, by using native IPC of the underlying operating system).
• Networking: The X Window System is an architecture that was designed at its core to run over a network. Wayland does not offer network transparency by itself; however, a compositor can implement any remote desktop protocol to achieve remote displaying. In addition, there is research into Wayland image streaming and compression that would provide remote frame buffer access similar to that of VNC.^[36]

Some of the differences can also be easily understood by comparing the architecture diagrams of both protocols.^[37]

Compatibility with X

A screenshot showing xwayland

XWayland is an X Server running as a Wayland client, thus capable of displaying native X11 client applications in a Wayland compositor environment.^[38] This is similar to the way XQuartz runs X applications in OS X’s native windowing system. The goal of XWayland is to facilitate the transition from X Window System to Wayland environments, providing a way to run unported applications in the meantime. XWayland was mainlined into X.Org Server version 1.16^[39]

Qt applications can switch between graphical back-ends like X and Wayland at load time with the -platform command-line option.^[40] In January 2011, Wayland support was moved into the Lighthouse branch of the upstream Qt repository.^[41] Qt Lighthouse is shipped in the Qt 4.8 release.^[42]

In December 2010, GTK+ added preliminary support for switching back-ends at run time, saying "interesting combinations are X11+Wayland or Quartz+X11".^[43][44] In January 2011, the GTK+ Wayland backend was updated to support the multiple-backends feature and moved to the gdk-wayland-backend branch of the upstream GTK+ Git repository.^[45] In April 2011, the gdk-wayland-backend branch was merged in the GTK+ master branch.

Wayland compositors

Typical elements of a window. Neither Wayland nor X11 specifies what software is responsible for rendering the window decoration. Weston requires that they are drawn by the client, but KWin will implement server-side decoration.^[33]

Display servers that implement the Wayland display server protocol are also called Wayland compositors because they additionally perform the task of a compositing window manager.

• Weston – the reference implementation of a Wayland compositor; Weston implements client-side decoration
• Lipstick – mobile graphical shell framework which implements Wayland compositor. It is used in Sailfish OS and Nemo Mobile.^[46]
• Enlightenment 0.20 (E20) will have full Wayland support.^[47]
• KWin had incomplete Wayland support in April 2013.^[48]
• Mutter maintains a separate branch for the integration of Wayland for GNOME 3.9 (in September 2013).^[49]
• Clayland is a simple example Wayland compositor using Clutter.

Weston

Weston is the reference implementation of a Wayland compositor. It is written in C and was initially published under GPLv2, but is currently published under the Historical Permission Notice and Disclaimer license. Weston is written for the Linux kernel API; that is, Weston only has official support for the Linux kernel due to dependence on certain features, such as Linux's kernel mode-setting, Graphics Execution Manager (GEM), and udev, which have not yet been implemented in other Unix-like operating systems.^[50] When running on the Linux kernel, handling of the input hardware relies on evdev, while the handling of buffers relies on Generic Buffer Management (GBM).

Weston is written for the Linux kernel; as of February 2013, a prototype port of Weston to FreeBSD was announced.^[51]

Weston relies on GEM to share application buffers between the compositor and applications. It contains a plugin system, external "shells" for WM/dock/etc, and Weston supports X clients. Clients are responsible for the drawing of their window borders and their decorations. For rendering, Weston can use OpenGL ES or software (pixman^[52]).^[53] The full OpenGL implementation is not used, because on most current systems, installing the full OpenGL libraries would also install GLX and other X Window System support libraries as dependencies.^[54]

Maynard is a graphical shell and has been written as a plugin for Weston, similar as the GNOME Shell has been written as a plugin to Mutter.^[55]

A remote access interface for Weston was proposed in October 2013 by a RealVNC employee.^[56]

libinput

libinput was created to consolidate the input stack across multiple Wayland compositors.

Libinput handles input devices for multiple Wayland compositors and also provides a generic X.Org Server input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via udev), device handling, input device event processing and abstraction.^[57][58]

Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI.^[59]

As GNOME/GTK+ and KDE Frameworks 5^[60] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput.^[61]

The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called libinput, for which support was first merged in Weston 1.5.^[62][63]

With version 1.16, the X.Org Server obtained support for the libinput library in form of a wrapper called xf86-input-libinput.^[64][65]

Wayland Security Module

Wayland Security Module is a proposition that resembles the Linux Security Module interface found in the Linux kernel.

Some applications (especially the ones related to accessibility) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events. Wayland developers are actively looking for feasible ways to handle privileged clients securely and then designing privileged interfaces for them.

Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine.^[66]

Wayland debugger

A debugger called wldbg was announced July 2015.^[67]

Adoption

As explained in the "Software architecture" section above, the Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. As of July 2014, these additional interfaces are actively being worked on. So, while the toolkits already fully support Wayland, the developers of the graphical shells are cooperating with the Wayland developers creating the necessary additional interfaces.

Linux distributions

In general, out of the box support for a full desktop running Wayland in major Linux distributions is still in early stages. However, many distributions are highly interested in eventually switching from X.org to Wayland.

• Fedora is planning for version 24 to change the login manager (GNOME Desktop Manager) to use Wayland by default when the graphics driver supports it.^[68] The desktop will still use X.org.
• Sailfish OS by Jolla use Wayland as standard, hence in several devices using it from Jolla. It is also used as standard when licensed Linux Sailfish OS is used with hardware from other vendors or when it is installed into Android devices by users themselves.^[69][70][71]

Toolkit support

Toolkits supporting Wayland include the following:

• Clutter has complete Wayland support.^[72]
• EFL has complete Wayland support, except for selection.^[73]
• GTK+ 3.10 has complete Wayland 1.2 support.^[74]
• Qt 5 has complete Wayland support.
• SDL support for Wayland debuts with the 2.0.2 release, but as experimental and disabled by default.^[75]
• GLFW 3.1 will have experimental unadvertised Wayland support.^[76]
• FreeGLUT has initial Wayland support^[77]

Desktop environments

Desktop environments supporting Wayland include the following:

• KDE support:
  • KWin: is in the process of becoming a Wayland compositor, but support is incomplete;^[78] support for OpenGL ES output was added in 2010,^[79] in version 4.7.^[80] In January 2013 KWin’s main developer Martin Grässlin started working for Blue Systems with one of the goals being a complete Wayland port.^[81] Experimental Wayland support is now working in current KWin 4.11.^[82]
  • KDE Frameworks 5: it is possible to run most applications built on top of Frameworks 5 under a Wayland compositor, without X11, as X11-dependent codepaths have become optional.^[78]
  • KDE Plasma 5: is based on Frameworks 5, but as e.g. interfaces between the workspace shell, the compositor (KWin) and the display server are not yet well-defined or implemented up-stream, support is incomplete.^[78]
  • Calligra Suite already has an unofficial but working port to Wayland.^[83]
• Glx-Dock has been ported to Wayland.^[84]
• The Hawaii desktop environment exclusively supports Wayland.
• GNOME: In March 2013 GNOME developers announced plans for a complete Wayland port within a year.^[85] GNOME 3.10 includes initial support that "will enable the project to fully adopt the next generation display and input technology in the future".^[86][87] The current roadmap targets GNOME 3.20 as the first version to be fully ported to Wayland.^[88][89]
• MATE: Wayland support is on MATE’s roadmap for “when MATE will become GTK+3 only”.^[90]

Other software

Other software supporting Wayland includes the following:

• Intelligent Input Bus is working on Wayland support, it could be ready for Fedora 22^[91]
• RealVNC published a Wayland developer preview in July 2014^[56][92][93]
• Maliit: Maliit, an input method framework, runs under Wayland.^[94][95][96]
• kmscon supports Wayland with wlterm^[97]
• Mesa: Mesa, to which AMD and Intel directly contribute to support their graphics processors, has Wayland support integrated.^[98] Within the Mesa projects, drivers for Qualcomm Snapdragon (freedreno)^[99][100] and Nvidia GPUs (nouveau)^[101][102] are being developed by Red Hat and community contributors.^[103][104]
• Eclipse was made to run on Wayland during a GSoC-Project in 2014.^[105]

Mobile and embedded hardware

Mobile and embedded hardware supporting Wayland includes the following:

• GENIVI Alliance: The GENIVI automotive industry consortium for in-vehicle infotainment (IVI) supports Wayland.^[106]
• Raspberry Pi: The Raspberry Pi Foundation in collaboration with Collabora released Maynard and work on improving performance and memory consumption, but do not expect to be able to replace X11 as the default display server until later in 2013^[107][108]
• Sailfish OS: Smartphones from Jolla use Wayland as standard. It is also used as standard when Linux Sailfish OS is used with hardware from other vendors or when it is installed into Android devices by users.^{[109][110][111]}
• Tizen: Tizen up to 2.x supports Wayland in in-vehicle infotainment (IVI) setups^[112] and from 3.0 onward defaults to Wayland.^[113]

History

Wayland uses direct rendering over EGL.

Kristian Høgsberg, a software engineer who works on the Linux graphics stack, started Wayland as a spare-time project in 2008 while working for Red Hat^[114] (he is now at Intel).^[115] His earlier work on X included AIGLX,^[116] which enabled hardware acceleration of compositing window managers, and DRI2.^{[117][118][119]} His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker."

Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name.^[120]

In October 2010, Wayland became a freedesktop.org project.^[121][122]

With the demo compositor and clients originally under the GPLv2 license and a LGPLv2 planned,^[123] the Wayland libraries (libwayland-server and libwayland-client) were released under the MIT License.^[124] Wayland works with all Mesa-compatible drivers with DRI2 support^[98] as well as Android drivers via the Hybris project.^{[125][126][127]}

On 4 October 2013, Nvidia released a beta version of their 331.13 driver which supports the EGL API.^[128] Although limited to X11, IT publications such as Phoronix and Golem.de noted that EGL support in the Nvidia driver could pave the way for future Wayland support.^[129][130] In March 2014, Nvidia announced a change in Wayland was "[throwing] a wrench into things" in their planned support for Wayland.^[131]

The developers of Wayland are largely present X.Org Server developers.^[132]

Releases

See also

• Mir (software)
• X Window System

References

External links

• Official website
• Wayland at Open Hub
• Wayland at FOSDEM 2012 by Kristian Høgsberg
• The way to Wayland: Preparing for life After X by Joe 'Zonker' Brockmeier, LWN, 17 November 2010
• Wayland – Beyond X by Richard Hillesley, The H, 13 February 2012
• The Wayland Situation: Facts About X vs. Wayland by Eric Griffith, Phoronix, 7 June 2013

Free and open-source software projects hosted by freedesktop.org OS components Avahi Compiz D-Bus DRI Enchant Kmscon luit nouveau PackageKit Plymouth PulseAudio systemd Wayland X.Org Server Glamor Xephyr Libraries AppStream cairo Fontconfig GStreamer Mesa 3D fprint HarfBuzz Pango Poppler Swfdec Video Acceleration API XCB Xft Frameworks CppUnit Galago GeoClue Open Collaboration Services Telepathy Meetings Create Project Portland Project