From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot environment update in linux embedded ARM architecture
Date: Mon, 20 Jul 2009 14:21:06 +0200 [thread overview]
Message-ID: <20090720122106.GA7450@mail.gnudd.com> (raw)
In-Reply-To: <4A6444BA.2040309@microhard.biz>
> 0x20000 *U-Boot (2009.06)*
> 0x60000 *U-Boot Env.*
So two blocks. for u-boot, which is bigger than one block.
> the u-boot environment part of the u-boot code is overwritten with the
> environment parameters. This happens only when our NAND flash has bad
> blocks in the u-boot zone. (Block 1 and 2),
In this case u-boot is stored in two blocks, but skipping the bad
block. Your env area will contain the trailing part of u-boot binary.
I'm sure your consultant already told you.
> /Questo messaggio ed i suoi allegati viene spedito solo alle persone
> indicate come destinatarie. Esso contiene informazioni confidenziali
Please avoid this meaningless stuff when posting to public lists (even
in private mail it sounds insulting, but that's just personal taste).
/alessandro
prev parent reply other threads:[~2009-07-20 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 10:19 [U-Boot] U-Boot environment update in linux embedded ARM architecture Jan Misfatto
2009-07-20 12:21 ` Alessandro Rubini [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=20090720122106.GA7450@mail.gnudd.com \
--to=rubini-list@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox