From: Juergen Beisert <jbe@pengutronix.de>
To: linux-mtd@lists.infradead.org
Subject: How to distinguish MLC and SLC NANDs?
Date: Thu, 15 Sep 2011 13:33:48 +0200 [thread overview]
Message-ID: <201109151333.48684.jbe@pengutronix.de> (raw)
Hi list,
my NAND controller is able to handle different corrections sum types (a weak
one for SLC, a more stronger one for MLC). Is there a unique pattern for MLC
or SLC in the mtd structure available after calling nand_scan_ident() to
select what correction sum type should be used for the attached NAND?
Or should I always use the strongest type, independent of the NAND type?
Thanks in advance for some hints.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
next reply other threads:[~2011-09-15 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 11:33 Juergen Beisert [this message]
2011-09-15 13:39 ` How to distinguish MLC and SLC NANDs? Brian Norris
2011-09-16 6:12 ` Juergen Beisert
2011-09-16 18:27 ` Atlant Schmidt
2011-09-19 19:06 ` Brian Norris
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=201109151333.48684.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox