Xinerama

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Four Head Xinerama

Xinerama is an extension to the X Window System which enables multi-headed X applications and window managers to use two or more physical displays as one large virtual display.

It was originally developed by DEC (under the name PanoramiX), who contributed it to The Open Group for X11 Release 6.4 (X11R6.4), where it was renamed Xinerama. From there it was incorporated into XFree86 for the XFree86 4.0 release, and Solaris in the Solaris 7 11/99 release. The name Xinerama may have been inspired from the Cinerama widescreen theatre process.


It is also an advantage if the window manager, via Xinerama awareness, can pop up new windows on the active physical display. Another advantage of Xinerama awareness is to only maximize windows to the dimensions of the active physical display.

Contents

[edit] General Theory of Operation

The general mode of operation is that multiple X screens (as denoted normally by :0.0, :0.1, etc) can be unified into a single workspace via enabling Xinerama in the X server. This creates a single unified work area that allows windows to be transferred across X screens.

[edit] XINERAMA extension

The Xinerama extension is used to provide clients with information about the layout of viewports within the unified workspace. It contains offset and size information to allow clients to make intelligent decisions about window placement, window maximization and other user interaction events.

[edit] Use in non-XINERAMA environments

Due to the X servers client/server architecture, the server can expose Xinerama information to the client without the X servers Xinerama infrastructure being active.

RANDR, ATI's big desktop and NVIDIA's twinview utilize this to provide window managers and clients with useful information about the output layout relative to the framebuffer.

[edit] Deprecation of XINERAMA

As of 2008, Xinerama is planned to be deprecated in the future by X.org in favor of XRandR. [1] X.Org had convened a standards committee to document the protocol and API as formal standards, but that effort has now ended. [2] Development of the Xinerama code is now hosted on freedesktop.org and managed by X.Org.

The RANDR infrastructure still relies on the Xinerama extension to provide output position information over the framebuffer. Xinerama supports the combining of any X displays across multiple ASICs, however RANDR only supports a single GPU.

[edit] Known problems

[edit] Common Color Depth

Xinerama requires that the physical screens have the same bit depth — an 8-bit screen cannot be combined with a 16-bit screen, for example.

[edit] Hardware Rendering

In most Open Source implementations, OpenGL (3D) direct-rendering only works on one of the screens. Windows that should show 3D graphics on other screens tend to just appear black. This is most commonly seen with 3D screen savers, which show on one of the screens and black on the others. The Solaris SPARC OpenGL implementation, ATI Proprietary Linux driver and NVIDIA Proprietary Linux driver all support hardware accelerated rendering to all screens in Xinerama mode.

[edit] Static Configuration

There is currently no way to dynamically add or remove physical screens, and there is no way to change the resolution of a screen. (The XRandR feature is disabled when Xinerama is used). This is a particular difficulty for laptop and tablet PC users (or any mobile computer), where you commonly want to sit at a desk and use an external physical display in addition to the computer's built-in screen, but only when at the desk. In these cases, use of RANDR, ATI's or NVIDIA's single GPU method is recommended.

Because Xinerama does not support adding or removing screens (at the time of writing)[when?], it causes several problems:

  • When the external screen is not connected, windows may still appear on it. You have to drag them to the built-in screen without being able to see them.
  • The laptop may still be sending video signals, which uses unnecessary power and may reduce the battery life.
  • When you want to use a different external display (for example when moving between locations that have one), there's a good chance it will need different settings like screen resolution and refresh rate. But you cannot change these settings when Xinerama is enabled.

These are all problems with the Xinerama implementation rather than the design, and they could be fixed with sufficient work.

[edit] Window Manager Support

Some[which?] window managers and desktop environments have limited awareness of the separate physical screens in Xinerama. They work, but the desktop is simply stretched over the physical screens. When a window opens, the window manager may place it on an unexpected screen, which is confusing and annoying if the displays are not arranged like a single large desktop.

Despite these problems, Xinerama offers an advantage over separate X screens: You can move windows between Xinerama screens.

[edit] Dead Space

The physical displays do not need to be the same resolution. Some window managers assume that the virtual display area is rectangular, but this isn't necessarily the case if the component physical displays are not the same size. The excess space, which is needed to make the area rectangular, is called "dead space". The window manager needs to be aware of Xinerama to recognize dead space, and avoid placing new windows there.


[edit] See also

[edit] References

[edit] External links

Personal tools