UPSTREAM: drivers/intel/fsp2_0: load and relocate FSPS in cbmem
The FSPS component loading was just loading to any memory address listed in the header. That could be anywhere in the address space including ramstage itself -- let alone corrupting the OS memory on S3 resume. Remedy this by loading and relocating FSPS into cbmem. The UEFI 2.4 header files include path are selected to provide the types necessary for FSP relocation. BUG=chrome-os-partner:52679 BRANCH=None TEST=None Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/15742 Tested-by: build bot (Jenkins) Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Andrey Petrov <andrey.petrov@intel.com> Reviewed-by: John Zhao <john.zhao@intel.com> Change-Id: Iaba103190731fc229566a3b0231cf967522040db Reviewed-on: https://chromium-review.googlesource.com/361775 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: John Zhao <john.zhao@intel.com> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: John Zhao <john.zhao@intel.com> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
90b7ffcb80
commit
b807d2b097
5 changed files with 47 additions and 13 deletions
|
|
@ -12,6 +12,7 @@ smm-y += region.c
|
|||
postcar-y += region.c
|
||||
|
||||
ramstage-$(CONFIG_PLATFORM_USES_FSP1_1) += fsp_relocate.c
|
||||
ramstage-$(CONFIG_PLATFORM_USES_FSP2_0) += fsp_relocate.c
|
||||
|
||||
bootblock-y += cbfs.c
|
||||
verstage-y += cbfs.c
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue