Wayland (display server protocol)

From Wikipedia, the free encyclopedia
  (Redirected from Wayland (display server))
Jump to: navigation, search
Wayland
Wayland Logo.svg
Wayland demo 2.png
Wayland demonstration
Original author(s) Kristian Høgsberg
Developer(s) freedesktop.org et al.
Initial release 0.85 / 9 February 2012; 2 years ago (2012-02-09)[1]
Stable release 1.6.0 / 19 September 2014; 2 days ago (2014-09-19)[2]
Development status Active
Written in C
Operating system Linux
Type
License MIT License
Website wayland.freedesktop.org

Wayland is a 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.[3] 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 to replace the X Window System with a modern, simpler windowing system in Linux and Unix-like operating systems.[4] The source code of the project is published under the MIT License.

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

Overview[edit]

① 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".[5]

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:[6]

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.[7] It was attempted as a Google Summer of Code project in 2011, but was not successful.[8] 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).[9] As of early 2013, Høgsberg is experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor.[10]

Software architecture[edit]

Protocol architecture[edit]

In 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 display pixel buffers on the screen, and the server (compositor) is the service provider controlling the display of these buffers.

Wayland reference implementation has been designed as a two-layer protocol:[11]

  • 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.[12]
  • 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".[13]

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.[14] 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.[15]

Protocol overview[edit]

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.[13] 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 certain request, or asynchronously, subject to the occurrence of internal events (as one from an input device) or state changes. The error conditions are also signaled as events by the compositor.[13]

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.[13] 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.[16]

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 can define and implement their own interfaces with their own requests and events, in order to extend its functionality beyond the core protocol.[17] To facilitate changes between versions of the protocol, interfaces contain a "version number" attribute in addition to its name; this attribute allows an interface to be treated differently from previous versions of itself with fewer or different requests and events. Each Wayland compositor exposes not only what interfaces are available but also their supported version, and objects implement a particular version of an interface.[18]

Wayland core interfaces[edit]

The interfaces of the current version of Wayland protocol are defined in the file protocol/wayland.xml of the Wayland source code.[14] 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 implement by any Wayland compositor.

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

  • wl_display – the core global object, a special object to encapsulate 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.[16]

Wayland extension interfaces[edit]

A Wayland compositor can define and export its own additional interfaces.[17] 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. Wayland reference compositor, Weston, used it 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[19]).

Rendering model[edit]

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

Wayland protocol does not include a rendering API.[20][21][22][23] Instead, Wayland follows a direct rendering model, in which the client must render itself the window contents to a buffer shareable with the compositor.[21] For that purpose, the client can choose 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.

Comparison with other window systems[edit]

Differences between Wayland and X[edit]

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

  • 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.[25]
  • 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.[26]
  • Rendering: the X server is able to render itself, although it can be instructed to display the rendered windows sent by clients. Wayland does not expose any API to render and delegates all the rendering responsibilities (including font rendering, widgets rendering, etc.) to the clients. Even the window decoration should be rendered in client side (by the graphic toolkits), although some compositors can offer server-side decorations.[27]
  • Security: Wayland isolates the input and output of every window, achieving confidentiality, integrity and availability in both cases; X lacks these important security features.[28] Also, with the vast majority of the code running in the client, less code needs to run with root privileges, improving security.[29]
  • 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.[30]

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

Compatibility with X[edit]

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.[32] 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[33]

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

In December 2010, GTK+ added preliminary support for switching back-ends at run time, saying "interesting combinations are X11+Wayland or Quartz+X11".[37][38] 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.[39] In April 2011, the gdk-wayland-backend branch was merged in the GTK+ master branch.

Wayland compositors[edit]

Typical elements of a window. Neither Wayland nor X11 specify which software has to do the drawing of the window decoration. Weston requires that they be drawn by the client, but KWin will implement server-side decoration.[27]

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[edit]

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 MIT license. Weston is written for the Linux kernel API, i.e. it is only officially supported to work with the Linux kernel due to dependence on certain features, such as KMS driver, Graphics Execution Manager (GEM), and udev, which have not been implemented yet in other Unix-like operating systems.[44] When running on 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 Wayland to FreeBSD was announced.[45]

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[46]).[47] 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.[48]

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.[49]

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

libinput[edit]

The Weston code to handle input devices (keyboards, pointers, touch screens, etc.) was split in its own separated library, called libinput.[51] The goal was to provide any Wayland compositor with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection, device handling, input device event processing and abstraction,[52] and it could also provide a generic X.Org input driver in the future. libinput support was first merged in Weston 1.5.[53]

XDG-Shell protocol[edit]

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.[54]

Wayland Security Module[edit]

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

As some applications (especially the ones related to accessibility) really DO require privileged capabilities and should work across the different Wayland compositors but applications under Wayland are generally unable to perform any sensitive task 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.[55]

Adoption[edit]

As explained in the above section "software architecture", the Wayland protocol is by choice kept basic and simple, so that additional protocols and interfaces do 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 have full Wayland support already, the developers of the graphical shells are cooperating with the Wayland developers in punching out the necessary additional interfaces:

Toolkits[edit]

As of October 2013:

  • Clutter has complete Wayland support.[56]
  • EFL has complete Wayland support, except for selection.[57]
  • GTK+ 3.10 (released 23 September 2013) has complete Wayland 1.2 support, including the client-side decorations, which is required by Weston.[58][59]
  • Qt 5 has complete Wayland support, including the client-side decorations, which is required by Weston but not KWin.
  • SDL support for Wayland debuts with the 2.0.2 release, but as experimental and disabled by default.[60]
  • GLFW 3.1 will have experimental unadvertised Wayland support.[61]

Desktop environments[edit]

  • KDE:
    • KWin: is in the process of becoming a Wayland compositor, but support is incomplete;[62] support for OpenGL ES output was added in 2010,[63] in version 4.7.[64] 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.[65] Experimental Wayland support is now working in current KWin 4.11.[66]
    • 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.[62]
    • 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.[62]
    • Calligra Suite already has an unofficial but working port to Wayland.[67]
  • Glx-Dock has been ported to Wayland.[68]
  • Enlightenment version E19: and Enlightenment Foundation Libraries version 1.10 include full Wayland support.[69][70]
  • The Hawaii desktop environment exclusively supports Wayland.
  • GNOME: In March 2013 GNOME developers announced plans for a complete Wayland port within a year.[71] GNOME 3.10 includes initial support that "will enable the project to fully adopt the next generation display and input technology in the future".[72][73] The current roadmap targets GNOME 3.12 as the first version to be fully ported to Wayland.[74]
  • Mate desktop: Wayland support is on Mate’s roadmap.[75] The targeted Mate version is 1.10.[76]

Other software[edit]

Mobile and embedded hardware[edit]

History[edit]

Wayland uses direct rendering over EGL.

Kristian Høgsberg (krh), a software engineer who works on the Linux graphics stack, started Wayland as a spare-time project in 2008, while working for Red Hat;[100] he is now at Intel.[101] His earlier work on X included AIGLX,[102] which enabled hardware acceleration of compositing window managers, and DRI2.[103][104][105] 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."

The name "Wayland" comes from the town of Wayland, Massachusetts. Høgsberg was driving through that town when the concepts behind Wayland "crystallized".[106]

In October 2010 Wayland became a freedesktop.org project.[107][108]

The Wayland libraries (libwayland-server and libwayland-client) were released under the MIT License, with the demo compositor and clients originally under the GPLv2 license. Moving the whole project to LGPLv2 was planned[109] but did not occur and the project is now switching fully to the MIT License.[110] Wayland works with all Mesa-compatible drivers with DRI2 support[84] as well as Android drivers via the Hybris project.[111][112][113] As of November 2010, Nvidia has no plans to support it in their proprietary drivers.[88][114][needs update]

On 4 October 2013 Nvidia released a beta version of their 331.13 driver which supports the EGL API.[115] 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.[116][117]

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

Releases[edit]

Major Wayland/Weston releases[119]
Version Date Wayland main features Weston main features
Old version, no longer supported: 0.85 9 Feb 2012[1] First release
Old version, no longer supported: 0.95 24 Jul 2012[120] Began API stabilization
Old version, no longer supported: 1.0 22 Oct 2012[121][122] Stable wayland-client API
Old version, no longer supported: 1.1 15 Apr 2013[123][124] Software rendering.[125] FBDEV, RDP backends
Old version, no longer supported: 1.2 12 Jul 2013[126][127] Stable wayland-server API Color management. Subsurfaces. Raspberry Pi backend
Old version, no longer supported: 1.3 11 Oct 2013[128] More pixel formats. Support for language bindings Android driver support via libhybris
Old version, no longer supported: 1.4 23 Jan 2014[19] New wl_subcompositor and wl_subsurface interfaces Multiple framebuffer formats. logind support for rootless Weston
Older version, yet still supported: 1.5 20 May 2014[53] libinput. Fullscreen shell.
Current stable version: 1.6 Sep 2014[2] libinput by default
Future release: 1.7 Sep 2014[2] xdg-shell interface
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

See also[edit]

References[edit]

  1. ^ a b Høgsberg, Kristian (9 February 2012). "[ANNOUNCE] Wayland and Weston 0.85.0 released". Wayland mailing list. Retrieved 8 June 2013. 
  2. ^ a b c Paalanen, Pekka (19 September 2014). "Wayland and Weston 1.6.0 released". FreeDesktop.org. 
  3. ^ "Wayland". "Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol." 
  4. ^ "Wayland". "Wayland is intended as a simpler replacement for X, easier to develop and maintain." 
  5. ^ Jonathan Corbet (5 November 2010). "Linux Plumbers Conference: Life after X (reporting a talk by Keith Packard)". LWN.net. 
  6. ^ "Wayland FAQ". Retrieved 17 February 2011. 
  7. ^ Kristian Høgsberg (9 November 2010). "Network transparency argument". 
    "Wayland isn't a remote rendering API like X, but that doesn't exclude network transparency. Clients render into a shared buffer and then have to tell the compositor (...) what they changed. The compositor can then send the new pixels in that region out over the network. The Wayland protocol is already violently asynchronous, so it should be able to handle a bit of network lag gracefully. Remote fullscreen video viewing or gaming isn't going to work well, [but] I don't know any other display system that handles that well and transparently."
  8. ^ Michael Larabel (18 August 2011). "Remote Wayland Server Project: Does It Work Yet?". 
  9. ^ Adam Jackson (ajax) (9 November 2010). "[Re:] Ubuntu moving towards Wayland". 
  10. ^ Stone, Daniel (1 February 2013). The real story behind Wayland and X. 42:00 minutes in.  Presentation at linux.conf.au 2013.
    "[W]e think it's going to better at remoting than X."
  11. ^ "The Hello Wayland Tutorial". Retrieved 25 July 2014. 
  12. ^ Høgsberg, Kristian. "Wayland Documentation 1.3 - Wire Format". FreeDesktop.org. Retrieved 25 July 2014. 
  13. ^ a b c d Høgsberg, Kristian. "Wayland Documentation 1.3 - Basic Principles". FreeDesktop.org. Retrieved 25 July 2014. 
  14. ^ a b Høgsberg, Kristian. "protocol/wayland.xml". FreeDesktop.org. Retrieved 25 July 2014. 
  15. ^ Høgsberg, Kristian. "Wayland Documentation 1.3 - Wayland Library". FreeDesktop.org. Retrieved 26 July 2014. 
  16. ^ a b Paalanen, Pekka. "Wayland protocol design: object lifespan". Retrieved 4 September 2014. 
  17. ^ a b c Høgsberg, Kristian. "Wayland Documentation 1.3 - Interfaces". FreeDesktop.org. Retrieved 31 July 2014. 
  18. ^ Høgsberg, Kristian. "Wayland Documentation 1.3 - Versioning". FreeDesktop.org. Retrieved 31 July 2014. 
  19. ^ a b Høgsberg, Kristian (24 January 2014). "Wayland and Weston 1.4 is out". Wayland mailing list. 
  20. ^ Høgsberg, Kristian. "Wayland". Retrieved 5 September 2014.  "No rendering API, all direct rendering"
  21. ^ a b Høgsberg, Kristian. "Wayland Documentation 1.3 - Wayland Rendering". FreeDesktop.org. Wayland project. Retrieved 4 September 2014. 
  22. ^ "Wayland FAQ". Wayland project. Wayland project. Retrieved 4 September 2014.  "Wayland doesn't render on behalf of the clients, it expects the clients to use whatever means they prefer to render into a shareable buffer."
  23. ^ Barnes, Jesse. "Introduction to Wayland". Intel Open Source Technology Center.  "Does not include a rendering API – Clients use what they want and send buffer handles to the server"
  24. ^ "The Wayland Situation: Facts About X vs. Wayland". Phoronix.com. 7 June 2013. p. 2. Retrieved 2013-07-18. 
  25. ^ "LFCS 2012: X and Wayland". LWN.net. 11 April 2012. Retrieved 19 March 2014. 
  26. ^ "Wayland/X Compositor Architecture By Example: Enlightenment DR19". Retrieved 4 July 2014. 
  27. ^ a b Gräßlin, Martin (7 February 2013). "Client Side Window Decorations and Wayland". Retrieved 26 February 2014. 
  28. ^ Peres, Martin. "Wayland Compositors - Why and How to Handle Privileged Clients!". Retrieved 26 February 2014. 
  29. ^ "XDC2012: Graphics stack security". LWN.net. Retrieved 2013-07-18. 
  30. ^ Stone, Daniel (28 January 2013). "The real story behind Wayland and X linux.conf.au". 
  31. ^ "Wayland architecture". freedesktop.org. Retrieved 2013-07-18. 
  32. ^ "X Clients under Wayland (XWayland)". Wayland project. Retrieved 18 July 2014. 
  33. ^ "ANNOUNCE: xorg-server 1.16.0". freedesktop.org. 2014-07-17. 
  34. ^ "Getting started with Lighthouse". Retrieved 17 December 2010. 
  35. ^ Kristian Høgsberg (25 January 2011). "Add wayland lighthouse plugin". 
  36. ^ Nokia (15 December 2011). "Qt Lighthouse git-repository". 
  37. ^ Michael Larabel (22 December 2010). "GTK+3 Now Uses X Input 2 By Default, New Back-End Caps". 
  38. ^ Matthias Clasen (21 December 2010). "GTK+ 2.91.7 released". 
  39. ^ Kristian Høgsberg (3 January 2011). "Multiple backends for GTK+". 
  40. ^ "Jolla: Sailfish OS, Qt, and open source". LWN. 31 July 2013. 
  41. ^ e-releasemanager (18 August 2013). "A Double Dose Of The W |". E19releasemanager.wordpress.com. Retrieved 2013-08-23. 
  42. ^ Grässlin, Martin. "The History on Wayland Support inside KWin". Martin’s Blog. Retrieved 2013-07-15. 
  43. ^ "Mutter-wayland tarballs". 
  44. ^ "README file from the Wayland source code repository". freedesktop.org. 
  45. ^ Larabel, Michael (16 February 2013). "Wayland Begins Porting Process To FreeBSD". Phoronix. Retrieved 14 July 2013. 
  46. ^ http://www.pixman.org/
  47. ^ Stone, Daniel (2013-02-01). The real story behind Wayland and X. 38:46 minutes in.  Presentation at linux.conf.au 2013.
    "It doesn't require OpenGL. Nothing in Wayland requires OpenGL."
  48. ^ Kristian Høgsberg (9 December 2010). "Blender3D & cursor clamping.". 
  49. ^ "Maynard announcement". 2014-04-16. Retrieved 2014-04-16. 
  50. ^ a b "[RFC weston] remote access interface module". freedesktop.org. 2013-10-18. 
  51. ^ Ådahl, Jonas (12 Nov 2013). "[RFC] Common input device library". Wayland mailing list. 
  52. ^ "libinput". Freedesktop.org. Retrieved 21 May 2014. 
  53. ^ a b Høgsberg, Kristian (20 May 2014). "Wayland and Weston 1.5.0 is released". Wayland mailing list. 
  54. ^ "xdg_shell: Adding a new shell protocol". freedesktop.org. 2013-12-03. Retrieved 2014-06-14. 
  55. ^ "Security in Wayland-based desktop environments: Privileged clients, authorization, authentication and sandboxing!". X.Org Foundation. 2014-10-08. 
  56. ^ "Clutter on Wayland". Retrieved 28 March 2012. 
  57. ^ "Wayland – Enlightenment". Retrieved 6 March 2013. 
  58. ^ "GTK+ 3.10 release mail". 23 September 2013. Retrieved 2013-09-24. 
  59. ^ "Documentation of the Wayland support in GTK+". 3 September 2013. 
  60. ^ Lantinga, Sam (8 March 2014). "SDL 2.0.2 RELEASED!". SDL Project. Retrieved 18 March 2014. 
  61. ^ Berglund, Camilla (8 April 2014). "Implementation for Wayland · Issue #106 · glfw/glfw · GitHub". Retrieved 14 Aug 2014. 
  62. ^ a b c "Plasma’s Road to Wayland". 2014-07-25. 
  63. ^ Grässlin, Martin (28 November 2010). "KWin runs on OpenGL ES". "It does not only help, it is a must have to start working for Wayland. So to say it’s the first part of the KWin port to Wayland" 
  64. ^ Grässlin, Martin (19 January 2011). "On the Road to Modern OpenGL (ES)". Retrieved 2013-07-31. 
  65. ^ Grässlin, Martin. "KWin Hacking++". Retrieved 2013-04-08. 
  66. ^ Larabel, Michael (14 June 2013). "KDE 4.11 Beta Released, Works On Wayland". Phoronix. Retrieved 16 June 2013. 
  67. ^ "ANNOUNCE: New Wayland live CD". Lists.freedesktop.org. 2014-03-21. Retrieved 2014-07-08. 
  68. ^ "Glx-Dock/Cairo-Dock Has Been Ported To Wayland". 2014-06-21. 
  69. ^ "Enlightenment and EFL backing Wayland". Enlightenment.org. 14 March 2013. Retrieved 2013-07-15. 
  70. ^ "Enlightenment as Standalone Wayland Compositor". 1 February 2014. Retrieved 2014-02-16. 
  71. ^ Larabel, Michael (13 March 2013). "GNOME Will Move Full-Speed With Wayland Support". Phoronix. Retrieved 8 Apr 2013. 
  72. ^ "GNOME 3.10 Has Been Officially Released". Phoronix. 25 September 2013. Retrieved 2013-10-08. 
  73. ^ "3.10 Released!". GNOME. 25 September 2013. Retrieved 2013-10-08. 
  74. ^ "GNOME Wayland Initiative". GNOME Project. Retrieved 18 March 2014. 
  75. ^ "MATE Mythbusting | LINUX Unplugged 26". Jupiter Broadcasting. Retrieved 2014-07-08. 
  76. ^ "Split MATE 1.8 roadmap". Ml.mate-desktop.org. Retrieved 2014-07-08. 
  77. ^ "Wayland in Fedora Update | Christian Schaller". Blogs.gnome.org. 2014-07-03. Retrieved 2014-07-08. 
  78. ^ "VNC® Wayland Developer Preview". 2014-07-08. 
  79. ^ "RealVNC Wayland developer preview email". freedesktop.org. 2014-07-09. 
  80. ^ "Maliit Status Update". Posterous. 2 April 2013. Archived from the original on 2013-05-17. Retrieved 2013-10-14. 
  81. ^ "More Maliit Keyboard Improvements: QtQuick2". Murray's Blog. 2 April 2013. Retrieved 2013-10-14. 
  82. ^ "Maliit under Wayland". Retrieved 2013-09-14. 
  83. ^ "wlterm". Freedesktop.org. Retrieved 2014-07-08. 
  84. ^ a b Richard Hillesley (13 February 2012). "Wayland – Beyond X". The H Open. Heise Media UK. p. 3. 
  85. ^ "Mesa/Gallium3D Gets Its First ARM SoC GPU Driver". Phoronix. 12 March 2013. Retrieved 30 July 2013. 
  86. ^ Rob Clark (30 July 2013). "freedreno update: drm/kms and ifc6410". Blogspot. Retrieved 30 July 2013. 
  87. ^ "Nouveau Merged". Phoronix. 20 December 2006. Retrieved 2013-07-30. 
  88. ^ a b Michael Larabel (8 November 2010). "NVIDIA Says It Has No Plans To Support Wayland". Phoronix. 
  89. ^ "Red Hat Picks Up Another Graphics Driver Developer". Phoronix. 15 February 2013. Retrieved 2013-07-30. 
  90. ^ "Red Hat Talks About Nouveau, Open-Source Drivers". Phoronix. 11 May 2010. Retrieved 2013-07-30. 
  91. ^ "Eclipse now runs on Wayland". 2014-08-18. 
  92. ^ "Wayland Backend DRM | IVI Layer Management". GENIVI Alliance. Retrieved 2013-07-15. 
  93. ^ "IVI/IVI Setup". Tizen Wiki. Retrieved 2013-04-08. 
  94. ^ "[IVI] Tizen IVI 3.0-M1 released". Tizen.org. Retrieved 2013-07-15. 
  95. ^ "Raspberry Pi Case Study". Collabora. Retrieved 2013-08-09. 
  96. ^ "Wayland preview". Raspberry Pi. Retrieved 2013-08-09. 
  97. ^ "The First Jolla Smartphone Runs With Wayland". LinuxG.net. 14 July 2013. Retrieved 2013-10-08. 
  98. ^ "sailfishos main components diagram". 
  99. ^ "our first Jolla will ship with wayland, yes". 
  100. ^ Høgsberg, Kristian. "Wayland – A New Display Server for Linux". Linux Plumbers Conference, 2009.  (Video available here [1])
  101. ^ Høgsberg, Kristian. "EGL and GLES1/2 on Linux". Linux Plumbers Conference, 2010. 
  102. ^ "Interview: Kristian Høgsberg". FOSDEM 2007. 6 February 2007. 
  103. ^ Høgsberg, Kristian (8 September 2008). "DRI2 Protocol Spec Draft". 
  104. ^ Høgsberg, Kristian (31 March 2008). "DRI2 Direct Rendering". 
  105. ^ "An Experimental GNOME Shell Running On Wayland". Retrieved 6 Apr 2012. "Founder Kristian Høgsberg responsible for key X improvement of the past few years: DRI2...." 
  106. ^ Evan Jenkins (March 2011). "The Linux graphics stack from X to Wayland". Ars Technica. 
  107. ^ "Wayland Becomes A FreeDesktop.org Project". Phoronix. 29 October 2010. Retrieved 2013-07-31. 
  108. ^ Kristian Høgsberg (29 October 2010). "Moving to freedesktop.org". Retrieved 2013-07-31. 
  109. ^ Larabel, Michael (22 November 2010). "Wayland License Changing To LGPLv2". Phoronix. Retrieved 21 September 2011. 
  110. ^ Larabel, Michael (20 September 2011). "Wayland Reference Code Being Re-Licensed". Phoronix. Retrieved 21 September 2011. 
  111. ^ Carsten Munk (11 April 2013). "Wayland utilizing Android GPU drivers on glibc based systems, Part 1". Mer Project. Retrieved 2013-07-03. 
  112. ^ Munk, Carsten (8 June 2013). "Wayland utilizing Android GPU drivers on glibc based systems, Part 2". Mer Project. Retrieved 2013-07-03. 
  113. ^ "Jolla Brings Wayland Atop Android GPU Drivers". Phoronix. 11 April 2013. Retrieved 2013-07-03. 
  114. ^ Aaron Plattner, nvidia's primary Linux developer (7 November 2010). "nvidia and the wayland display server". "We have no plans to support Wayland." 
  115. ^ "Nvidia drivers 331.13 beta". 4 October 2013. Retrieved 2013-10-05. "Added support for the EGL API on 32-bit platforms. Currently, the supported client APIs are OpenGL ES 1.1, 2.0 and 3.0, and the only supported window system backend is X11." 
  116. ^ "NVIDIA Releases Major Linux Driver With New Features, EGL". Phoronix. Retrieved 5 October 2013. 
  117. ^ "Unterstützt Nvidia Wayland und Mir?". Golem.de (in German) (Klass & Ihlenfeld Verlag GmbH). Retrieved 5 October 2013. 
  118. ^ Daniel Stone (March 2013). "The real story behind Wayland and X linux.conf.au". Ars Technica. 
  119. ^ "Wayland". Wayland.freedesktop.org. Retrieved 2013-07-15. 
  120. ^ Høgsberg, Kristian (24 July 2012). "Wayland and Weston 0.95.0 released". Wayland mailing list. Retrieved 14 July 2013. 
  121. ^ Høgsberg, Kristian (22 October 2012). "Wayland and Weston 1.0". Wayland mailing list. Retrieved 14 July 2013. 
  122. ^ Scherschel, Fabian (23 October 2012). "Wayland's 1.0 milestone fixes graphics protocol". The H - Open. Heinz Heise. Retrieved 14 July 2013. 
  123. ^ Larabel, Michael (16 April 2013). "Wayland 1.1 Officially Released With Weston 1.1". Phoronix. Retrieved 14 July 2013. 
  124. ^ Høgsberg, Kristian (15 April 2013). "1.1 Released". Wayland mailing list. Retrieved 18 July 2013. 
  125. ^ Larabel, Michael (6 January 2013). "A Software-Based Pixman Renderer For Wayland's Weston". Phoronix. Retrieved 14 July 2013. 
  126. ^ Larabel, Michael (13 July 2013). "Wayland 1.2.0 Released, Joined By Weston Compositor". Phoronix. Retrieved 14 July 2013. 
  127. ^ Høgsberg, Kristian (12 July 2013). "Wayland and Weston 1.2.0 released". Wayland mailing list. Retrieved 18 July 2013. 
  128. ^ Høgsberg, Kristian (11 October 2013). "Wayland and Weston 1.3 release notes". Wayland mailing list. 

External links[edit]