summaryrefslogtreecommitdiff
path: root/tools/binman/README.entries
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2018-09-14 04:57:11 -0600
committerSimon Glass <sjg@chromium.org>2018-09-28 11:09:01 -0600
commita326b495cdcfd56507841e38158683e6e4d5894c (patch)
treeed9f9a1077bda5d9c09346c17be149e00e017776 /tools/binman/README.entries
parent35b384cbe5d40e618391cc076409e89cedf9c863 (diff)
downloadu-boot-a326b495cdcfd56507841e38158683e6e4d5894c.tar.gz
binman: Tidy up the vblock entry
At present if there are two vblock entries an image their contents are written to the same file in the output directory. This prevents checking the contents of each separately. Fix this by adding part of the entry path to the filename, and add some missing comments. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/binman/README.entries')
-rw-r--r--tools/binman/README.entries5
1 files changed, 5 insertions, 0 deletions
diff --git a/tools/binman/README.entries b/tools/binman/README.entries
index 31bc725d57..5cb52a92ff 100644
--- a/tools/binman/README.entries
+++ b/tools/binman/README.entries
@@ -546,6 +546,11 @@ Properties / Entry arguments:
- kernelkey: Name of the kernel key to use (inside keydir)
- preamble-flags: Value of the vboot preamble flags (typically 0)
+Output files:
+ - input.<unique_name> - input file passed to futility
+ - vblock.<unique_name> - output file generated by futility (which is
+ used as the entry contents)
+
Chromium OS signs the read-write firmware and kernel, writing the signature
in this block. This allows U-Boot to verify that the next firmware stage
and kernel are genuine.