diff options
author | Lubomir Rintel <lkundrak@v3.sk> | 2017-12-28 01:48:09 +0100 |
---|---|---|
committer | Kyösti Mälkki <kyosti.malkki@gmail.com> | 2018-05-16 06:19:34 +0000 |
commit | d8ec973fd24e091d0038d7060bfb516bad7534f0 (patch) | |
tree | 0945e83c1648cf6dc10569d863543b01de4362e8 /src/northbridge/via/vx900/vx900.h | |
parent | faafbfb81e28df373d3319a6378e73cb37c9ced3 (diff) |
vx900: Move to EARLY_CBMEM_INIT
To calculate the CBMEM address we need to determine the framebuffer
size early in the ROMSTAGE. We now do the calculation before
cbmem_recovery() and configure the memory controller right away.
If the calculation was done from cbmem_top() instead, we'd loose some
logging that seems useful, since printk() would recurse to cbmem_top() too
with CONSOLE_CBMEM enabled.
If we didn't configure the memory controller at this point, we'd
need to store the result somewhere else. However, CAR_GLOBAL is not
practical at this point, because calling car_get_var() from cbmem_top()
would recurse back to cbmem_top().
Change-Id: Ib9ae0f97f9f769a20a610f8d76f14165fb924042
Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
Reviewed-on: https://review.coreboot.org/25798
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Diffstat (limited to 'src/northbridge/via/vx900/vx900.h')
-rw-r--r-- | src/northbridge/via/vx900/vx900.h | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/northbridge/via/vx900/vx900.h b/src/northbridge/via/vx900/vx900.h index fe756f9665..cb7bca9703 100644 --- a/src/northbridge/via/vx900/vx900.h +++ b/src/northbridge/via/vx900/vx900.h @@ -31,7 +31,10 @@ #include <console/console.h> -u32 chrome9hd_fb_size(void); +u32 vx900_get_tolm(void); +void vx900_set_chrome9hd_fb_size(u32 size_mb); +u8 vx900_get_chrome9hd_fb_pow(void); +u32 vx900_get_chrome9hd_fb_size(void); u8 vx900_int15_get_5f18_bl(void); uint64_t get_uma_memory_base(void); |