From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fw_env: add NAND support
Date: Wed, 03 Sep 2008 00:45:17 +0200 [thread overview]
Message-ID: <20080902224517.1EF1E2489D@gemini.denx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0809030014190.12823@axis700.grange>
Dear Guennadi Liakhovetski,
In message <Pine.LNX.4.64.0809030014190.12823@axis700.grange> you wrote:
>
> If you were first setting the flag to "invalid, write in progress", then
> wrote the environment, then reset the flag to "valid, write completed
> successfully", then yes, writing per one write would be essentially
> different.
But that's exactly what we are doing. The flag value for "invalid,
write in progress" is 0xFF and is set as soon as we start to destroy
the valid data by erasing the flash.
> In short, I think, CRC provides sufficient protection of data integrity.
CRC32 is not a perfect test. Yes, it's good enough for most ordinary
cases, but when we can design in additional robustness we should do
this. And we should not give up what we already have without very
good reasons.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The Wright Bothers weren't the first to fly. They were just the first
not to crash.
next prev parent reply other threads:[~2008-09-02 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 17:05 [U-Boot] [PATCH] fw_env: add NAND support Guennadi Liakhovetski
2008-09-02 20:32 ` Wolfgang Denk
2008-09-02 21:18 ` Guennadi Liakhovetski
2008-09-02 22:29 ` Guennadi Liakhovetski
2008-09-02 22:45 ` Wolfgang Denk [this message]
2008-09-03 9:19 ` Guennadi Liakhovetski
2008-09-03 13:23 ` Wolfgang Denk
2008-09-03 14:00 ` Guennadi Liakhovetski
2008-09-03 11:19 ` Guennadi Liakhovetski
2008-09-03 11:51 ` Markus Klotzbücher
2008-09-03 13:25 ` Wolfgang Denk
2008-09-03 14:26 ` Guennadi Liakhovetski
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=20080902224517.1EF1E2489D@gemini.denx.de \
--to=wd@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