2005-04-17 02:20:36 +04:00
|
|
|
#
|
|
|
|
|
# Drm device configuration
|
|
|
|
|
#
|
|
|
|
|
# This driver provides support for the
|
|
|
|
|
# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
|
|
|
|
|
#
|
2007-10-16 12:29:39 +04:00
|
|
|
menuconfig DRM
|
2005-04-17 02:20:36 +04:00
|
|
|
tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
|
2010-05-27 23:40:25 +04:00
|
|
|
depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU
|
2008-12-13 11:21:08 +03:00
|
|
|
select I2C
|
|
|
|
|
select I2C_ALGOBIT
|
2010-05-07 10:42:51 +04:00
|
|
|
select SLOW_WORK
|
2005-04-17 02:20:36 +04: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 23:40:25 +04:00
|
|
|
(/dev/agpgart) support if it is available for your platform.
|
2005-04-17 02:20:36 +04:00
|
|
|
|
2009-09-08 05:08:32 +04:00
|
|
|
config DRM_KMS_HELPER
|
2009-09-07 09:45:33 +04:00
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
select FB
|
2009-09-08 05:08:32 +04:00
|
|
|
select FRAMEBUFFER_CONSOLE if !EMBEDDED
|
2009-09-07 09:45:33 +04:00
|
|
|
help
|
2009-09-08 05:08:32 +04:00
|
|
|
FB and CRTC helpers for KMS drivers.
|
2009-09-07 09:45:33 +04:00
|
|
|
|
2009-06-10 17:20:19 +04:00
|
|
|
config DRM_TTM
|
2009-06-05 16:42:42 +04:00
|
|
|
tristate
|
2009-06-10 17:20:19 +04: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.
|
|
|
|
|
|
2005-04-17 02:20:36 +04: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 21:37:26 +04:00
|
|
|
select FW_LOADER
|
2005-04-17 02:20:36 +04: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 16:42:42 +04:00
|
|
|
select FB_CFB_FILLRECT
|
|
|
|
|
select FB_CFB_COPYAREA
|
|
|
|
|
select FB_CFB_IMAGEBLIT
|
2009-08-29 17:53:51 +04:00
|
|
|
select FW_LOADER
|
2009-09-08 05:09:50 +04:00
|
|
|
select DRM_KMS_HELPER
|
|
|
|
|
select DRM_TTM
|
2010-05-21 09:41:20 +04:00
|
|
|
select POWER_SUPPLY
|
2005-04-17 02:20:36 +04: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 22:23:13 +03:00
|
|
|
run the Radeon in plain VGA mode.
|
2007-11-05 05:50:58 +03:00
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
If M is selected, the module will be called radeon.
|
|
|
|
|
|
2010-02-01 04:35:47 +03:00
|
|
|
source "drivers/gpu/drm/radeon/Kconfig"
|
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
config DRM_I810
|
|
|
|
|
tristate "Intel I810"
|
|
|
|
|
depends on DRM && AGP && AGP_INTEL
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Intel 830M, 845G, 852GM, 855GM, 865G"
|
|
|
|
|
depends on DRM && AGP && AGP_INTEL
|
|
|
|
|
optional
|
|
|
|
|
|
|
|
|
|
config DRM_I830
|
|
|
|
|
tristate "i830 driver"
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you have a system that has Intel 830M, 845G,
|
|
|
|
|
852GM, 855GM or 865G integrated graphics. If M is selected, the
|
|
|
|
|
module will be called i830. AGP support is required for this driver
|
2006-08-12 10:03:52 +04:00
|
|
|
to work. This driver is used by the older X releases X.org 6.7 and
|
|
|
|
|
XFree86 4.3. If unsure, build this and i915 as modules and the X server
|
|
|
|
|
will load the correct one.
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
config DRM_I915
|
2009-05-30 05:11:27 +04:00
|
|
|
tristate "i915 driver"
|
2009-06-19 07:22:19 +04:00
|
|
|
depends on AGP_INTEL
|
2009-11-22 18:40:31 +03:00
|
|
|
select SHMEM
|
2009-09-08 05:08:32 +04:00
|
|
|
select DRM_KMS_HELPER
|
2008-12-04 09:43:14 +03:00
|
|
|
select FB_CFB_FILLRECT
|
|
|
|
|
select FB_CFB_COPYAREA
|
|
|
|
|
select FB_CFB_IMAGEBLIT
|
2009-05-30 05:11:27 +04:00
|
|
|
# i915 depends on ACPI_VIDEO when ACPI is enabled
|
|
|
|
|
# but for select to work, need to select ACPI_VIDEO's dependencies, ick
|
|
|
|
|
select VIDEO_OUTPUT_CONTROL if ACPI
|
|
|
|
|
select BACKLIGHT_CLASS_DEVICE if ACPI
|
|
|
|
|
select INPUT if ACPI
|
|
|
|
|
select ACPI_VIDEO if ACPI
|
2009-09-11 02:28:03 +04:00
|
|
|
select ACPI_BUTTON if ACPI
|
2005-04-17 02:20:36 +04:00
|
|
|
help
|
|
|
|
|
Choose this option if you have a system that has Intel 830M, 845G,
|
|
|
|
|
852GM, 855GM 865G or 915G integrated graphics. If M is selected, the
|
|
|
|
|
module will be called i915. AGP support is required for this driver
|
2006-08-12 10:03:52 +04:00
|
|
|
to work. This driver is used by the Intel driver in X.org 6.8 and
|
2007-11-05 05:50:58 +03:00
|
|
|
XFree86 4.4 and above. If unsure, build this and i830 as modules and
|
2006-08-12 10:03:52 +04:00
|
|
|
the X server will load the correct one.
|
2007-11-05 05:50:58 +03: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-08 01:24:08 +03:00
|
|
|
config DRM_I915_KMS
|
|
|
|
|
bool "Enable modesetting on intel by default"
|
|
|
|
|
depends on DRM_I915
|
|
|
|
|
help
|
2009-02-19 01:48:38 +03: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-08 01:24:08 +03:00
|
|
|
|
2009-02-19 01:48:38 +03:00
|
|
|
endchoice
|
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-08 01:24:08 +03:00
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
config DRM_MGA
|
|
|
|
|
tristate "Matrox g200/g400"
|
Add support for PCI MGA cards to MGA DRM.
This patch adds serveral new ioctls and a new query to get_param query to
support PCI MGA cards.
Two ioctls were added to implement interrupt based waiting. With this change,
the client-side driver no longer needs to map the primary DMA region or the
MMIO region. Previously, end-of-frame waiting was done by busy waiting in the
client-side driver until one of the MMIO registers (the current DMA pointer)
matched a pointer to the end of primary DMA space. By using interrupts, the
busy waiting and the extra mappings are removed.
A third ioctl was added to bootstrap DMA. This ioctl, which is used by the
X-server, moves a *LOT* of code from the X-server into the kernel. This allows
the kernel to do whatever needs to be done to setup DMA buffers. The entire
process and the locations of the buffers are hidden from user-mode.
Additionally, a get_param query was added to differentiate between G4x0 cards
and G550 cards. A gap was left in the numbering sequence so that, if needed,
G450 cards could be distinguished from G400 cards. According to Ville
Syrjälä, the G4x0 cards and the G550 cards handle anisotropic filtering
differently. This seems the most compatible way to let the client-side driver
know which card it's own. Doing this very small change now eliminates the
need to bump the DRM minor version twice.
http://marc.theaimsgroup.com/?l=dri-devel&m=106625815319773&w=2
(airlied - this may not work at this point, I think the follow on buffer
cleanup patches will be needed)
From: Ian Romanick <idr@us.ibm.com>
Signed-off-by: Dave Airlie <airlied@linux.ie>
2005-07-10 12:20:09 +04:00
|
|
|
depends on DRM
|
2009-08-23 21:34:25 +04:00
|
|
|
select FW_LOADER
|
2005-04-17 02:20:36 +04: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 11:11:22 +04:00
|
|
|
depends on FB_SIS || FB_SIS=n
|
2005-04-17 02:20:36 +04:00
|
|
|
help
|
2007-11-05 05:50:58 +03:00
|
|
|
Choose this option if you have a SiS 630 or compatible video
|
2005-04-17 02:20:36 +04:00
|
|
|
chipset. If M is selected the module will be called sis. AGP
|
|
|
|
|
support is required for this driver to work.
|
|
|
|
|
|
2005-06-28 16:48:56 +04:00
|
|
|
config DRM_VIA
|
|
|
|
|
tristate "Via unichrome video cards"
|
|
|
|
|
depends on DRM
|
|
|
|
|
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 09:43:54 +04:00
|
|
|
config DRM_SAVAGE
|
|
|
|
|
tristate "Savage video cards"
|
|
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
|
|
|
|
|
chipset. If M is selected the module will be called savage.
|
