mirror of
https://github.com/FEX-Emu/linux.git
synced 2024-12-23 18:07:03 +00:00
da0df92b57
Broken monitors and/or broken graphic boards may send erroneous or no EDID data. This also applies to broken KVM devices that are unable to correctly forward the EDID data of the connected monitor but invent their own fantasy data. This patch allows to specify an EDID data set to be used instead of probing the monitor for it. It contains built-in data sets of frequently used screen resolutions. In addition, a particular EDID data set may be provided in the /lib/firmware directory and loaded via the firmware interface. The name is passed to the kernel as module parameter of the drm_kms_helper module either when loaded options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel commandline parameter drm_kms_helper.edid_firmware=edid/1280x1024.bin It is also possible to restrict the usage of a specified EDID data set to a particular connector. This is done by prepending the name of the connector to the name of the EDID data set using the syntax edid_firmware=[<connector>:]<edid> such as, for example, edid_firmware=DVI-I-1:edid/1920x1080.bin in which case no other connector will be affected. The built-in data sets are Resolution Name -------------------------------- 1024x768 edid/1024x768.bin 1280x1024 edid/1280x1024.bin 1680x1050 edid/1680x1050.bin 1920x1080 edid/1920x1080.bin They are ignored, if a file with the same name is available in the /lib/firmware directory. The built-in EDID data sets are based on standard timings that may not apply to a particular monitor and even crash it. Ideally, EDID data of the connected monitor should be used. They may be obtained through the drm/cardX/cardX-<connector>/edid entry in the /sys/devices PCI directory of a correctly working graphics adapter. It is even possible to specify the name of an EDID data set on-the-fly via the /sys/module interface, e.g. echo edid/myedid.bin >/sys/module/drm_kms_helper/parameters/edid_firmware The new screen mode is considered when the related kernel function is called for the first time after the change. Such calls are made when the X server is started or when the display settings dialog is opened in an already running X server. Signed-off-by: Carsten Emde <C.Emde@osadl.org> Signed-off-by: Dave Airlie <airlied@redhat.com>
186 lines
6.0 KiB
Plaintext
186 lines
6.0 KiB
Plaintext
#
|
|
# Drm device configuration
|
|
#
|
|
# This driver provides support for the
|
|
# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
|
|
#
|
|
menuconfig DRM
|
|
tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
|
|
depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU
|
|
select I2C
|
|
select I2C_ALGOBIT
|
|
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
|
|
(/dev/agpgart) support if it is available for your platform.
|
|
|
|
config DRM_USB
|
|
tristate
|
|
depends on DRM
|
|
select USB
|
|
|
|
config DRM_KMS_HELPER
|
|
tristate
|
|
depends on DRM
|
|
select FB
|
|
select FRAMEBUFFER_CONSOLE if !EXPERT
|
|
select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
|
|
help
|
|
FB and CRTC helpers for KMS drivers.
|
|
|
|
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.
|
|
|
|
config DRM_TTM
|
|
tristate
|
|
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.
|
|
|
|
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
|
|
select FW_LOADER
|
|
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
|
|
select FB_CFB_FILLRECT
|
|
select FB_CFB_COPYAREA
|
|
select FB_CFB_IMAGEBLIT
|
|
select FW_LOADER
|
|
select DRM_KMS_HELPER
|
|
select DRM_TTM
|
|
select POWER_SUPPLY
|
|
select HWMON
|
|
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
|
|
run the Radeon in plain VGA mode.
|
|
|
|
If M is selected, the module will be called radeon.
|
|
|
|
source "drivers/gpu/drm/radeon/Kconfig"
|
|
|
|
config DRM_I810
|
|
tristate "Intel I810"
|
|
# !PREEMPT because of missing ioctl locking
|
|
depends on DRM && AGP && AGP_INTEL && (!PREEMPT || BROKEN)
|
|
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
|
|
tristate "Intel 8xx/9xx/G3x/G4x/HD Graphics"
|
|
depends on DRM
|
|
depends on AGP
|
|
depends on AGP_INTEL
|
|
# we need shmfs for the swappable backing store, and in particular
|
|
# the shmem_readpage() which depends upon tmpfs
|
|
select SHMEM
|
|
select TMPFS
|
|
select DRM_KMS_HELPER
|
|
select FB_CFB_FILLRECT
|
|
select FB_CFB_COPYAREA
|
|
select FB_CFB_IMAGEBLIT
|
|
# i915 depends on ACPI_VIDEO when ACPI is enabled
|
|
# but for select to work, need to select ACPI_VIDEO's dependencies, ick
|
|
select BACKLIGHT_LCD_SUPPORT if ACPI
|
|
select BACKLIGHT_CLASS_DEVICE if ACPI
|
|
select VIDEO_OUTPUT_CONTROL if ACPI
|
|
select INPUT if ACPI
|
|
select ACPI_VIDEO if ACPI
|
|
select ACPI_BUTTON if ACPI
|
|
help
|
|
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.
|
|
|
|
config DRM_I915_KMS
|
|
bool "Enable modesetting on intel by default"
|
|
depends on DRM_I915
|
|
help
|
|
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.
|
|
|
|
config DRM_MGA
|
|
tristate "Matrox g200/g400"
|
|
depends on DRM && PCI
|
|
select FW_LOADER
|
|
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
|
|
depends on FB_SIS || FB_SIS=n
|
|
help
|
|
Choose this option if you have a SiS 630 or compatible video
|
|
chipset. If M is selected the module will be called sis. AGP
|
|
support is required for this driver to work.
|
|
|
|
config DRM_VIA
|
|
tristate "Via unichrome video cards"
|
|
depends on DRM && PCI
|
|
help
|
|
Choose this option if you have a Via unichrome or compatible video
|
|
chipset. If M is selected the module will be called via.
|
|
|
|
config DRM_SAVAGE
|
|
tristate "Savage video cards"
|
|
depends on DRM && PCI
|
|
help
|
|
Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
|
|
chipset. If M is selected the module will be called savage.
|
|
|
|
source "drivers/gpu/drm/exynos/Kconfig"
|
|
|
|
source "drivers/gpu/drm/vmwgfx/Kconfig"
|
|
|
|
source "drivers/gpu/drm/gma500/Kconfig"
|
|
|
|
source "drivers/gpu/drm/udl/Kconfig"
|