From: Nathan Williams <nathan.williams@flightdata.com.au>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: UBI on dual NAND chips
Date: Thu, 24 Sep 2015 12:44:50 +1000 [thread overview]
Message-ID: <1443062690.32223.70.camel@ubuntu.flightdata.com.au> (raw)
Hi,
We are planning to use two 32GiB MLC NAND flash chips in a product using
a SoC FPGA with two NAND interfaces. The motivation for wanting to use
multiple NAND chips is to improve reliability, not capacity.
>From what I've read, it's possible to use UBI on a concatenated MTD.
If I have two identical chips, will these be concatenated automatically?
Is creating a single UBI volume over the two NAND chips (and using UBIFS
on it) the best way to make use of a redundant NAND chip? Would
mirroring data on a second UBI volume offer additional improvements to
data reliability?
Also, what's the current status of the "unstable bits issue"?
Thanks,
Nathan
next reply other threads:[~2015-09-24 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 2:44 Nathan Williams [this message]
2015-09-24 9:02 ` UBI on dual NAND chips Richard Weinberger
2015-09-24 14:22 ` Nathan Williams
[not found] <A765B125120D1346A63912DDE6D8B6310BF4CAC4@NTXXIAMBX02.xacn.micron.com>
2015-09-25 4:43 ` Nathan Williams
2015-09-25 5:35 ` Bean Huo 霍斌斌 (beanhuo)
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=1443062690.32223.70.camel@ubuntu.flightdata.com.au \
--to=nathan.williams@flightdata.com.au \
--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.