|Initial release||6 April 2004|
|Stable release||1.16.3 (December 20, 2014) [±]|
|Preview release||184.108.40.2061 (October 29, 2014) [±]|
X.Org Server refers to the free and open source implementation of the X Window System stewarded by the X.Org Foundation that includes not only the display server but also the client libraries (like Xlib and XCB), developer and user tools, and the rest of the components required to run an entire X Window System architecture.
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[clarification needed].
The X.Org Server implements the server side of the X Window System core protocol and extensions to it. Implementations of the client side of the protocol are available e.g. in the form of Xlib and XCB. Version 1.16.0 integrates support for systemd-based launching and management which improved boot performance and reliability.
- Graphics device drivers
- For historical reasons the X.Org Server still contains graphics device drivers supporting some form of 2D rendering acceleration.
- Device Independent X (DIX)
- The Device Independent X (DIX) is the part of the 2D graphics device driver, which is not specific to any hardware.
- Device Independent X (DIX)
- Device Dependent X (DDX)
- The Device Dependent X (DDX) is the part of the 2D graphics device driver, which is hardware specific. AMD's proprietary Catalyst includes such an extra device driver, just for the X.Org Server, additionally to the actual kernel blobs and user space device driver. So does Nvidia's proprietary driver package. The available free and open-source graphics device drivers all maintain such a DDX additionally to the DRM kernel part and the user-space driver in Mesa 3D.
- Device Dependent X (DDX)
- Glamor is a generic 2D acceleration driver for the X server that works translating the X render primitives to OpenGL operations, taking advantage of any existing 3D OpenGL drivers, proprietary and open-source. The ultimate goal of GLAMOR is to obsolete and replace all the DDX, the device dependent X drivers, and acceleration architectures for them (like XAA, EXA, UXA or SNA) by a single hardware independent 2D driver, avoiding the need to write X 2D specific drivers for every supported graphic chipset. Glamor requires a 3D driver with shader support.
- Glamor performance tuning was accepted for Google Summer of Code 2014. Glamor supports Xephyr and DRI3, and can boost some operations by 700–800%. Since its mainlining into version 1.16 of the X.Org Server, development on Glamor was continued and patches for the upcoming 1.17 release were published early.
- 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 of X11 applications during the transition to Wayland, and was mainlined in version 1.16 of the X.Org Server.
- 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.
- There is a device driver for the X.Org Server called Xspice. It supports the QXL framebuffer device and includes a wrapper script 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 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.
- Unix and Linux
- The X.Org Server runs on many free-software Unix-like operating systems; most Linux distributions and BSD variants have adopted it. It is also the X server for the Solaris operating system.
- Microsoft Windows
- Cygwin/X, Cygwin's implementation of the X server for Microsoft Windows, uses the X.Org Server, as do VcXsrv(Visual C++ X-server) and Xming.
- 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. 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. 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.
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. 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, 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 release 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 (using GNU Autotools) 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. Both efforts had the long-term goal of bringing new developers to the project. In the words of Alan Coopersmith:
|“||Some of our efforts here have been technological - one of the driving efforts of the conversions from Imake to automake and from CVS to git was to make use of tools developers would already be familiar and productive with from other projects. The Modularization project, which broke up X.Org from one giant tree into over 200 small ones, had the goal of making it possible to fix a bug in a single library or driver without having to download and build many megabytes of software & fonts that were not being changed.||”|
In the release 7.1 the KDrive framework (a small implementation of X, written by Keith Packard, that 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 KMS-based DRI2 replaced the old 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 2013 the implementation of GLX was rewritten by Adam Jackson at Red Hat.
- "X.Org Foundation releases X Window System X11R6.7". Linux Weekly News. 2004-04-07. Retrieved 2012-04-04.
- "xorg-server 220.127.116.111". 2014-10-29.
- "Debian X.Org Server Package in sid".
- "ANNOUNCE: xorg-server 1.16.0". freedesktop.org. 2014-07-17.
- "What is Glamor?". FreeDesktop.org. Retrieved 10 February 2014.
- Anholt, Eric. "Building 2D rendering acceleration with OpenGL". linux.conf.au. Retrieved 10 February 2014.
- Packard, Keith. "Brief Glamor Hacks". Retrieved 7 March 2014.
- "Adam Jackson - GLX rewrite". 2013-09-24. Retrieved 2014-03-23.
- "Radeon Feature Matrix". freedesktop.org.
- "Glamor Performance Tuning".
- "GLAMOR Xephyr & DRI3 Support Called For Pulling". Phoronix. 2014-03-05.
- "GLAMOR Patch Bomb Can Boost Some Operations By 700~800%". Phoronix. 2014-03-13.
- "glamor changes for 1.17". 2014-07-17.
- "X Clients under Wayland (XWayland)". Wayland Project. Retrieved 10 February 2014.
- "XSpice README". Cgit.freedesktop.org. Retrieved 2013-10-25.
- "VcXsrv Windows X Server". Sourceforge.net. Retrieved 2014-04-28.
- "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.
- Re: Xorg in Leopard?, From: Ben Byer, Date: 29 June 2007, Apple Mailing Lists
- Slivka, Eric (February 17, 2012). "Apple Removes X11 in OS X Mountain Lion, Shifts Support to Open Source XQuartz". MacRumors. Retrieved February 23, 2012.
- "X.Org Foundation Modularization Working Group". X.Org Foundation. Retrieved 6 February 2014.
- Høgsberg, Kristian. "Doing git migration now". Retrieved 6 February 2014.
- Coopersmith, Alan. "Some times it’s a book sprint, other times it’s a marathon". Retrieved 6 February 2014.
- "The X.Org Server's GLX Is Being Rewritten". 2013-10-26.
- "ANNOUNCE: xorg-server 18.104.22.1681". 2013-11-01.
- "add XWayland GLAMOR & DRI3 support". 2014-06-25.
|Wikimedia Commons has media related to X.Org Server.|