Mode setting

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Regulating access to the hardware is a fundamental kernel task. The Direct Rendering Manager and KMS are part of the Linux kernel. The KMS does only the mode setting.

Mode setting is a software operation that activates a display mode (screen resolution, color depth, and refresh rate) for a computer's display controller.

In kernel mode-setting (KMS), the display mode is set by the kernel. In user-space mode-setting (UMS), the display mode is set by a userland process.

Kernel mode-setting is more flexible and allows displaying of an error in the case of a fatal error in the kernel, even when using a user-space display server.

User-space mode setting would require superuser privileges for direct hardware access, so kernel-based mode setting shuns such requirement for the user-space graphics server.

Implementation

Microsoft Windows

Microsoft Windows versions that are NT-based use kernel mode setting. The kernel error display made possible by kernel mode setting is known as the Blue Screen of Death.

Linux

The role of KMS (Kernel mode-setting), Linux example
The Linux Graphics Stack 2013
Wayland compositors require KMS (and also OpenGL ES and EGL)
The place of certain Linux kernel modules
evdev is the Linux kernel module that receives data from various Input devices such as Keyboard, Mouse, Touch-Pad, etc. The data is passed to the Display server (e.g. the X.Org Server or some Wayland compositor only to be passed further to the Wayland client respectively X client. Some applications require a minimal latency

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Direct Rendering Manager

The Linux kernel got the prerequisite for kernel-based mode setting by accepting Intel GEM in version 2.6.28, released in December 2008.[1] This will be[needs update] replaced by Tungstens Graphics TTM (Translation Table Maps) memory manager which supports the GEM API.[2] TTM was developed for the free and open-source drivers for Radeon and S3 Graphics graphic chipsets (see Free and open-source graphics device driver).[3] Support for Intel GMA graphic chipsets was accepted in version 2.6.29, released on March 23, 2009.[4] Support for pre-R600 ATI Radeon graphics cards was accepted in version 2.6.31, released on September 9, 2009.[5] Support for R600 and R700 was in development within DRM and was merged in version 2.6.32.[6] Support for Evergreen (R800) was merged in version 2.6.34. As Nvidia did not release all the needed documentation for its graphics chip, development proceeded under the nouveau project, which uses reverse engineering to build a working open-source driver for Nvidia cards. Nouveau was accepted in version 2.6.33 of the kernel, released on December 10, 2009. Kernel-based mode setting is not only supported by the nouveau driver, it is required.[7] Wayland compositors (e.g. Weston) and kmscon depend on kernel mode setting via ioctl.

FreeBSD

FreeBSD has support for both kernel-based mode setting and GEM for later generations of Intel GPUs (IronLake, SandyBridge, and IvyBridge) starting with version 9.1.[8]

NetBSD

NetBSD has support for kernel-based mode setting and accelerated graphics for Intel and Radeon devices. This implementation was introduced in version 7.0 by porting the Linux 3.15 DRM/KMS code.[9]

OpenBSD

OpenBSD has kernel-based mode setting support for Intel and Radeon GPUs. Starting with version 5.4 of OpenBSD, support for Intel GPUs is available. With the release of version 5.5, the implementation has been extended to add support for Radeon chipsets as well.

Alternatives

Lua error in package.lua at line 80: module 'strict' not found. The following alternatives have been presented during the Linux Plumbers Conference 2013:

  • It was suggested to split GEM and KMS.[10]
  • Atomic Display Framework, by Google's Android-Team.[11][12]
  • Common Display Framework.[13]

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ http://www.linuxplumbersconf.org/2013/ocw/sessions/1107
  11. ↑ http://www.linuxplumbersconf.org/2013/ocw/proposals/1551
  12. ↑ http://www.linuxplumbersconf.org/2013/ocw/sessions/1467
  13. ↑ http://www.linuxplumbersconf.org/2013/ocw/sessions/1317

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Mode_setting&oldid=717090858"