1MODESETTING(4)             Kernel Interfaces Manual             MODESETTING(4)
2
3
4

NAME

6       modesetting - video driver for framebuffer device
7

SYNOPSIS

9       Section "Device"
10         Identifier "devname"
11         Driver "modesetting"
12         BusID  "pci:bus:dev:func"
13         ...
14       EndSection
15

DESCRIPTION

17       modesetting  is  an  Xorg driver for KMS devices.  This driver supports
18       TrueColor visuals at framebuffer depths of 15, 16, 24,  and  30.  RandR
19       1.2  is supported for multi-head configurations. Acceleration is avail‐
20       able through glamor for devices supporting at least OpenGL  ES  2.0  or
21       OpenGL  2.1.  If glamor is not enabled, a shadow framebuffer is config‐
22       ured based on the KMS drivers' preference (unless the framebuffer is 24
23       bits per pixel, in which case the shadow framebuffer is always used).
24

SUPPORTED HARDWARE

26       The  modesetting  driver  supports  all  hardware where a KMS driver is
27       available.  modesetting uses the Linux DRM KMS ioctls and  dumb  object
28       create/map.
29

CONFIGURATION DETAILS

31       Please  refer  to xorg.conf(5) for general configuration details.  This
32       section only covers configuration details specific to this driver.
33
34       For this driver it is not required to specify modes in the screen  sec‐
35       tion  of  the config file.  The modesetting driver can pick up the cur‐
36       rently used video mode from the kernel driver and will use it if  there
37       are no video modes configured.
38
39       For  PCI  boards  you might have to add a BusID line to the Device sec‐
40       tion.  See above for a sample line.
41
42       The following driver Options are supported:
43
44       Option "SWcursor" "boolean"
45              Selects software cursor.  The default is off.
46
47       Option "kmsdev" "string"
48              The framebuffer device to use. Default: /dev/dri/card0.
49
50       Option "ShadowFB" "boolean"
51              Enable or disable use of the shadow framebuffer layer.  Default:
52              on.
53
54       Option "DoubleShadow" "boolean"
55              Double-buffer shadow updates. When enabled, the driver will keep
56              two copies of the shadow framebuffer.  When  the  shadow  frame‐
57              buffer  is  flushed,  the old and new versions of the shadow are
58              compared, and only tiles that have actually changed are uploaded
59              to  the  device.  This  is an optimization for server-class GPUs
60              with a remote display function  (typically  VNC),  where  remote
61              updates  are  triggered  by any framebuffer write, so minimizing
62              the amount of  data  uploaded  is  crucial.   This  defaults  to
63              enabled  for ASPEED and Matrox G200 devices, and disabled other‐
64              wise.
65
66       Option "AccelMethod" "string"
67              One of "glamor" or "none".  Default: glamor.
68
69       Option "PageFlip" "boolean"
70              Enable DRI3 page flipping.  The default is on.
71
72       Option "ZaphodHeads" "string"
73              Specify the RandR output(s) to use with zaphod mode for  a  par‐
74              ticular  driver  instance.   If you use this option you must use
75              this option for all instances of the driver.
76              For  example:  Option  "ZaphodHeads"  "LVDS,VGA-0"  will  assign
77              xrandr outputs LVDS and VGA-0 to this instance of the driver.
78
79
80       SEE ALSO
81              Xorg(1), xorg.conf(5), Xserver(1), X(7)
82

AUTHORS

84       Authors include: Dave Airlie
85
86
87
88X Version 11                  xorg-server 1.20.6                MODESETTING(4)
Impressum