From 6f9c84dc88fc4fcc351ec91b2bb9ff5ae6e4f1a6 Mon Sep 17 00:00:00 2001 From: Stefan Tauner Date: Mon, 30 Jul 2018 17:56:28 +0200 Subject: Documentation/gfx: explain port mapping in libgfxinit's config Change-Id: Id24ded4ba641aade66468313e33ede1a82090f05 Signed-off-by: Stefan Tauner Reviewed-on: https://review.coreboot.org/27854 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel Reviewed-by: Patrick Georgi --- Documentation/gfx/libgfxinit.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'Documentation/gfx') diff --git a/Documentation/gfx/libgfxinit.md b/Documentation/gfx/libgfxinit.md index 472e967972..2086a90529 100644 --- a/Documentation/gfx/libgfxinit.md +++ b/Documentation/gfx/libgfxinit.md @@ -76,8 +76,11 @@ know through which interface the EDID can be queried: select GFX_GMA_ANALOG_I2C_HDMI_D Beside Kconfig options, *libgfxinit* needs to know which ports are -implemented on a board and should be probed for displays. Each -board has to implement the package `GMA.Mainboard` with a list: +implemented on a board and should be probed for displays. The mapping +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; -- cgit v1.2.3