blob: b1b5acd501ed4bf44858cd2f9c9629edf211f144 [file] [log] [blame]
Mauro Carvalho Chehabbaa293e2019-06-27 15:39:22 -03001.. SPDX-License-Identifier: GPL-2.0
Mauro Carvalho Chehaba2f405a2019-06-12 14:53:04 -03002
3====
4EDID
5====
6
Carsten Emdeda0df922012-03-18 22:37:33 +01007In the good old days when graphics parameters were configured explicitly
8in a file called xorg.conf, even broken hardware could be managed.
9
10Today, with the advent of Kernel Mode Setting, a graphics board is
11either correctly working because all components follow the standards -
12or the computer is unusable, because the screen remains dark after
13booting or it displays the wrong area. Cases when this happens are:
14- The graphics board does not recognize the monitor.
15- The graphics board is unable to detect any EDID data.
16- The graphics board incorrectly forwards EDID data to the driver.
17- The monitor sends no or bogus EDID data.
18- A KVM sends its own EDID data instead of querying the connected monitor.
19Adding the kernel parameter "nomodeset" helps in most cases, but causes
20restrictions later on.
21
22As a remedy for such situations, the kernel configuration item
23CONFIG_DRM_LOAD_EDID_FIRMWARE was introduced. It allows to provide an
24individually prepared or corrected EDID data set in the /lib/firmware
25directory from where it is loaded via the firmware interface. The code
26(see drivers/gpu/drm/drm_edid_load.c) contains built-in data sets for
Daniel Thompson4cbe1bfa2014-05-23 16:01:43 +010027commonly used screen resolutions (800x600, 1024x768, 1280x1024, 1600x1200,
Carsten Emde8091ee52013-04-06 16:01:34 +0000281680x1050, 1920x1080) as binary blobs, but the kernel source tree does
29not contain code to create these data. In order to elucidate the origin
30of the built-in binary EDID blobs and to facilitate the creation of
31individual data for a specific misbehaving monitor, commented sources
32and a Makefile environment are given here.
Carsten Emdeda0df922012-03-18 22:37:33 +010033
34To create binary EDID and C source code files from the existing data
35material, simply type "make".
36
Carsten Emdebac4b7c2012-07-19 15:54:25 +000037If you want to create your own EDID file, copy the file 1024x768.S,
38replace the settings with your own data and add a new target to the
39Makefile. Please note that the EDID data structure expects the timing
40values in a different way as compared to the standard X11 format.
41
42X11:
Mauro Carvalho Chehaba2f405a2019-06-12 14:53:04 -030043 HTimings:
44 hdisp hsyncstart hsyncend htotal
45 VTimings:
46 vdisp vsyncstart vsyncend vtotal
Carsten Emdebac4b7c2012-07-19 15:54:25 +000047
Mauro Carvalho Chehaba2f405a2019-06-12 14:53:04 -030048EDID::
Carsten Emdebac4b7c2012-07-19 15:54:25 +000049
Mauro Carvalho Chehaba2f405a2019-06-12 14:53:04 -030050 #define XPIX hdisp
51 #define XBLANK htotal-hdisp
52 #define XOFFSET hsyncstart-hdisp
53 #define XPULSE hsyncend-hsyncstart
54
55 #define YPIX vdisp
56 #define YBLANK vtotal-vdisp
57 #define YOFFSET vsyncstart-vdisp
58 #define YPULSE vsyncend-vsyncstart