summaryrefslogtreecommitdiff
path: root/Documentation/gfx
diff options
context:
space:
mode:
authorNico Huber <nico.h@gmx.de>2017-07-16 16:40:41 +0200
committerNico Huber <nico.h@gmx.de>2017-10-28 19:46:17 +0000
commit504d1eff4bd324915f5c44223ab03086b0cbbd2c (patch)
treebde35bdf0c7bd59456af336735c4e5c69bfc71ae /Documentation/gfx
parent18228168a5e5ada33390ca96ef4b6ee80a509a89 (diff)
downloadcoreboot-504d1eff4bd324915f5c44223ab03086b0cbbd2c.tar.xz
3rdparty/lib{hwbase,gfxinit}: Update to latest master
Simplifies our C interface function gma_gfxinit(), due to the following changes: * *libgfxinit* knows about the underlying PCI device now and can probe MMIO addresses by itself. * The framebuffer mapping is now completely handled inside the library where we validate that we neither overflow - the stolen memory, - the GTT address space, the GTT itself nor - the aperture window (i.e. resource2 of the PCI device) that we use to access the framebuffer. Other changes: * Fixes and a quirk for DP training. * Fix for DP-VGA adapters that report an analog display in EDID. * Fixes for Skylake support with coreboot. * DDI Buffer drive-strength configuration for Haswell, Broadwell and Skylake. * `gfx_test` can now be run from X windows (with glitches). * Compatibility with GCC 7 and SPARK GPL 2017. TEST=Booted lenovo/t420 and verified that everything works as usual. Change-Id: I001ba973d864811503410579fd7ad55ab8612759 Signed-off-by: Nico Huber <nico.h@gmx.de> Reviewed-on: https://review.coreboot.org/20606 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
Diffstat (limited to 'Documentation/gfx')
-rw-r--r--Documentation/gfx/libgfxinit.md13
1 files changed, 2 insertions, 11 deletions
diff --git a/Documentation/gfx/libgfxinit.md b/Documentation/gfx/libgfxinit.md
index 8e7473df89..472e967972 100644
--- a/Documentation/gfx/libgfxinit.md
+++ b/Documentation/gfx/libgfxinit.md
@@ -39,22 +39,13 @@ GMA: Hook-up in Chipset Initialization
Both configurations described above implement a procedure
`GMA.gfxinit()`:
- procedure gfxinit
- (mmio_base : in word64;
- linear_fb : in word64;
- phys_fb : in word32;
- lightup_ok : out int);
+ procedure gfxinit (lightup_ok : out int);
This procedure is exported as the C function `gma_gfxinit()` as
follows:
- void gma_gfxinit(uint64_t mmio_base, uint64_t linear_fb,
- uint32_t phys_fb, int *lightup_ok);
+ void gma_gfxinit(int *lightup_ok);
-* `mmio_base`: the base address of the GMA's MMIO resource
-* `linear_fb`: the base address of the GMA's GTT window resource
-* `phys_fb`: the physical address where the framebuffer should be
- stored (usually the GMA's stolen memory)
* `lightup_ok`: returns whether the initialization succeeded `1` or
failed `0`. Currently, only the case that no display
could be found counts as failure. A failure at a la-