From: Mark Hatle <fray@mvista.com>
To: Magnus Damm <damm@opensource.se>
Cc: ¶¡ºñÓÀ <nari_dhy@nari-china.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: file system over CF flash
Date: Sun, 01 Jun 2003 09:40:54 -0500 [thread overview]
Message-ID: <3EDA1076.8010701@mvista.com> (raw)
In-Reply-To: <20030601112826.76f9978a.damm@opensource.se>
Magnus Damm wrote:
> There is no need for any special Flash file system, the Compact Flash itself keeps
> track of things like wear levelling, sector size and command set of the flash devices.
Just want to point out a common misconception on CF here. While the unit will
do wear leveling, you MUST power cycle it for that to happen. Each power cycle
pretty much locks down the sectors it is using. Bizarre I agree, but you will
burn out a CF disk very quickly if you do not constantly power cycle it. (We
had a customer experience that exact problem with the CF vendor's response being
"ohh you didn't know that?".)
CF disks are great for read-only, occasional writes, and "consumer devices"..
but are terrible for anything that you would expect long uptimes and moderate
writing. (In this situation, the little IBM CF hard drive seems to work pretty
good, but I don't have any long term experience with failure/success on one of
those.)
> The exported interface for a Compact Flash is just like any ATA Flash and under
> Linux the standard IDE driver is normally used. The CF needs to be mapped into
> some address space however, and this setup is usually taken care of by the PCMCIA
> layer or the firmware/bootloader of your specific board.
--Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-01 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 2:46 file system over CF flash 丁厚永
2003-06-01 9:28 ` Magnus Damm
2003-06-01 14:40 ` Mark Hatle [this message]
2003-06-02 20:25 ` Scott Anderson
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=3EDA1076.8010701@mvista.com \
--to=fray@mvista.com \
--cc=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nari_dhy@nari-china.com \
/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).