[U-Boot] [PATCH 1/2] doc: "os" is also mandatory for "ramdisk" FIT image components
According to fit_image_print(), the "os" property from "image" node is required also when "type=ramdisk".
Signed-off-by: Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com --- doc/uImage.FIT/source_file_format.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt index b47ce73..e62b679 100644 --- a/doc/uImage.FIT/source_file_format.txt +++ b/doc/uImage.FIT/source_file_format.txt @@ -166,10 +166,10 @@ the '/images' node should have the following layout: should be set to "none".
Conditionally mandatory property: - - os : OS name, mandatory for type="kernel", valid OS names are: "openbsd", - "netbsd", "freebsd", "4_4bsd", "linux", "svr4", "esix", "solaris", "irix", - "sco", "dell", "ncr", "lynxos", "vxworks", "psos", "qnx", "u_boot", - "rtems", "unity", "integrity". + - os : OS name, mandatory for types "kernel" and "ramdisk". Valid OS names + are: "openbsd", "netbsd", "freebsd", "4_4bsd", "linux", "svr4", "esix", + "solaris", "irix", "sco", "dell", "ncr", "lynxos", "vxworks", "psos", "qnx", + "u_boot", "rtems", "unity", "integrity". - arch : Architecture name, mandatory for types: "standalone", "kernel", "firmware", "ramdisk" and "fdt". Valid architecture names are: "alpha", "arm", "i386", "ia64", "mips", "mips64", "ppc", "s390", "sh", "sparc",
Signed-off-by: Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com --- doc/uImage.FIT/source_file_format.txt | 2 +- doc/uImage.FIT/verified-boot.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt index e62b679..427ea49 100644 --- a/doc/uImage.FIT/source_file_format.txt +++ b/doc/uImage.FIT/source_file_format.txt @@ -159,7 +159,7 @@ the '/images' node should have the following layout: - description : Textual description of the component sub-image - type : Name of component sub-image type, supported types are: "standalone", "kernel", "ramdisk", "firmware", "script", "filesystem", - "flat_dt" and others (see uimage_type in common/images.c). + "flat_dt" and others (see uimage_type in common/image.c). - data : Path to the external file which contains this node's binary data. - compression : Compression used by included data. Supported compressions are "gzip" and "bzip2". If no compression is used compression property diff --git a/doc/uImage.FIT/verified-boot.txt b/doc/uImage.FIT/verified-boot.txt index 3c83fbc..e639e7a 100644 --- a/doc/uImage.FIT/verified-boot.txt +++ b/doc/uImage.FIT/verified-boot.txt @@ -64,7 +64,7 @@ software from updatable memory.
It is critical that the public key be secure and cannot be tampered with. It can be stored in read-only memory, or perhaps protected by other on-chip -crypto provided by some modern SOCs. If the public key can ben changed, then +crypto provided by some modern SOCs. If the public key can be changed, then the verification is worthless.
@@ -87,7 +87,7 @@ affect the whole change.
Flattened Image Tree (FIT) -------------------------- -The FIT format is alreay widely used in U-Boot. It is a flattened device +The FIT format is already widely used in U-Boot. It is a flattened device tree (FDT) in a particular format, with images contained within. FITs include hashes to verify images, so it is relatively straightforward to add signatures as well.
On Thu, Jan 15, 2015 at 02:37:34AM -0200, Guilherme Maciel Ferreira wrote:
Signed-off-by: Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com
Applied to u-boot/master, thanks!
On Thu, Jan 15, 2015 at 02:37:33AM -0200, Guilherme Maciel Ferreira wrote:
According to fit_image_print(), the "os" property from "image" node is required also when "type=ramdisk".
Signed-off-by: Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com
Applied to u-boot/master, thanks!
participants (2)
-
Guilherme Maciel Ferreira -
Tom Rini