| Message ID | 1379071701-28760-1-git-send-email-yamada.m@jp.panasonic.com |
|---|---|
| State | Accepted |
| Delegated to: | Tom Rini |
| Headers | show |
On Fri, Sep 13, 2013 at 5:28 AM, Masahiro Yamada <yamada.m@jp.panasonic.com>wrote: > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> > Acked-by: Simon Glass <sjg@chromium.org> > --- > doc/uImage.FIT/command_syntax_extensions.txt | 2 +- > 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 002818c..6c99b1c 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 6d20707..160b2d0 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. > > > -- > 1.8.1.2 > > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot >
On Fri, Sep 13, 2013 at 08:28:21PM +0900, Masahiro Yamada wrote: > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> > Acked-by: Simon Glass <sjg@chromium.org> Applied to u-boot/master, thanks!
diff --git a/doc/uImage.FIT/command_syntax_extensions.txt b/doc/uImage.FIT/command_syntax_extensions.txt index 002818c..6c99b1c 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 6d20707..160b2d0 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.
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> --- doc/uImage.FIT/command_syntax_extensions.txt | 2 +- doc/uImage.FIT/source_file_format.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)