diff options
| author | Simon Glass <sjg@chromium.org> | 2019-12-06 21:42:02 -0700 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2019-12-15 11:44:13 +0800 |
| commit | 0ad9b6a98836b8109d46ba32e6a4a40beb058388 (patch) | |
| tree | 925f1bfa7c3b578b31966857de1f6861c699e8b6 /arch/x86/cpu/tangier | |
| parent | 112629c53a488fd87e3b6116f16ce768e8930f94 (diff) | |
x86: Correct mrccache find_next_mrc_cache() calculation
This should take account of the end of the new cache record since a record
cannot extend beyond the end of the flash region. This problem was not
seen before due to the alignment of the relatively small amount of MRC
data.
But with Apollo Lake the MRC data is about 45KB, even if most of it is
zeroes.
Fix this bug and update the parameter name to be less confusing.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'arch/x86/cpu/tangier')
0 files changed, 0 insertions, 0 deletions