Man page 4 : intel

intel - Intel integrated graphics chipsets

Section \*qDevice\*q Identifier \*q devname \*q

Driver \*qintel\*q   ...

EndSection

intel is an Xorg driver for Intel integrated graphics chipsets. The driver supports depths 8, 15, 16 and 24. All visual types are supported in depth 8. For the i810/i815 other depths support the TrueColor and DirectColor visuals. For the i830M and later, only the TrueColor visual is supported for depths greater than 8. The driver supports hardware accelerated 3D via the Direct Rendering Infrastructure (DRI), but only in depth 16 for the i810/i815 and depths 16 and 24 for the 830M and later.

intel supports the i810, i810-DC100, i810e, i815, i830M, 845G, 852GM, 855GM, 865G, 915G, 915GM, 945G, 945GM, 965G, 965Q, 946GZ, 965GM, 945GME, G33, Q33, Q35, G35, GM45, G45, Q45, G43, G41 chipsets, and Pineview-M in Atom N400 series, Pineview-D in Atom D400/D500 series.

Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.

The Intel 8xx and 9xx families of integrated graphics chipsets have a unified memory architecture meaning that system memory is used as video RAM. For the i810 and i815 family of chipsets, operating system support for allocating system memory is required in order to use this driver. For the 830M and later, this is required in order for the driver to use more video RAM than has been pre-allocated at boot time by the BIOS. This is usually achieved with an "agpgart" or "agp" kernel driver. Linux, FreeBSD, OpenBSD, NetBSD, and Solaris have such kernel drivers available.

By default, the i810/i815 will use 8 MB of system memory for graphics if AGP allocable memory is < 128 MB, 16 MB if < 192 MB or 24 MB if higher. Use the

VideoRam option to change the default value.

For the 830M and later, the driver will automatically size its memory allocation according to the features it will support. Therefore, the

VideoRam option, which in the past had been necessary to allow more than some small amount of memory to be allocated, is now ignored.

The following driver

Options are supported

• Option \*qColorKey\*q \*q integer \*q
      This sets the default pixel value for the YUV video overlay key.

Default: undefined.

• Option \*qDRI\*q \*q boolean \*q
      Disable or enable DRI support.

Default: DRI is enabled for configurations where it is supported.

The following driver

Options are supported for the i810 and i815 chipsets:

• Option \*qCacheLines\*q \*q integer \*q
      This allows the user to change the amount of graphics memory used for 2D acceleration and video when XAA acceleration is enabled. Decreasing this amount leaves more for 3D textures. Increasing it can improve 2D performance at the expense of 3D performance.

Default: depends on the resolution, depth, and available video memory. The driver attempts to allocate space for at 3 screenfuls of pixmaps plus an HD-sized XV video. The default used for a specific configuration can be found by examining the Xorg log file.

• Option \*qDDC\*q \*q boolean \*q
      Disable or enable DDC support.

Default: enabled.

• Option \*qDac6Bit\*q \*q boolean \*q
      Enable or disable 6-bits per RGB for 8-bit modes.

Default: 8-bits per RGB for 8-bit modes.

• Option \*qXvMCSurfaces\*q \*q integer \*q
      This option enables XvMC. The integer parameter specifies the number of surfaces to use. Valid values are 6 and 7.

Default: XvMC is disabled.

• VideoRam integer
      This option specifies the amount of system memory to use for graphics, in KB.

The default is 8192 if AGP allocable memory is < 128 MB, 16384 if < 192 MB, 24576 if higher. DRI require at least a value of 16384. Higher values may give better 3D performance, at expense of available system memory.

• Option \*qNoAccel\*q \*q boolean \*q
      Disable or enable acceleration.

Default: acceleration is enabled.

The following driver

Options are supported for the 830M and later chipsets:

• Option \*qVideoKey\*q \*q integer \*q
      This is the same as the

\*qColorKey\*q option described above. It is provided for compatibility with most other drivers.

• Option \*qXvPreferOverlay\*q \*q boolean \*q
      Make hardware overlay be the first XV adaptor. The overlay behaves incorrectly in the presence of compositing, but some prefer it due to it syncing to vblank in the absence of compositing. While most XV-using applications have options to select which XV adaptor to use, this option can be used to place the overlay first for applications which don't have options for selecting adaptors.

Default: Textured video adaptor is preferred.

• Option \*qFallbackDebug\*q \*q boolean \*q
      Enable printing of debugging information on acceleration fallbacks to the server log.

Default: Disabled

• Option \*qDebugFlushBatches\*q \*q boolean \*q
      Flush the batch buffer after every single operation.

Default: Disabled

• Option \*qDebugFlushCaches\*q \*q boolean \*q
      Include an MI_FLUSH at the end of every batch buffer to force data to be flushed out of cache and into memory before the completion of the batch.

Default: Disabled

• Option \*qDebugWait\*q \*q boolean \*q
      Wait for the completion of every batch buffer before continuing, i.e. perform synchronous rendering.

Default: Disabled

• Option \*qShadow\*q \*q boolean \*q
      This option controls the use of GPU acceleration and placement of auxiliary buffers in memory. Enabling the Shadow will disable all use of the GPU for RENDER acceleration and force software-fallbacks for all but updating the scan-out buffer. Hardware overlay is still supported so Xv will continue to playback videos using the GPU, but GL will be forced to use software rasterisation as well. This is a last resort measure for systems with crippling bugs, such as early 8xx chipsets. It is still hoped that we will find a workaround to enable as much hardware acceleration on those architectures as is possible, but until then, using a shadow buffer should maintain system stability.

Default: Disabled

• Option \*qSwapbuffersWait\*q \*q boolean \*q
      This option controls the behavior of glXSwapBuffers and glXCopySubBufferMESA calls by GL applications. If enabled, the calls will avoid tearing by making sure the display scanline is outside of the area to be copied before the copy occurs. If disabled, no scanline synchronization is performed, meaning tearing will likely occur. Note that when enabled, this option can adversely affect the framerate of applications that render frames at less than refresh rate.

Default: enabled.

• Option \*qTiling\*q \*q boolean \*q
      This option controls whether memory buffers are allocated in tiled mode. In most cases (especially for complex rendering), tiling dramatically improves performance.

Default: enabled.

• Option \*qXvMC\*q \*q boolean \*q
      Enable XvMC driver. Current support MPEG2 MC on 915/945 and G33 series. User should provide absolute path to libIntelXvMC.so in XvMCConfig file.

Default: Disabled.

On 830M and better chipsets, the driver supports runtime configuration of detected outputs. You can use the

xrandr tool to control outputs on the command line as follows:

xrandr --output output

--set property value Note that you may need to quote property and value arguments that contain spaces. Each output listed below may have one or more properties associated with it (like a binary EDID block if one is found). Some outputs have unique properties which are described below. See the "MULTIHEAD CONFIGURATIONS" section below for additional information.

6.1. VGA ▲

6.2. LVDS ▲

6.3. TV ▲

6.4. TMDS-1 ▲

6.5. TMDS-2 ▲

6.6. TMDS-1, TMDS-2, HDMI-1, HDMI-2 ▲

The number of independent outputs is dictated by the number of CRTCs (in X parlance) a given chip supports. Most recent Intel chips have two CRTCs, meaning that two separate framebuffers can be displayed simultaneously, in an extended desktop configuration. If a chip supports more outputs than it has CRTCs (say local flat panel, VGA and TV in the case of many outputs), two of the outputs will have to be "cloned", meaning that they display the same framebuffer contents (or one displays a subset of another's framebuffer if the modes aren't equal). You can use the "xrandr" tool, or various desktop utilities, to change your output configuration at runtime. To statically configure your outputs, you can use the "Monitor-<type>" options along with additional monitor sections in your xorg.conf to create your screen topology. The example below puts the VGA output to the right of the builtin laptop screen, both running at 1024x768.

Section \*qMonitor\*q Identifier \*qLaptop FooBar Internal Display\*q Option \*qPosition\*q \*q0 0\*q

EndSection

Section \*qMonitor\*q Identifier \*qSome Random CRT\*q Option \*qPosition\*q \*q1024 0\*q Option \*qRightOf\*q \*qLaptop FoodBar Internal Display\*q

EndSection

Section \*qDevice\*q Driver \*qintel\*q Option \*qmonitor-LVDS\*q \*qLaptop FooBar Internal Display\*q Option \*qmonitor-VGA\*q \*qSome Random CRT\*q

EndSection

The driver supports the following X11 Xv attributes for Textured Video. You can use the "xvattr" tool to query/set those attributes at runtime.

8.1. XV_SYNC_TO_VBLANK ▲

8.2. XV_BRIGHTNESS ▲

8.3. XV_CONTRAST ▲

The xf86-video-intel driver is part of the X.Org and Freedesktop.org umbrella projects. Details on bug reporting can be found at http://www.intellinuxgraphics.org/how_to_report_bug.html. Mailing lists are also commonly used to report experiences and ask questions about configuration and other topics. See lists.freedesktop.org for more information (the mailing list is the most appropriate place to ask X.Org and driver related questions).

Xorg(1), xorg.conf(5), Xserver(1), X(7)

Authors include: Keith Whitwell, and also Jonathan Bian, Matthew J Sottek, Jeff Hartmann, Mark Vojkovich, Alan Hourihane, H. J. Lu. 830M and 845G support reworked for XFree86 4.3 by David Dawes and Keith Whitwell. 852GM, 855GM, and 865G support added by David Dawes and Keith Whitwell. 915G, 915GM, 945G, 945GM, 965G, 965Q and 946GZ support added by Alan Hourihane and Keith Whitwell. Lid status support added by Alan Hourihane. Textured video support for 915G and later chips, RandR 1.2 and hardware modesetting added by Eric Anholt and Keith Packard. EXA and Render acceleration added by Wang Zhenyu. TV out support added by Zou Nan Hai and Keith Packard. 965GM, G33, Q33, and Q35 support added by Wang Zhenyu.