From: Andrea Scian <rnd4@dave-tech.it>
To: mtd_mailinglist <linux-mtd@lists.infradead.org>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
"Jeff Lauruhn \(jlauruhn\)" <jlauruhn@micron.com>
Subject: [MLC NAND]: data pattern sensivity
Date: Fri, 03 Apr 2015 11:46:05 +0200 [thread overview]
Message-ID: <551E615D.3090804@dave-tech.it> (raw)
Dear All,
I was looking inside Boris presentation at latest ELC (nice work!) and
trying to understand a bit deeper the systematic data pattern problem.
I also did some research on this ML, looking for some details about this
topic, finding not so much more the original RFC thread:
http://thread.gmane.org/gmane.linux.drivers.devicetree/72230/
I search for this kind of information inside various MLC NAND datasheets
that I've available on my desk but I cannot find any reference on this,
maybe is called in a different way or maybe I'm looking to the wrong
devices (e.g. I'm currently working with some Micron NANDs
MT29F32G08CBADA, MT29F32G08CBACA..)
I CCed Boris and Jeff directly because maybe they can help me in better
understanding the impact of this problem on some real device.
TIA & BR,
--
Andrea SCIAN
DAVE Embedded Systems
next reply other threads:[~2015-04-03 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 9:46 Andrea Scian [this message]
2015-04-03 17:20 ` [MLC NAND]: data pattern sensivity Jeff Lauruhn (jlauruhn)
2015-04-07 10:31 ` Andrea Scian
2015-04-07 11:19 ` Boris Brezillon
2015-04-07 13:21 ` Andrea Scian
2015-04-07 15:08 ` Boris Brezillon
2015-04-07 17:45 ` Jeff Lauruhn (jlauruhn)
2015-04-09 20:19 ` Andrea Scian
[not found] <mailman.1.1428433201.16973.linux-mtd@lists.infradead.org>
2015-04-10 2:52 ` Bean Huo 霍斌斌 (beanhuo)
-- strict thread matches above, loose matches on Subject: below --
2015-04-10 8:27 Qi Wang 王起 (qiwang)
2015-04-10 9:30 ` Andrea Scian
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=551E615D.3090804@dave-tech.it \
--to=rnd4@dave-tech.it \
--cc=boris.brezillon@free-electrons.com \
--cc=jlauruhn@micron.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 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).