From: Jim Duda <jim@duda.tzo.com>
To: linux-mtd@lists.infradead.org
Subject: Advice on New Hardware Platform
Date: Sun, 18 Oct 2009 12:27:40 -0400 [thread overview]
Message-ID: <hbffls$lic$1@ger.gmane.org> (raw)
I have designed a new NAND Flash Controller which supports ECC at the hardware layer.
It can be programmed to support between 6-30 bits of Reed Solomon correction over 512 or 1024K bytes of data.
The controller supports the following four main functions in hardware:
1.CLE cycles of 1 to 15 bytes of information
2. ALE cycles of 1 to 15 bytes of information
3. Page Write with DMA calculating ECC on the fly
4. Page Read with DMA correcting bytes using ECC on the fly.
ECC is stored intermixed with data, using main and spare data as one piece.
The combination of the four main functions can be used to support most devices.
I'm now investigating how to map this design to the MTD layer.
I've read all of the documentation I can find.
Since my new hardware does ECC on the fly, I'm struggling to determine which "model" to use.
Can anyone suggest an example driver to use as a starting point?
Any advice appreciated.
Thanks,
Jim
reply other threads:[~2009-10-19 22:30 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='hbffls$lic$1@ger.gmane.org' \
--to=jim@duda.tzo.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.