diff options
| author | Karthikeyan Ramasubramanian <kramasub@google.com> | 2024-04-30 04:25:05 +0000 |
|---|---|---|
| committer | Karthik Ramasubramanian <kramasub@google.com> | 2024-05-03 17:03:37 +0000 |
| commit | 3c7bbde4fdfc90520b5281b266f321219912d942 (patch) | |
| tree | 96cbcb1cafc97e5bef73f04ccb2d3014aae6a4ed /src/drivers/intel/fsp1_1 | |
| parent | 0c66e9ddf0ce83d5e499485b419cad694a8a45a7 (diff) | |
drivers/intel/fsp2_0: Release bmp_logo during OS_PAYLOAD_LOAD stage
bmp_load_logo() loads the custom logo.bmp file into CBMEM. This cbmem
buffer is released after FSP-S init is complete. In certain platforms,
the logo file is displayed during PCI enumeration. This means the logo
buffer is used after it is released. Fix this issue by releasing the
logo buffer when the coreboot has finished loading payload. During S3
scenario CBMEM is locked, bmp logo is not loaded and hence the release
is a no-op.
BUG=b:337144954
TEST=Build Skyrim BIOS Image and boot to OS. Ensure that the chromeOS
boot logo is seen without any corruption.
Change-Id: Id27cf02de04055075e7c1cb0ae531dee8524f828
Signed-off-by: Karthikeyan Ramasubramanian <kramasub@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/82121
Reviewed-by: Subrata Banik <subratabanik@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Matt DeVillier <matt.devillier@amd.corp-partner.google.com>
Diffstat (limited to 'src/drivers/intel/fsp1_1')
0 files changed, 0 insertions, 0 deletions