All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitin Garg <nitin.garg@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: imximage: Fix the maximum DCD size for mx53/mx6
Date: Tue, 2 Sep 2014 10:11:39 -0500	[thread overview]
Message-ID: <5405DE2B.7090004@freescale.com> (raw)
In-Reply-To: <1409576183-2819-1-git-send-email-fabio.estevam@freescale.com>

On 09/01/2014 07:56 AM, Fabio Estevam wrote:
> According to mx53 and mx6 reference manuals:
> 
> "The maximum size of the DCD limited to 1768 bytes."
> 
> As each DCD entry consists of 8 bytes, we have a total of 1768 / 8 = 221, and
> excluding the first entry, which is the header leads to 220 as the maximum
> number for DCD size.
> 
> Reported-by: Jonas Karlsson <jonas.d.karlsson@gmail.com> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  tools/imximage.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/imximage.h b/tools/imximage.h
> index 01f861e..5b5ad0e 100644
> --- a/tools/imximage.h
> +++ b/tools/imximage.h
> @@ -8,7 +8,7 @@
>  #ifndef _IMXIMAGE_H_
>  #define _IMXIMAGE_H_
>  
> -#define MAX_HW_CFG_SIZE_V2 121 /* Max number of registers imx can set for v2 */
> +#define MAX_HW_CFG_SIZE_V2 220 /* Max number of registers imx can set for v2 */
>  #define MAX_HW_CFG_SIZE_V1 60  /* Max number of registers imx can set for v1 */
>  #define APP_CODE_BARKER	0xB1
>  #define DCD_BARKER	0xB17219E9
> 

Acked-by: Nitin Garg <nitin.garg@freescale.com>

  parent reply	other threads:[~2014-09-02 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 12:56 [U-Boot] [PATCH] tools: imximage: Fix the maximum DCD size for mx53/mx6 Fabio Estevam
2014-09-01 13:35 ` Nitin Garg
2014-09-02 14:15   ` Tom Rini
2014-09-02 14:57 ` Nitin Garg
2014-09-02 15:11 ` Nitin Garg [this message]
2014-09-09 14:24 ` Stefano Babic

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=5405DE2B.7090004@freescale.com \
    --to=nitin.garg@freescale.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.