1MODESETTING(@drivermansuffix@) MODESETTING(@drivermansuffix@)
2
6 modesetting - video driver for framebuffer device
7
9 Section "Device"
10 Identifier "devname"
11 Driver "modesetting"
12 BusID "pci:bus:dev:func"
13 ...
14 EndSection
15
17 modesetting is an @xservername@ driver for KMS devices. This driver
18 supports TrueColor visuals at framebuffer depths of 15, 16, 24, and 30.
19 RandR 1.2 is supported for multi-head configurations. Acceleration is
20 available through glamor for devices supporting at least OpenGL ES 2.0
21 or OpenGL 2.1. If glamor is not enabled, a shadow framebuffer is con‐
22 figured based on the KMS drivers' preference (unless the framebuffer is
23 24 bits per pixel, in which case the shadow framebuffer is always
24 used).
25
27 The modesetting driver supports all hardware where a KMS driver is
28 available. modesetting uses the Linux DRM KMS ioctls and dumb object
29 create/map.
30
32 Please refer to @xconfigfile@(@filemansuffix@) for general configura‐
33 tion details. This section only covers configuration details specific
34 to this driver.
35 For this driver it is not required to specify modes in the screen sec‐
37 tion of the config file. The modesetting driver can pick up the cur‐
38 rently used video mode from the kernel driver and will use it if there
39 are no video modes configured.
40 For PCI boards you might have to add a BusID line to the Device sec‐
42 tion. See above for a sample line.
43 The following driver Options are supported:
45 Option "SWcursor" "boolean"
47 Selects software cursor. The default is off.
48 Option "kmsdev" "string"
50 The framebuffer device to use. Default: /dev/dri/card0.
51 Option "ShadowFB" "boolean"
53 Enable or disable use of the shadow framebuffer layer. Default:
54 on.
55 Option "DoubleShadow" "boolean"
57 Double-buffer shadow updates. When enabled, the driver will keep
58 two copies of the shadow framebuffer. When the shadow frame‐
59 buffer is flushed, the old and new versions of the shadow are
60 compared, and only tiles that have actually changed are uploaded
61 to the device. This is an optimization for server-class GPUs
62 with a remote display function (typically VNC), where remote
63 updates are triggered by any framebuffer write, so minimizing
64 the amount of data uploaded is crucial. This defaults to
65 enabled for ASPEED and Matrox G200 devices, and disabled other‐
66 wise.
67 Option "AccelMethod" "string"
69 One of "glamor" or "none". Default: glamor.
70 Option "PageFlip" "boolean"
72 Enable DRI3 page flipping. The default is on.
73 Option "ZaphodHeads" "string"
75 Specify the RandR output(s) to use with zaphod mode for a par‐
76 ticular driver instance. If you use this option you must use
77 this option for all instances of the driver.
78 For example: Option "ZaphodHeads" "LVDS,VGA-0" will assign
79 xrandr outputs LVDS and VGA-0 to this instance of the driver.
80 SEE ALSO
83 @xservername@(@appmansuffix@), @xconfigfile@(@filemansuffix@),
84 Xserver(@appmansuffix@), X(@miscmansuffix@)
85
87 Authors include: Dave Airlie
88 @vendorversion@ MODESETTING(@drivermansuffix@)