From: Wolfgang Denk <wd@denx.de>
To: "Jón Benediktsson" <jonb@marel.is>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Handling power failure - MPC5200
Date: Fri, 05 Nov 2004 15:32:18 +0100 [thread overview]
Message-ID: <20041105143223.52CDFC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 05 Nov 2004 14:13:51 GMT." <OF5D3B44B5.3530BFCD-ON00256F43.0035B584-00256F43.004E2C6C@marel.is>
In message <OF5D3B44B5.3530BFCD-ON00256F43.0035B584-00256F43.004E2C6C@marel.is> you wrote:
>
> > Use the standard methods: use the CF card read-only (many CF cards
> > can be damaged [beyond repair] when you power off while a write
> > operation is in progress).
>
> Is this an acknowledged fact by CF manufacturers or based on experiece ?
You mean acknowledged officially in writing on letterhead paper? No.
Inofficially: yes.
Also many people have confirmed this behaviour, at least on the cheap
"standard" (versus "industrial grade") CF cards.
I recommend to specifically ask your CF card vendor / distributor for
a confirmation and guarantee (in writing) that it is safe to turn off
power while writing to the device. Guess what you will get?
Best regards,
Wolfgang Denk
--
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"The whole world is about three drinks behind." - Humphrey Bogart
next prev parent reply other threads:[~2004-11-05 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 12:32 Handling power failure - MPC5200 Jón Benediktsson
2004-11-04 16:22 ` Wolfgang Denk
2004-11-05 14:13 ` Jón Benediktsson
2004-11-05 14:32 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 14:48 VanBaren, Gerald (AGRE)
2004-11-05 15:09 ` Mark Chambers
2004-11-05 20:47 ` Wolfgang Denk
2004-11-05 21:26 ` Mark Chambers
2004-11-06 0:52 ` Wolfgang Denk
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=20041105143223.52CDFC1430@atlas.denx.de \
--to=wd@denx.de \
--cc=jonb@marel.is \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).