diff options
| author | Jonathan Neuschäfer <j.neuschaefer@gmx.net> | 2020-02-14 20:41:32 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2020-02-19 14:10:31 +0300 |
| commit | 1733ec77d34059cd67a7b9677fe2fd3ef977afb3 (patch) | |
| tree | 4812255b4de26e77d626d0baf1c6e6009352b836 /Documentation/driver-api | |
| parent | 965fc39f73932041441e03730db31516e285b61a (diff) | |
| download | linux-1733ec77d34059cd67a7b9677fe2fd3ef977afb3.tar.xz | |
docs: driver-api: edid: Fix list formatting
Without the empty lines, Sphinx renders the list as part of the running
text.
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/driver-api')
| -rw-r--r-- | Documentation/driver-api/edid.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/driver-api/edid.rst b/Documentation/driver-api/edid.rst index b1b5acd501ed..7dc07942ceb2 100644 --- a/Documentation/driver-api/edid.rst +++ b/Documentation/driver-api/edid.rst @@ -11,11 +11,13 @@ Today, with the advent of Kernel Mode Setting, a graphics board is either correctly working because all components follow the standards - or the computer is unusable, because the screen remains dark after booting or it displays the wrong area. Cases when this happens are: + - The graphics board does not recognize the monitor. - The graphics board is unable to detect any EDID data. - The graphics board incorrectly forwards EDID data to the driver. - The monitor sends no or bogus EDID data. - A KVM sends its own EDID data instead of querying the connected monitor. + Adding the kernel parameter "nomodeset" helps in most cases, but causes restrictions later on. |