X.Org Server

X.Org Server
X.Org Server logo
Developer(s) X.Org Foundation
Initial release 6 April 2004 (2004-04-06)[1]
Stable release
1.19.3 / 15 March 2017 (2017-03-15)[2]
Repository http://cgit.freedesktop.org/xorg/xserver, git://anongit.freedesktop.org/git/xorg/xserver, git://anongit.freedesktop.org/xorg/xserver
Written in C
Operating system Cross-platform
Size 3.7 MiB[3]
Available in English
Type Display server
License MIT License
Website www.x.org

X.Org Server is the free and open source implementation of the display server for the X Window System stewarded by the X.Org Foundation.

Implementations of the client side of the protocol are available e.g. in the form of Xlib and XCB.

The services with which the X.Org Foundation supports X Server include the packaging of the releases; certification (for a fee); evaluation of improvements to the code; developing the web site, and handling the distribution of monetary donations. The releases are coded, documented, and packaged by global developers.

Software architecture

The X.Org Server implements the server side of the X Window System core protocol and extensions to it, e.g. RandR.[4]

Version 1.16.0 integrates support for systemd-based launching and management which improved boot performance and reliability.[5]

Device Independent X (DIX)

The Device Independent X (DIX) is the part of the X.Org Server that interacts with clients and implements software rendering. Basically everything in the server except for the hw/ directory. The main loop and the event delivery are part of the DIX.[6]

An X server has a tremendous amount of functionality that must be implemented to support the X core protocol. This includes code tables, glyph rasterization and caching, XLFDs, and the entire core rendering API that draws stippled lines, polygons, wide arcs and many more state-of-the-1980s style graphics primitives.

Device Dependent X (DDX)

The Device Dependent X (DDX) is the part of the x-server that interacts with the hardware. In the X.Org Server source code, each directory under "hw" corresponds to one DDX. Hardware comprises graphics cards as well as mouse and keyboards. Each driver is hardware specific and implemented as a separate loadable module.

2D graphics driver

For historical reasons the X.Org Server still contains graphics device drivers supporting some form of 2D rendering acceleration. In ancient times, the mode-setting was done by some x-server graphics device drivers specific to some video controller/graphics card. To this mode-setting functionality, additional support for 2D acceleration was added when such became available with various GPUs. The mode-setting functionality was moved into the DRM and is being exposed through an DRM mode-setting interface, the new approach being called "kernel mode-setting" (KMS). But the 2D rendering acceleration remained.

In Debian the 2D graphics drivers for the X.Org Server are packaged individually and called xserver-xorg-video-*.[7] After installation the 2D graphics driver-file is found under /usr/lib/xorg/modules/drivers/. The package xserver-xorg-video-nouveau installs nouveau_drv.so with a size of 215 KiB, the proprietary Nvidia GeForce driver installs a 8 MiB-sized file called nvidia_drv.so and Radeon Software installs fglrx_drv.so with a size of about 25MiB.

The available free and open-source graphics device drivers are being developed inside of the Mesa 3D-project. While these can be recompiled as required, the development of the proprietary DDX 2D graphics drivers is greatly eased when the X.Org Server keeps a stable API/ABI across multiple of its versions.

With version 1.17 a generic method for mode-setting was mainlined: xf86-video-modesetting, the Debian-package being called xserver-xorg-video-modesetting.

On April 7, 2016 AMD employee Michel Dänzer released xf86-video-ati version 7.7.0[8] and xf86-video-amdgpu version 1.1.0,[9] the later including support for their Polaris microarchitecture.

Acceleration architectures

There are (at least) XAA, EXA, UXA and SNA.

Glamor
A high-level architecture overview, showing Glamor's role

Glamor is a generic, i.e. hardware independent, 2D acceleration driver for the X server that translates the X render primitives to OpenGL operations, taking advantage of any existing 3D OpenGL drivers (proprietary or otherwise).[10] In this way, it is functionally similar to Quartz Extreme and QuartzGL (2D performance acceleration) for Apple Quartz Compositor.

The ultimate goal of GLAMOR is to obsolete and replace all the DDX 2D graphics device drivers and acceleration architectures, thereby avoiding the need to write X 2D specific drivers for every supported graphic chipset.[11][12][13] Glamor requires a 3D driver with support for shaders.[14]

Glamor performance tuning was accepted for Google Summer of Code 2014.[15] Glamor supports Xephyr and DRI3,[16] and can boost some operations by 700–800%.[17] Since its mainlining into version 1.16 of the X.Org Server, development on Glamor was continued and patches for the 1.17 release were published.[18]

Input stack

Under Debian, drivers related to input are found under /usr/lib/xorg/modules/input/. Such drivers are named e.g. evdev_drv.so, mouse_drv.so, synaptics_drv.so or wacom_drv.so.

With version 1.16, the X.Org Server obtained support for the libinput library in form of a wrapper called xf86-input-libinput.[19] At the XDC 2015 in Toronto, libratbag was introduced as a generic library to support configurable mice.[20][21] xserver-xorg-input-joystick is the input module for the X.Org server to handle classic joysticks and gamepads, which is not meant for playing games under X, but to control the cursor with a joystick or gamepad.[22][23]

Other DDX components

XWayland
XWayland is a series of patches over the X.Org server codebase that implements an X server running upon the Wayland protocol. The patches are developed and maintained by the Wayland developers for compatibility with X11 applications during the transition to Wayland,[24] and was mainlined in version 1.16 of the X.Org Server in 2014.[5] When you want to run an X application from within Weston, it spins up XWayland to service the request.[25]
XQuartz
XQuartz is a series of patches from Apple Inc. to integrate support for the X11 protocol into their Quartz Compositor, in a similar way to how XWayland integrates X11 into Wayland compositors.
Xspice
There is a device driver for the X.Org Server called Xspice. It supports the QXL framebuffer device and includes a wrapper script[26] which makes it possible to launch an X.Org Server whose display is exported via the SPICE protocol. This enables use of SPICE in a remote desktop environment, without requiring KVM virtualization.
Xephyr
Xephyr is an X-on-X implementation. Since version 1.16.0, Xephyr serves as the primary development environment for the new 2D acceleration subsystem (Glamor), permitting rapid development and testing on a single machine.[5]

IPC

The X.Org Server, and any x-client, each run as distinct processes. On Unix/Linux, a process knows nothing about any other processes. For it to communicate with another process, it is completely and utterly reliant on the kernel to moderate the communication via available inter-process communication (IPC) mechanisms. Unix domain sockets are used to communicate with processes running on the same machine. Special socket function calls are part of the System Call Interface. Although Internet domain sockets can be used locally, Unix domain sockets are more efficient, since they do not have the protocol overhead (checksums, byte orders, etc.).

X.Org Server does not use D-Bus.

Sockets is the most common interprocess communication (IPC) method between the processes of the X server and its various X clients. It provides the Application Programming Interface (API) for communication in the TCP/IP domain and also locally only in the UNIX domain. There are several other APIs described in the X Transport Interface, for instance TLI (Transport Layer Interface). Other options for IPC between for the X client-server, require X Window system extensions, for instance the MIT Shared Memory Extension (MIT-SHM).

Multiseat configuration

Multi-seat refers to an assembly of a single computer with multiple "seats", allowing multiple users to sit down at the computer, log in, and use the computer at the same time independently. The computer has multiple keyboards, mice, and monitors attached to each, each "seat" having one keyboard, one mouse and one monitor assigned to it. A "seat" consists of all hardware devices assigned to a specific workplace. It consists of at least one graphics device (graphics card or just an output and the attached monitor) and a keyboard and a mouse. It can also include video cameras, sound cards and more.

Due to limitation of the VT system in the Linux kernel and of the X core protocol (in particularly how X defines the relation between the root window and an output of the graphics card), multi-seat does not work out-of-the-box for the usual Linux distribution but necessitates a special configuration.

There are these methods to configure a multi-seat assembly:

The utilized command-line options of the xorg-server are:

Only the user on the first monitor has the use of vt consoles and can use Ctrl+Alt+Fx to select them. The other users have a GDM login screen and can use xorg-server normally, but have no vt's.

Even though a single user can utilize multiple monitors connected to the different ports of a single graphics card (cf. RandR), the method which is based on multiple instances of the xorg-server seems to require multiple PCI graphics cards.

It is possible to configure multi-seat employing only one graphics card, but due to limitations of the X protocol this necessitates the usage of X Display Manager Control Protocol XDMCP.[27]

There is also Xdmx (Distributed Multihead X).

Adoption

Unix and Linux
The X.Org Server runs on many free-software Unix-like operating systems, including being adopted for use by most Linux distributions and BSD variants. It is also the X server for the Solaris operating system. X.Org is also available in the repositories of Minix 3
Microsoft Windows
Cygwin/X, Cygwin's implementation of the X server for Microsoft Windows, uses the X.Org Server, as do VcXsrv[28] (Visual C++ X-server[29]) and Xming. SSH clients such as PuTTY allow launching of X applications through X11 forwarding on the condition that it is enabled on both the server and client.
OS X
OS X versions prior to Mac OS X Leopard (10.5) shipped with an XFree86-based server, but 10.5's X server adopted the X.Org codebase.[30] Starting with OS X Mountain Lion, (10.7) X11 is not bundled in OS X; instead, it has to be installed from, for example, the open source XQuartz project.[31] As of version 2.7.4, X11.app/XQuartz does not expose support for high-resolution Retina displays to X11 apps, which run in pixel-doubled mode on high-resolution displays.

History

A display server, such as X.Org Server, implements the windowing system and serves its clients.

The modern X.Org Foundation came into being in 2004 when the body that oversaw X standards and published the official reference implementation joined forces with former XFree86 developers. X11R6.7.0, the first version of the X.Org Server, was forked from XFree86 4.4 RC2.[1] The immediate reason for the fork was a disagreement with the new license for the final release version of XFree86 4.4, but several disagreements among the contributors surfaced prior to the split. Many of the previous XFree86 developers have joined the X.Org Server project.

In 2005, a great effort was put in the modularization of the X.Org server source code,[32] resulting in a dual release by the end of the year. The X11R7.0.0 release added a new modular build system based on the GNU Autotools, while X11R6.9.0 kept the old imake build system, both releases sharing the same codebase. Since then the X11R6.9 branch is maintained frozen and all the ongoing development is done to the modular branch. The new build system also brought the use of dlloader standard dynamic linker to load plugins and drivers, deprecating the old own method. As a consequence of the modularization, the X11 binaries were moving out of their own /usr/X11R6 subdirectory tree and into the global /usr tree on many Unix systems.

In June 2006, another effort was done to move the X.Org server source codebase from CVS to git.[33] Both efforts had the long-term goal of bringing new developers to the project. In the words of Alan Coopersmith:[34]

In the 7.1 release, the KDrive framework (a small implementation of X written by Keith Packard, which was not based on XFree86 that X.Org developers used as a testing ground for new ideas, such as EXA) was integrated into the main codebase of X.Org server.

In 2008, the new DRI2, based on the kernel mode-setting (KMS) driver, replaced DRI. This change also set a major milestone in the X.Org server architecture, as the drivers were moved out from the server and user space (UMS) to the kernel space.

In 2013, the initial versions of DRI3 and Present extensions were written and coded by Keith Packard to provide a faster and tearing-free 2D rendering. By the end of the year the implementation of GLX was rewritten by Adam Jackson at Red Hat.[35]

Releases

Version Date X11 Release Main features
Old version, no longer supported: 1.0 21 December 2005[36] X11R7.0 (1.0.1) Initial modularized X server, EXA architecture
Old version, no longer supported: 1.1 22 May 2006[37] X11R7.1 (1.1.0) KDrive integration, AIGLX support[38]
Old version, no longer supported: 1.2 22 January 2007[39] X11R7.2 (1.2.0) Autoconfiguration, enhanced support for GL-based compositing managers[40]
Old version, no longer supported: 1.3 19 April 2007[41] RandR 1.2[42]
Old version, no longer supported: 1.4 6 September 2007[43] X11R7.3 (1.4.0) Input hotplugging support[43][44]
Old version, no longer supported: 1.5 3 September 2008[45] X11R7.4 (1.5.1) MPX[46]
Old version, no longer supported: 1.6 25 February 2009[47] RandR 1.3, DRI2, XInput 1.5[48]
Old version, no longer supported: 1.7 1 October 2009[49] X11R7.5 (1.7.1) XInput 2.0, multi-pointer X[50][51]
Old version, no longer supported: 1.8 2 April 2010[52] xorg.conf.d, udev input handling[53]
Old version, no longer supported: 1.9 20 August 2010[54] X11R7.6 (1.9.3)
Old version, no longer supported: 1.10 25 February 2011[55] X Synchronization Fences[56]
Old version, no longer supported: 1.11 26 August 2011[57]
Old version, no longer supported: 1.12 4 March 2012[58] X11R7.7 (1.12.2) XInput 2.2 (including multi-touch support)[59]
Old version, no longer supported: 1.13 5 September 2012[60] New DDX driver API, DRI2 offload, RandR 1.4, OpenGL 3.x+ contexts, removing XAA[61]
Old version, no longer supported: 1.14 5 March 2013[62] XInput 2.3[63]
Old version, no longer supported: 1.15 27 December 2013[64] DRI3 and Present extensions[65][66]
Older version, yet still supported: 1.16 17 July 2014[67] XWayland DDX, GLAMOR acceleration, non-PCI devices support, systemd-logind support (rootless X),[67][68] obtained support for the libinput library in form of a wrapper called xf86-input-libinput[69][70]
Older version, yet still supported: 1.17 4 February 2015[71] Generic DRM/KMS driver xf86-video-modesetting,[72][73] added support for DRI2 with GLAMOR
Older version, yet still supported: 1.18 9 November 2015[74] RandR 1.5
Current stable version: 1.19 15 November 2016[75] Threaded Input, PRIME synchronization, XWayland pointer confinement and warping, Windows DRI extension support[76]
Future release: 1.20 TBA Meson build system
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

See also

References

  1. 1 2 "X.Org Foundation releases X Window System X11R6.7". Linux Weekly News. 7 April 2004. Retrieved 2012-04-04.
  2. ↑ Jackson, Adam (15 March 2017). "[ANNOUNCE] xorg-server 1.19.3". xorg-announce (Mailing list).
  3. ↑ "Debian X.Org Server Package in sid".
  4. ↑ "git: xorg-server, RandR".
  5. 1 2 3 "ANNOUNCE: xorg-server 1.16.0". freedesktop.org. 17 July 2014.
  6. ↑ "X.Org Server Glossary".
  7. ↑ "xserver-xorg-video-nouveau in Debian repositories".
  8. ↑ "[ANNOUNCE] xf86-video-ati 7.7.0". 2016-04-07.
  9. ↑ "[ANNOUNCE] xf86-video-amdgpu 1.1.0". 2016-04-07.
  10. ↑ "What is Glamor?". FreeDesktop.org. Retrieved 10 February 2014.
  11. ↑ Anholt, Eric. "Building 2D rendering acceleration with OpenGL". linux.conf.au. Retrieved 10 February 2014.
  12. ↑ Packard, Keith. "Brief Glamor Hacks". Retrieved 7 March 2014.
  13. ↑ "Adam Jackson - GLX rewrite". 24 September 2013. Retrieved 2014-03-23.
  14. ↑ "Radeon Feature Matrix". freedesktop.org.
  15. ↑ "Glamor Performance Tuning".
  16. ↑ "GLAMOR Xephyr & DRI3 Support Called For Pulling". Phoronix. 5 March 2014.
  17. ↑ "GLAMOR Patch Bomb Can Boost Some Operations By 700~800%". Phoronix. 13 March 2014.
  18. ↑ "glamor changes for 1.17". 17 July 2014.
  19. ↑ "libinput - a common input stack for Wayland compositors and X.Org drivers".
  20. ↑ "Introduction of libratbag".
  21. ↑ "How to debug a broken input device?".
  22. ↑ "XDC2012: xorg-input-joystick" (PDF) (pdf).
  23. ↑ "Debian package "xserver-xorg-input-joystick"".
  24. ↑ "X Clients under Wayland (XWayland)". Wayland Project. Retrieved 10 February 2014.
  25. ↑ "Wayland". Arch Linux Project. Retrieved 2016-05-09.
  26. ↑ "XSpice README". Cgit.freedesktop.org. Retrieved 2013-10-25.
  27. ↑ "multi-seat with only one graphics card".
  28. ↑ "VcXsrv Windows X Server". Sourceforge.net. Retrieved 2014-04-28.
  29. ↑ "VcXsrv Windows X Server". SourceForge.net. Retrieved 2013-06-23. Windows X-server based on the xorg git sources (like xming or cygwin's xwin), but compiled with Visual C++ 2010.
  30. ↑ Re: Xorg in Leopard?, From: Ben Byer, Date: 29 June 2007, Apple Mailing Lists
  31. ↑ Slivka, Eric (17 February 2012). "Apple Removes X11 in OS X Mountain Lion, Shifts Support to Open Source XQuartz". MacRumors. Retrieved 23 February 2012.
  32. ↑ "X.Org Foundation Modularization Working Group". X.Org Foundation. Retrieved 6 February 2014.
  33. ↑ Høgsberg, Kristian. "Doing git migration now". Retrieved 6 February 2014.
  34. ↑ Coopersmith, Alan. "Some times it's a book sprint, other times it's a marathon". Retrieved 6 February 2014.
  35. ↑ "The X.Org Server's GLX Is Being Rewritten". 26 October 2013.
  36. ↑ "X11R6.9 and X11R7.0 Officially Released". X.org. Retrieved 7 February 2015.
  37. ↑ Jackson, Adam. "[ANNOUNCE] xorg-server 1.1.0". X.org. Retrieved 7 February 2015.
  38. ↑ "Summary of new features in X11R7.1". X.org. Retrieved 7 February 2015.
  39. ↑ Jackson, Adam. "[ANNOUNCE] xserver 1.2.0". X.org. Retrieved 7 February 2015.
  40. ↑ "X11R7.2 Release". X.org. Retrieved 7 February 2015.
  41. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.3.0.0 again". X.org. Retrieved 7 February 2015.
  42. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.2.99.901 (X server 1.3 RC1)". X.org. Retrieved 7 February 2015.
  43. 1 2 Anholt, Eric. "[ANNOUNCE] xorg-server 1.4". X.org. Retrieved 7 February 2015.
  44. ↑ "X server version 1.4 release plans". X.org. Retrieved 7 February 2015.
  45. ↑ Jackson, Adam. "[ANNOUNCE] xserver 1.5.0". X.org. Retrieved 7 February 2015.
  46. ↑ "MPX has been merged". 2008-05-26.
  47. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.6.0". X.org. Retrieved 7 February 2015.
  48. ↑ "Server 1.6 branch". X.org. Retrieved 7 February 2015.
  49. ↑ Hutterer, Peter. "[ANNOUNCE] xorg-server 1.7.0". X.org. Retrieved 7 February 2015.
  50. ↑ "Server 1.7 branch". X.org. Retrieved 7 February 2015.
  51. ↑ Larabel, Michael. "X Server 1.7 Released With XI2/MPX Glory". Phoronix. Retrieved 7 February 2015.
  52. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.8.0". X.org. Retrieved 7 February 2015.
  53. ↑ Larabel, Michael. "X.Org Server 1.8.0 Is Here". Phoronix. Retrieved 7 February 2015.
  54. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.9.0". X.org. Retrieved 7 February 2015.
  55. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.10.0". X.org. Retrieved 7 February 2015.
  56. ↑ Larabel, Michael. "That Was Quick, X Server 1.10 Officially Released". Phoronix. Retrieved 8 February 2015.
  57. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.11.0". X.org. Retrieved 7 February 2015.
  58. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.12.0". X.org. Retrieved 7 February 2015.
  59. ↑ Larabel, Michael. "X.Org Server 1.12 Released With Multi-Touch". Phoronix. Retrieved 8 February 2015.
  60. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.13.0". X.org. Retrieved 7 February 2015.
  61. ↑ Larabel, Michael. "X.Org Server 1.13 Released With Massive Changes". Phoronix. Retrieved 8 February 2015.
  62. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.14.0". X.org. Retrieved 7 February 2015.
  63. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.13.99.901 (1.14 RC1)". X.org. Retrieved 9 February 2015.
  64. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.15.0". X.org. Retrieved 7 February 2015.
  65. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.14.99.901". X.org. Retrieved 9 February 2015.
  66. ↑ Larabel, Michael. "X.Org Server 1.15 Release Has Several New Features". Phoronix. Retrieved 9 February 2015.
  67. 1 2 Packard, Keith. "[ANNOUNCE] xorg-server 1.16.0". X.org. Retrieved 7 February 2015.
  68. ↑ Larabel, Michael. "X.Org Server 1.16 Officially Released With Terrific Features". Phoronix. Retrieved 9 February 2015.
  69. ↑ Hutterer, Peter (24 September 2014). "libinput - a common input stack for Wayland compositors and X.Org drivers". Retrieved 17 April 2016.
  70. ↑ de Goede, Hans (1 February 2015). "Replacing xorg input - Drivers with libinput" (PDF). Retrieved 18 April 2016.
  71. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.17.0". X.org. Retrieved 7 February 2015.
  72. ↑ Packard, Keith. "[ANNOUNCE] xorg-server 1.16.99.901". X.org. Retrieved 9 February 2015.
  73. ↑ Larabel, Michael. "X.Org Server 1.17 Officially Released". Phoronix. Retrieved 9 February 2015.
  74. ↑ Jackson, Adam (9 November 2015). "[ANNOUNCE] xorg-server 1.18.0". xorg-announce (Mailing list).
  75. ↑ Packard, Keith (15 November 2016). "[ANNOUNCE] xorg-server 1.19.0". xorg-announce (Mailing list).
  76. ↑ Larabel, Michael. "X.Org Server 1.19 Officially Released With A Year's Worth Of Improvements". Phoronix. Retrieved 15 November 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.