Documentation/gfx: explain port mapping in libgfxinit's config

Change-Id: Id24ded4ba641aade66468313e33ede1a82090f05
Signed-off-by: Stefan Tauner <stefan.tauner@gmx.at>
Reviewed-on: https://review.coreboot.org/27854
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
Stefan Tauner 2018-07-30 17:56:28 +02:00 committed by Patrick Georgi
parent e08ffa615e
commit 6f9c84dc88
1 changed files with 5 additions and 2 deletions

View File

@ -76,8 +76,11 @@ know through which interface the EDID can be queried:
select GFX_GMA_ANALOG_I2C_HDMI_D select GFX_GMA_ANALOG_I2C_HDMI_D
Beside Kconfig options, *libgfxinit* needs to know which ports are Beside Kconfig options, *libgfxinit* needs to know which ports are
implemented on a board and should be probed for displays. Each implemented on a board and should be probed for displays. The mapping
board has to implement the package `GMA.Mainboard` with a list: between the physical ports and these entries depends on the hardware
implementation and can be recovered by testing or studying the output
of `intelvbttool` or `intel_vbt_decode`.
Each board has to implement the package `GMA.Mainboard` with a list:
ports : HW.GFX.GMA.Display_Probing.Port_List; ports : HW.GFX.GMA.Display_Probing.Port_List;