diff options
| author | Masahiro Yamada <yamada.m@jp.panasonic.com> | 2013-09-13 20:28:21 +0900 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2013-09-20 10:30:53 -0400 |
| commit | 61ffc17aeb0883bd59ced1f1589221242e8c689f (patch) | |
| tree | c7b6179b806241d3e7e96da67fde215f4b357344 | |
| parent | a466e49bf3ab88e9645b35a48f9ca3b0b9283e76 (diff) | |
cosmetic: doc: uImage.FIT: fix typos
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Acked-by: Simon Glass <sjg@chromium.org>
| -rw-r--r-- | doc/uImage.FIT/command_syntax_extensions.txt | 2 | ||||
| -rw-r--r-- | doc/uImage.FIT/source_file_format.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/uImage.FIT/command_syntax_extensions.txt b/doc/uImage.FIT/command_syntax_extensions.txt index 002818c226..6c99b1c159 100644 --- a/doc/uImage.FIT/command_syntax_extensions.txt +++ b/doc/uImage.FIT/command_syntax_extensions.txt @@ -170,7 +170,7 @@ bootm 200000 In case of the new uImage argument syntax, the address portion of any argument can be omitted. If <addr3> is omitted, then it is assumed that image at -<addr2> should be used. Similarly, when <addr2> is omitted, is is assumed that +<addr2> should be used. Similarly, when <addr2> is omitted, it is assumed that image at <addr1> should be used. If <addr1> is omitted, it is assumed that the current image address is to be used. For example, consider the following commands: diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt index 6d2070758d..160b2d05f8 100644 --- a/doc/uImage.FIT/source_file_format.txt +++ b/doc/uImage.FIT/source_file_format.txt @@ -62,7 +62,7 @@ c) Image building procedure The following picture shows how the new uImage is prepared. Input consists of image source file (.its) and a set of data files. Image is created with the help of standard U-boot mkimage tool which in turn uses dtc (device tree -compiler) to produce image tree blob (.itb). Resulting .itb file is is the +compiler) to produce image tree blob (.itb). Resulting .itb file is the actual binary of a new uImage. |