From: Steven Scholz <steven.scholz@imc-berlin.de>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: checking CRCs twice!?
Date: Wed, 12 Jan 2005 16:16:34 +0100 [thread overview]
Message-ID: <41E53F52.3010601@imc-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0501121508270.10617@phoenix.infradead.org>
>>Well. I think when a sectors gots written correctly (and summary is correct), I
>>have to assume that the sector stay intact. So no need for checks.
>>
>>If a sector got broken just by reading it then the whole embedded system is
>>broken and has to be replaced ...
>
> This seems to be true for NOR. But chrcking CRC helps at least *detect*
> and *report* media problems.
Fair enough.
But how will pay attention if the system is embedded into your microwave oven or
washing maschine... ;-)
--
Steven
next prev parent reply other threads:[~2005-01-12 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 7:51 JFFS2: checking CRCs twice!? Steven Scholz
2005-01-12 9:28 ` Ferenc Havasi
2005-01-12 14:05 ` Steven Scholz
2005-01-12 15:11 ` Artem B. Bityuckiy
2005-01-12 15:16 ` Steven Scholz [this message]
2005-01-12 15:21 ` Artem B. Bityuckiy
2005-01-12 15:28 ` Josh Boyer
2005-01-12 15:33 ` Steven Scholz
2005-01-14 10:24 ` Steven Scholz
2005-01-14 11:07 ` Artem B. Bityuckiy
2005-01-12 18:26 ` Jörn Engel
2005-01-12 18:43 ` Josh Boyer
2005-01-12 18:50 ` Jörn Engel
2005-01-12 9:35 ` Artem B. Bityuckiy
2005-01-12 10:08 ` Artem B. Bityuckiy
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=41E53F52.3010601@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linux-mtd@lists.infradead.org \
/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