diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2018-10-09 12:00:10 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-10-15 16:01:59 -0700 |
| commit | c5cdf6fce6b0c0116bf4bcf522fce38bb05ab6d4 (patch) | |
| tree | b5e22634dbeb381bf822f261cc34792614e48244 /tests | |
| parent | 3e6397d3d612a6436052c163b8686020357e7442 (diff) | |
| download | vboot-c5cdf6fce6b0c0116bf4bcf522fce38bb05ab6d4.tar.gz | |
futility: updater: Allow patching rootkey and vblock files
For white label projects, the firmware updater has to select correct
root key and corresponding vblock files per different LOEM. In Unified
build, multiple models may share same firmware base image, with
different key files (per OEM). As a result, we have to apply the key
files before using the firmware image files.
This change adds the "patch" information when building manifest, and
prints the correct key hash in `--manifest` mode.
BUG=chromium:875551
TEST=TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility
BRANCH=None
Change-Id: Ib5e31af5262a0989a5a474d0683c83121f24cc78
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1270323
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/futility/link.manifest.json | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/futility/link.manifest.json b/tests/futility/link.manifest.json index 2cd5281b..2e11cd3b 100644 --- a/tests/futility/link.manifest.json +++ b/tests/futility/link.manifest.json @@ -1,6 +1,7 @@ { "default": { "host": { "versions": { "ro": "Google_Link.2695.1.133", "rw": "Google_Link.2695.1.133" }, + "keys": { "root": "7b5c520ceabce86f13e02b7ca363cfb509fc5b98", "recovery": "7e74cd6d66f361da068c0419d2e0946b4d091e1c" }, "image": "bios.bin" } } } |