From: "Yigal Sadgat" <YSadgat1@gcte.com>
To: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Cc: jwboyer@linux.vnet.ibm.com, joern@logfs.org
Subject: Compact Flash Question
Date: Tue, 6 May 2008 14:59:33 -0700 [thread overview]
Message-ID: <005b01c8afc4$77f4ec90$6401a8c0@techwriter> (raw)
We wrote the Kernel to support CF drives (in IDE mode) several years ago but
now there are strange things coming back from the field that compel us to go
back and re-evaluate many design decisions.
For instance,
(1) Can you really ignore bit(2) (CORR) in the Status register offset 7 that
tells
you that the CF has detected and corrected a soft error?, etc.
(2) An engineer at SanDisk Engineering told me NOT to do wear leveling.
The file allocation table is written very frequently back into the flash. So
is it really safe to assume that I don't need wear leveling???
(3) Re. the BUSY bit in the status register (offset 7, bit D7), anybody
experienced
time outs?
(4) Re Error register (offset 1) bit D7 (BBK), again, I was told that it
cannot (???)
happen since the CF performs read-after-write and it automatically switches
good blocks
for bad ones... Is this correct?
We get many "soft" errors and I cannot wait to put my hand on a system to
test but
thought I would draw on your collective experience before we dive into these
issues again.
Any comments would be greatly appreciated.
Yigal Sadgat
General Computer Technology (GCT)
YSadgat1@gcte.com
next reply other threads:[~2008-05-06 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:59 Yigal Sadgat [this message]
2008-05-06 22:09 ` Compact Flash Question Alan Cox
2008-05-13 17:13 ` Yigal Sadgat
2008-05-06 22:22 ` linux-os (Dick Johnson)
2008-05-07 6:15 ` Bart Van Assche
2008-05-07 7:39 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 7:27 Tomasz Chmielewski
[not found] <48215673.3060201@wpkg.org>
[not found] ` <e2e108260805070044v42f596bbj39c5b52b6f0a096@mail.gmail.com>
2008-05-07 7:54 ` Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche
2008-05-07 12:31 ` Helge Hafting
2008-05-07 15:01 ` Stéphane ANCELOT
2008-05-07 16:46 ` Bart Van Assche
2008-05-08 13:26 ` Mark Lord
2008-05-08 14:27 ` Lennart Sorensen
2008-05-08 14:59 ` Willy Tarreau
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='005b01c8afc4$77f4ec90$6401a8c0@techwriter' \
--to=ysadgat1@gcte.com \
--cc=joern@logfs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).