d9edb18037
So far, cbfstool write, when used with the -u/-d options (to "fill upwards/downwards") left the parts of the region alone for which there was no new data to write. When adding -i [0..255], these parts are overwritten with the given value. BUG=chromium:595715 BRANCH=none TEST=cbfstool write -u -i 0 ... does the right thing (fill the unused space with zeroes) Change-Id: I1b1c0eeed2862bc9fe5f66caae93b08fe21f465c Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: baf378c5f2afdae9946600ef6ff07408a3668fe0 Original-Change-Id: I3752f731f8e6592b1a390ab565aa56e6b7de6765 Original-Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Reviewed-on: https://chromium-review.googlesource.com/417319 Original-Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Original-Tested-by: Patrick Georgi <pgeorgi@chromium.org> Original-Reviewed-by: Stefan Reinauer <reinauer@chromium.org> Reviewed-on: https://review.coreboot.org/17787 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com> |
||
---|---|---|
.. | ||
abuild | ||
acpi | ||
amdfwtool | ||
amdtools | ||
archive | ||
arm_boot_tools/mksunxiboot | ||
autoport | ||
bimgtool | ||
board_status | ||
broadcom | ||
cbfstool | ||
cbmem | ||
checklist | ||
chromeos | ||
crossgcc | ||
docker | ||
dtd_parser | ||
ectool | ||
exynos | ||
futility | ||
fuzz-tests | ||
genbuild_h | ||
genprof | ||
gitconfig | ||
ifdfake | ||
ifdtool | ||
intelmetool | ||
inteltool | ||
intelvbttool | ||
ipqheader | ||
k8resdump | ||
kconfig | ||
lint | ||
marvell | ||
mma | ||
msrtool | ||
mtkheader | ||
nvidia | ||
nvramtool | ||
optionlist | ||
post | ||
release | ||
riscvtools | ||
rockchip | ||
romcc | ||
sconfig | ||
scripts | ||
showdevicetree | ||
spkmodem_recv | ||
superiotool | ||
uio_usbdebug | ||
vgabios | ||
viatool | ||
xcompile |