diff options
| author | Furquan Shaikh <furquan@chromium.org> | 2017-10-28 00:09:33 -0700 |
|---|---|---|
| committer | Furquan Shaikh <furquan@google.com> | 2017-10-29 01:59:18 +0000 |
| commit | 2d65d2043664fc5b04a59ac1a1b18282228e1b41 (patch) | |
| tree | 9914bff629a59e9259bb7f25586f16b3cecbe19d /util | |
| parent | 504d1eff4bd324915f5c44223ab03086b0cbbd2c (diff) | |
arch/x86: Restore forwarding table on resume for non EARLY_EBDA_INIT
In commit c06a3f72 (arch/x86: initialize EBDA in S3 and S0/S5 path),
BDA and EBDA are wiped in the resume path. It results in coreboot
forwarding table address being wiped out since it is stored in the
BDA. This issue was resolved for platforms using EARLY_EBDA_INIT in
commit f46a9a0d (arch/x86: restore forwarding table on resume for
EARLY_EBDA_INIT). However platforms that do not use EARLY_EBDA_INIT
still run into the same issue and hence cbmem does not work on
resume. This change fixes the issue by using the stash/restore of
forwarding table address for all platforms using BDA.
BUG=b:68412690
TEST=Verified that cbmem works on S3 resume for coral.
Change-Id: I42ae2ccb0b4ce8e989b1032d82b9bb34d0d84db0
Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: https://review.coreboot.org/22207
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions