BIOS needs to ensure that SPI write does not cross 256-byte
boundary. Else, if the write is across 256-byte boundary, then it
corrupts the block by wrapping write to start of current block. Thus,
ensure nuclear_spi_{read,write} operate within a single 256-byte block
only at a time.
BUG=chrome-os-partner:59813
BRANCH=None
TEST=Verified that elog writes do not corrupt the event log when write
is across 256-byte blocks.
Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: https://review.coreboot.org/17419
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Change-Id: I854ca2979d65b9f1232f93182cb84d4dee4f4139
Reviewed-on: https://chromium-review.googlesource.com/412044
Commit-Ready: Furquan Shaikh <furquan@chromium.org>
Tested-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
|
||
|---|---|---|
| .. | ||
| apollolake | ||
| baytrail | ||
| braswell | ||
| broadwell | ||
| common | ||
| fsp_baytrail | ||
| fsp_broadwell_de | ||
| quark | ||
| sch | ||
| skylake | ||