From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README.imximage: Fix the maximum DCD size
Date: Tue, 09 Sep 2014 17:31:44 +0200 [thread overview]
Message-ID: <540F1D60.10207@denx.de> (raw)
In-Reply-To: <1410276498-6716-1-git-send-email-fabio.estevam@freescale.com>
Hi Fabio,
On 09/09/2014 17:28, Fabio Estevam wrote:
> In commit 021e79c85371 ("tools: imximage: Fix the maximum DCD size for
> mx53/mx6") we have fixed the maximum DCD size for mx53/mx53.
>
> Do the same on the README document for consistency.
>
> Reported-by: Jonas Karlsson <jonas.d.karlsson@gmail.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> doc/README.imximage | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/README.imximage b/doc/README.imximage
> index dcda200..27d3354 100644
> --- a/doc/README.imximage
> +++ b/doc/README.imximage
> @@ -120,7 +120,7 @@ Configuration command line syntax:
> DATA 4 0x73FA88a0 0x200
>
> The processor support up to 60 register programming commands for IMXIMAGE_VERSION 1
> -and 121 register programming commands for IMXIMAGE_VERSION 2.
> +and 220 register programming commands for IMXIMAGE_VERSION 2.
> An error is generated if more commands are found in the configuration file.
>
Correct. Thanks for fixing the documentation, too.
Acked-by: Stefano Babic <sbabic@denx.de>
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2014-09-09 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:28 [U-Boot] [PATCH] README.imximage: Fix the maximum DCD size Fabio Estevam
2014-09-09 15:31 ` Stefano Babic [this message]
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=540F1D60.10207@denx.de \
--to=sbabic@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