All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RE : Davinci DM365 custom design : Problem when reading uBoot environment variables
Date: Fri, 17 Sep 2010 13:01:36 -0500	[thread overview]
Message-ID: <20100917130136.563f05a9@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <20100917143204.6416A15242D@gemini.denx.de>

On Fri, 17 Sep 2010 16:32:04 +0200
Wolfgang Denk <wd@denx.de> wrote:

> Dear Reda MIMOUNE,
> 
> In message <1918F436C366B34BB245DD28389E039453ADFAAD2A@mars.easii.fr> you wrote:
> >
> >  reading the README file, here is what I read:
> > 
> > 	Note: CFG_ENV_OFFSET and CFG_ENV_OFFSET_REDUND must be aligned
> > 	to a block boundary, and CFG_ENV_SIZE must be a multiple of
> > 	the NAND devices block size.
> 
> I think that should be CONFIG_ENV_SECT_SIZE

CONFIG_ENV_SECT_SIZE isn't used by env_nand.c -- it uses the
dynamically-read block size in nand_info.

> > Since my sectors/blocks are 128KB, I must be at least 128KB!
> > 
> > Is the README file wrong ?
> 
> Seems so. Unless Davinci has messed up this.

Yes, the README is wrong.  It used to be that way until commit
c3db8c649c6ab3da2f1411c4c6d61aecea054aa4, and README wasn't updated.

The current requirement is that CONFIG_ENV_SIZE be a multiple of the
page size.

-Scott

  parent reply	other threads:[~2010-09-17 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 16:21 [U-Boot] Davinci DM365 custom design : Problem when reading uBoot environment variables Reda MIMOUNE
2010-09-15 18:15 ` Scott Wood
2010-09-16  7:42   ` [U-Boot] RE : " Reda MIMOUNE
2010-09-16 16:55     ` [U-Boot] " Scott Wood
2010-09-17  7:35       ` [U-Boot] RE : " Reda MIMOUNE
2010-09-17 12:37         ` Wolfgang Denk
2010-09-17 12:48           ` [U-Boot] RE : " Reda MIMOUNE
2010-09-17 14:32             ` Wolfgang Denk
2010-09-17 14:49               ` Reda MIMOUNE
2010-09-17 15:02                 ` Wolfgang Denk
2010-09-17 18:01               ` Scott Wood [this message]
2010-09-21 14:47                 ` Reda MIMOUNE

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=20100917130136.563f05a9@schlenkerla.am.freescale.net \
    --to=scottwood@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.