diff options
author | Julius Werner <jwerner@chromium.org> | 2023-11-02 16:20:17 -0700 |
---|---|---|
committer | Julius Werner <jwerner@chromium.org> | 2023-11-07 22:30:12 +0000 |
commit | ca71588620b9f4a3c37d10f133febe5d2026921f (patch) | |
tree | 152de9db0e81fad76b059250838bd1b40a1b200f /src/superio/fintek/f71863fg/Kconfig | |
parent | 682cb3b56419a242b54605cc734b99ffdcab8213 (diff) |
fmap: Eliminate some impossible code paths
When the FMAP cache is enabled, it cannot fail in pre-RAM stages unless
flash I/O in general doesn't work. Therefore, it is unnecessary and a
waste of binary size to also link a fallback path for this case.
Similarly, once the cache is written to CAR/SRAM/CBMEM there should be
no way for it to become magically corrupted between boot stages. Many
other parts of coreboot blindly assume that persistent memory stays
valid between stages so there is no reason why this code should link in
extra fallback paths in case it doesn't.
This saves a little over 200 bytes per affected (uncompressed) stage on
aarch64.
Change-Id: I7b8251dd6b34fe4f63865ebc44b9a8a103f32a57
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/78904
Reviewed-by: Yu-Ping Wu <yupingso@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/superio/fintek/f71863fg/Kconfig')
0 files changed, 0 insertions, 0 deletions