2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# Drm device configuration
|
|
|
|
|
#
|
|
|
|
|
# This driver provides support for the
|
|
|
|
|
# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
|
|
|
|
|
#
|
2007-10-16 08:29:39 +00:00
|
|
|
menuconfig DRM
|
2005-04-16 22:20:36 +00:00
|
|
|
tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
|
2010-05-27 19:40:25 +00:00
|
|
|
depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU
|
2012-11-21 14:31:35 +00:00
|
|
|
select HDMI
|
2008-12-13 08:21:08 +00:00
|
|
|
select I2C
|
|
|
|
|
select I2C_ALGOBIT
|
2011-11-25 15:21:02 +00:00
|
|
|
select DMA_SHARED_BUFFER
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Kernel-level support for the Direct Rendering Infrastructure (DRI)
|
|
|
|
|
introduced in XFree86 4.0. If you say Y here, you need to select
|
|
|
|
|
the module that's right for your graphics card from the list below.
|
|
|
|
|
These modules provide support for synchronization, security, and
|
|
|
|
|
DMA transfers. Please see <http://dri.sourceforge.net/> for more
|
|
|
|
|
details. You should also select and configure AGP
|
2010-05-27 19:40:25 +00:00
|
|
|
(/dev/agpgart) support if it is available for your platform.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2012-03-20 06:59:29 +00:00
|
|
|
config DRM_USB
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
2012-08-24 19:20:03 +00:00
|
|
|
depends on USB_SUPPORT && USB_ARCH_HAS_HCD
|
2012-03-20 06:59:29 +00:00
|
|
|
select USB
|
|
|
|
|
|
2009-09-08 01:08:32 +00:00
|
|
|
config DRM_KMS_HELPER
|
2009-09-07 05:45:33 +00:00
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
select FB
|
2011-01-20 22:44:16 +00:00
|
|
|
select FRAMEBUFFER_CONSOLE if !EXPERT
|
2011-04-21 21:51:33 +00:00
|
|
|
select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
|
2009-09-07 05:45:33 +00:00
|
|
|
help
|
2009-09-08 01:08:32 +00:00
|
|
|
FB and CRTC helpers for KMS drivers.
|
2009-09-07 05:45:33 +00:00
|
|
|
|
2012-03-18 21:37:33 +00:00
|
|
|
config DRM_LOAD_EDID_FIRMWARE
|
|
|
|
|
bool "Allow to specify an EDID data set instead of probing for it"
|
|
|
|
|
depends on DRM_KMS_HELPER
|
|
|
|
|
help
|
|
|
|
|
Say Y here, if you want to use EDID data to be loaded from the
|
|
|
|
|
/lib/firmware directory or one of the provided built-in
|
|
|
|
|
data sets. This may be necessary, if the graphics adapter or
|
|
|
|
|
monitor are unable to provide appropriate EDID data. Since this
|
|
|
|
|
feature is provided as a workaround for broken hardware, the
|
|
|
|
|
default case is N. Details and instructions how to build your own
|
|
|
|
|
EDID data are given in Documentation/EDID/HOWTO.txt.
|
|
|
|
|
|
2009-06-10 13:20:19 +00:00
|
|
|
config DRM_TTM
|
2009-06-05 12:42:42 +00:00
|
|
|
tristate
|
2009-06-10 13:20:19 +00:00
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
GPU memory management subsystem for devices with multiple
|
|
|
|
|
GPU memory types. Will be enabled automatically if a device driver
|
|
|
|
|
uses it.
|
|
|
|
|
|
2012-06-27 13:30:18 +00:00
|
|
|
config DRM_GEM_CMA_HELPER
|
|
|
|
|
bool
|
|
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
Choose this if you need the GEM CMA helper functions
|
|
|
|
|
|
2012-07-02 14:37:47 +00:00
|
|
|
config DRM_KMS_CMA_HELPER
|
|
|
|
|
bool
|
|
|
|
|
select DRM_GEM_CMA_HELPER
|
|
|
|
|
select FB_SYS_FILLRECT
|
|
|
|
|
select FB_SYS_COPYAREA
|
|
|
|
|
select FB_SYS_IMAGEBLIT
|
|
|
|
|
help
|
|
|
|
|
Choose this if you need the KMS CMA helper functions
|
|
|
|
|
|
2013-01-24 21:46:07 +00:00
|
|
|
source "drivers/gpu/drm/i2c/Kconfig"
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DRM_TDFX
|
|
|
|
|
tristate "3dfx Banshee/Voodoo3+"
|
|
|
|
|
depends on DRM && PCI
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
|
|
|
|
|
graphics card. If M is selected, the module will be called tdfx.
|
|
|
|
|
|
|
|
|
|
config DRM_R128
|
|
|
|
|
tristate "ATI Rage 128"
|
|
|
|
|
depends on DRM && PCI
|
2009-08-23 17:37:26 +00:00
|
|
|
select FW_LOADER
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have an ATI Rage 128 graphics card. If M
|
|
|
|
|
is selected, the module will be called r128. AGP support for
|
|
|
|
|
this card is strongly suggested (unless you have a PCI version).
|
|
|
|
|
|
|
|
|
|
config DRM_RADEON
|
|
|
|
|
tristate "ATI Radeon"
|
|
|
|
|
depends on DRM && PCI
|
2009-06-05 12:42:42 +00:00
|
|
|
select FB_CFB_FILLRECT
|
|
|
|
|
select FB_CFB_COPYAREA
|
|
|
|
|
select FB_CFB_IMAGEBLIT
|
2009-08-29 13:53:51 +00:00
|
|
|
select FW_LOADER
|
2009-09-08 01:09:50 +00:00
|
|
|
select DRM_KMS_HELPER
|
|
|
|
|
select DRM_TTM
|
2010-05-21 05:41:20 +00:00
|
|
|
select POWER_SUPPLY
|
2010-07-02 16:58:16 +00:00
|
|
|
select HWMON
|
2013-01-21 12:58:46 +00:00
|
|
|
select BACKLIGHT_CLASS_DEVICE
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have an ATI Radeon graphics card. There
|
|
|
|
|
are both PCI and AGP versions. You don't need to choose this to
|
2006-03-20 19:23:13 +00:00
|
|
|
run the Radeon in plain VGA mode.
|
2007-11-05 02:50:58 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
If M is selected, the module will be called radeon.
|
|
|
|
|
|
2010-02-01 01:35:47 +00:00
|
|
|
source "drivers/gpu/drm/radeon/Kconfig"
|
|
|
|
|
|
2012-03-16 08:19:14 +00:00
|
|
|
source "drivers/gpu/drm/nouveau/Kconfig"
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DRM_I810
|
|
|
|
|
tristate "Intel I810"
|
2011-01-25 22:17:15 +00:00
|
|
|
# !PREEMPT because of missing ioctl locking
|
|
|
|
|
depends on DRM && AGP && AGP_INTEL && (!PREEMPT || BROKEN)
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have an Intel I810 graphics card. If M is
|
|
|
|
|
selected, the module will be called i810. AGP support is required
|
|
|
|
|
for this driver to work.
|
|
|
|
|
|
|
|
|
|
config DRM_I915
|
2011-01-25 22:17:16 +00:00
|
|
|
tristate "Intel 8xx/9xx/G3x/G4x/HD Graphics"
|
|
|
|
|
depends on DRM
|
|
|
|
|
depends on AGP
|
2009-06-19 03:22:19 +00:00
|
|
|
depends on AGP_INTEL
|
2011-01-20 10:03:24 +00:00
|
|
|
# we need shmfs for the swappable backing store, and in particular
|
|
|
|
|
# the shmem_readpage() which depends upon tmpfs
|
2009-11-22 15:40:31 +00:00
|
|
|
select SHMEM
|
2011-01-20 10:03:24 +00:00
|
|
|
select TMPFS
|
2009-09-08 01:08:32 +00:00
|
|
|
select DRM_KMS_HELPER
|
2008-12-04 06:43:14 +00:00
|
|
|
select FB_CFB_FILLRECT
|
|
|
|
|
select FB_CFB_COPYAREA
|
|
|
|
|
select FB_CFB_IMAGEBLIT
|
2009-05-30 01:11:27 +00:00
|
|
|
# i915 depends on ACPI_VIDEO when ACPI is enabled
|
|
|
|
|
# but for select to work, need to select ACPI_VIDEO's dependencies, ick
|
2011-10-31 19:51:30 +00:00
|
|
|
select BACKLIGHT_LCD_SUPPORT if ACPI
|
2009-05-30 01:11:27 +00:00
|
|
|
select BACKLIGHT_CLASS_DEVICE if ACPI
|
2011-04-12 10:27:47 +00:00
|
|
|
select VIDEO_OUTPUT_CONTROL if ACPI
|
2009-05-30 01:11:27 +00:00
|
|
|
select INPUT if ACPI
|
|
|
|
|
select ACPI_VIDEO if ACPI
|
2009-09-10 22:28:03 +00:00
|
|
|
select ACPI_BUTTON if ACPI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2011-01-25 22:17:16 +00:00
|
|
|
Choose this option if you have a system that has "Intel Graphics
|
|
|
|
|
Media Accelerator" or "HD Graphics" integrated graphics,
|
|
|
|
|
including 830M, 845G, 852GM, 855GM, 865G, 915G, 945G, 965G,
|
|
|
|
|
G35, G41, G43, G45 chipsets and Celeron, Pentium, Core i3,
|
|
|
|
|
Core i5, Core i7 as well as Atom CPUs with integrated graphics.
|
|
|
|
|
If M is selected, the module will be called i915. AGP support
|
|
|
|
|
is required for this driver to work. This driver is used by
|
|
|
|
|
the Intel driver in X.org 6.8 and XFree86 4.4 and above. It
|
|
|
|
|
replaces the older i830 module that supported a subset of the
|
|
|
|
|
hardware in older X.org releases.
|
|
|
|
|
|
|
|
|
|
Note that the older i810/i815 chipsets require the use of the
|
|
|
|
|
i810 driver instead, and the Atom z5xx series has an entirely
|
|
|
|
|
different implementation.
|
2007-11-05 02:50:58 +00:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
config DRM_I915_KMS
|
|
|
|
|
bool "Enable modesetting on intel by default"
|
|
|
|
|
depends on DRM_I915
|
|
|
|
|
help
|
2009-02-18 22:48:38 +00:00
|
|
|
Choose this option if you want kernel modesetting enabled by default,
|
|
|
|
|
and you have a new enough userspace to support this. Running old
|
|
|
|
|
userspaces with this enabled will cause pain. Note that this causes
|
|
|
|
|
the driver to bind to PCI devices, which precludes loading things
|
|
|
|
|
like intelfb.
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DRM_MGA
|
|
|
|
|
tristate "Matrox g200/g400"
|
2010-07-08 21:43:27 +00:00
|
|
|
depends on DRM && PCI
|
2009-08-23 17:34:25 +00:00
|
|
|
select FW_LOADER
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have a Matrox G200, G400 or G450 graphics
|
|
|
|
|
card. If M is selected, the module will be called mga. AGP
|
|
|
|
|
support is required for this driver to work.
|
|
|
|
|
|
|
|
|
|
config DRM_SIS
|
|
|
|
|
tristate "SiS video cards"
|
|
|
|
|
depends on DRM && AGP
|
2008-08-24 07:11:22 +00:00
|
|
|
depends on FB_SIS || FB_SIS=n
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2007-11-05 02:50:58 +00:00
|
|
|
Choose this option if you have a SiS 630 or compatible video
|
2005-04-16 22:20:36 +00:00
|
|
|
chipset. If M is selected the module will be called sis. AGP
|
|
|
|
|
support is required for this driver to work.
|
|
|
|
|
|
2005-06-28 12:48:56 +00:00
|
|
|
config DRM_VIA
|
|
|
|
|
tristate "Via unichrome video cards"
|
2010-07-08 21:43:27 +00:00
|
|
|
depends on DRM && PCI
|
2005-06-28 12:48:56 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have a Via unichrome or compatible video
|
|
|
|
|
chipset. If M is selected the module will be called via.
|
|
|
|
|
|
2005-08-07 05:43:54 +00:00
|
|
|
config DRM_SAVAGE
|
|
|
|
|
tristate "Savage video cards"
|
2010-07-08 21:43:27 +00:00
|
|
|
depends on DRM && PCI
|
2005-08-07 05:43:54 +00:00
|
|
|
help
|
|
|
|
|
Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
|
|
|
|
|
chipset. If M is selected the module will be called savage.
|
2011-10-04 10:19:01 +00:00
|
|
|
|
2011-10-11 08:42:51 +00:00
|
|
|
source "drivers/gpu/drm/exynos/Kconfig"
|
|
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/vmwgfx/Kconfig"
|
2011-11-03 18:22:48 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/gma500/Kconfig"
|
|
|
|
|
|
2010-12-14 21:14:24 +00:00
|
|
|
source "drivers/gpu/drm/udl/Kconfig"
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 13:40:04 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/ast/Kconfig"
|
|
|
|
|
|
2012-04-17 14:01:25 +00:00
|
|
|
source "drivers/gpu/drm/mgag200/Kconfig"
|
2012-04-17 13:12:29 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/cirrus/Kconfig"
|
2012-04-26 11:53:59 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/shmobile/Kconfig"
|
2012-11-15 21:28:22 +00:00
|
|
|
|
2013-02-11 17:43:09 +00:00
|
|
|
source "drivers/gpu/drm/omapdrm/Kconfig"
|
2013-02-20 23:31:47 +00:00
|
|
|
|
2013-01-08 21:04:28 +00:00
|
|
|
source "drivers/gpu/drm/tilcdc/Kconfig"
|
drm: add new QXL driver. (v1.4)
QXL is a paravirtual graphics device used by the Spice virtual desktop
interface.
The drivers uses GEM and TTM to manage memory, the qxl hw fencing however
is quite different than normal TTM expects, we have to keep track of a number
of non-linear fence ids per bo that we need to have released by the hardware.
The releases are freed from a workqueue that wakes up and processes the
release ring.
releases are suballocated from a BO, there are 3 release categories, drawables,
surfaces and cursor cmds. The hw also has 3 rings for commands, cursor and release handling.
The hardware also have a surface id tracking mechnaism and the driver encapsulates it completely inside the kernel, userspace never sees the actual hw surface
ids.
This requires a newer version of the QXL userspace driver, so shouldn't be
enabled until that has been placed into your distro of choice.
Authors: Dave Airlie, Alon Levy
v1.1: fixup some issues in the ioctl interface with padding
v1.2: add module device table
v1.3: fix nomodeset, fbcon leak, dumb bo create, release ring irq,
don't try flush release ring (broken hw), fix -modesetting.
v1.4: fbcon cpu usage reduction + suitable accel flags.
Signed-off-by: Alon Levy <alevy@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2013-02-25 04:47:55 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/qxl/Kconfig"
|
