b807d2b097
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>
28 lines
639 B
Makefile
28 lines
639 B
Makefile
bootblock-y += mem_pool.c
|
|
verstage-y += mem_pool.c
|
|
romstage-y += mem_pool.c
|
|
ramstage-y += mem_pool.c
|
|
postcar-y += mem_pool.c
|
|
|
|
bootblock-y += region.c
|
|
verstage-y += region.c
|
|
romstage-y += region.c
|
|
ramstage-y += region.c
|
|
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
|
|
romstage-y += cbfs.c
|
|
ramstage-y += cbfs.c
|
|
smm-y += cbfs.c
|
|
postcar-y += cbfs.c
|
|
|
|
bootblock-y += lz4_wrapper.c
|
|
verstage-y += lz4_wrapper.c
|
|
romstage-y += lz4_wrapper.c
|
|
ramstage-y += lz4_wrapper.c
|
|
postcar-y += lz4_wrapper.c
|