From: Marek Vasut Date: Sun, 15 Sep 2013 18:45:53 +0200 Subject: [U-Boot] [PATCH] doc: README.mxsimage: Use mkimage provided by U-boot In-Reply-To: <1379261501-18624-1-git-send-email-festevam@gmail.com> References: <1379261501-18624-1-git-send-email-festevam@gmail.com> Message-ID: <201309151845.54194.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Fabio Estevam, > From: Fabio Estevam > > 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 > --- > 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 \ > + ./tools/mkimage -A arm -O u-boot -T mxsimage -n 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 > + ./tools/mkimage -l > > 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