From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] doc: README.mxsimage: Use mkimage provided by U-boot
Date: Sun, 15 Sep 2013 18:45:53 +0200 [thread overview]
Message-ID: <201309151845.54194.marex@denx.de> (raw)
In-Reply-To: <1379261501-18624-1-git-send-email-festevam@gmail.com>
Dear Fabio Estevam,
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Fix the text to make clear that the 'mkimage' provided by U-boot should be
> used instead of the one provided by the host PC distribution.
>
> While at it, also fix the directory location of the configuration files.
>
> After these changes, it is possible succesfully generate a u-boot.sb image.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> doc/README.mxsimage | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/README.mxsimage b/doc/README.mxsimage
> index 88a2caf..79cd06e 100644
> --- a/doc/README.mxsimage
> +++ b/doc/README.mxsimage
> @@ -9,12 +9,12 @@ Usage -- producing image:
> The mxsimage tool is targeted to be a simple replacement for the elftosb2
> . To generate an image, write an image configuration file and run:
>
> - mkimage -A arm -O u-boot -T mxsimage -n <path to configuration file> \
> + ./tools/mkimage -A arm -O u-boot -T mxsimage -n <path to configuration
> file> \ <output bootstream file>
>
> The output bootstream file is usually using the .sb file extension. Note
> that the example configuration files for producing bootable BootStream
> with -the U-Boot bootloader can be found under
> arch/arm/boot/cpu/arm926ejs/mxs/ +the U-Boot bootloader can be found under
> arch/arm/cpu/arm926ejs/mxs/ directory. See the following files:
>
> mxsimage.mx23.cfg -- This is an example configuration for i.MX23
> @@ -158,7 +158,7 @@ Usage -- verifying image:
> The mxsimage can also verify and dump contents of an image. Use the
> following syntax to verify and dump contents of an image:
>
> - mkimage -l <input bootstream file>
> + ./tools/mkimage -l <input bootstream file>
>
> This will output all the information from the SB image header and all the
> instructions contained in the SB image. It will also check if the various
Tom, are you OK with such a hack (invoking the in-tree mkimage) in the
documentation?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-09-15 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 16:11 [U-Boot] [PATCH] doc: README.mxsimage: Use mkimage provided by U-boot Fabio Estevam
2013-09-15 16:45 ` Marek Vasut [this message]
2013-09-15 16:50 ` Fabio Estevam
2013-09-15 22:58 ` Otavio Salvador
2013-09-19 14:48 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201309151845.54194.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox