From: Ranga Raju B <brraju@hyd.hellosoft.com>
To: linux-mtd@lists.infradead.org
Subject: Controller which doesn't give spare area access
Date: Wed, 18 Jul 2007 11:14:46 +0530 [thread overview]
Message-ID: <469DA8CE.1000405@hyd.hellosoft.com> (raw)
Hi,
1. The NFC I am using doesn't give read/write access to spare area.
2. I have to write 512 bytes at a time or read 512 bytes at a time.
3. I don't have access to status, ready/busy pin.
Please tell me what auto placement strategy I need to adopt. What ECC
scheme I need to use. It has a HW ECC Generator but I don't have access
to the value of ECC.
I only get an interrupt if there is a ECC mismatch.
Best regards
Ranga Raju B
reply other threads:[~2007-07-18 5:47 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=469DA8CE.1000405@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.