From a326b495cdcfd56507841e38158683e6e4d5894c Mon Sep 17 00:00:00 2001 From: Simon Glass Date: Fri, 14 Sep 2018 04:57:11 -0600 Subject: 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 --- tools/binman/README.entries | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'tools/binman/README.entries') 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. - input file passed to futility + - vblock. - 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. -- cgit v1.2.1