From: Ranga Raju B <brraju@hyd.hellosoft.com>
To: linux-mtd@lists.infradead.org
Subject: Doubts regarding MTD
Date: Mon, 16 Jul 2007 21:45:15 +0530 [thread overview]
Message-ID: <469B9993.9020702@hyd.hellosoft.com> (raw)
Hi,
We are using ARASAN NFC with Micron NAND Device. I am writing a
driver based on ndfc.c I have few problems here.
1. ARASAN NFC doesn't give me read or write access to spare area. I can
know a block is bad (Manufacture Bad Block) using a command and it gives
the status.
2. NFC itself generates NAND_ECC_HW3_512, writes into the spare area
when we specify the Spare Area Address where the ECC to written or read
for a 512 byte. It never allows us to know what the ECC is as we can't
read the content of spare area.
3. NFC handles the single bit errors if any but doesn't handle the multi
bit errors.
I don't know how to handle this. I know that we need to return the value
of the ECC into the ECC buffer whenever a read/write is requested. What
is the placement scheme that is recommended for this situation. How do I
handle the ECC from MTD. Should I use Software ECC or shall I specify
ECC_NONE.
Summary: How do handle the situation when NFC doesn't give access to the
spare area of the NAND Device.
Regards
Ranga
reply other threads:[~2007-07-16 16:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=469B9993.9020702@hyd.hellosoft.com \
--to=brraju@hyd.hellosoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.