From: Enrico Joerns <ejo@pengutronix.de>
To: caglar.kilimci@accenture.com
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] NAND flash
Date: Wed, 5 Apr 2017 16:15:38 +0200 [thread overview]
Message-ID: <4e01c63c-0a2a-42ae-17a3-c222017b6598@pengutronix.de> (raw)
In-Reply-To: <3e26b6170d82478b9510b8dbdec7a8e3@DM2PR42MB141.048d.mgd.msft.net>
Hi Caglar,
On 04/05/2017 03:10 PM, caglar.kilimci@accenture.com wrote:
> Hello,
>
> I have a question about storage type, NAND. The documentation [1] emphasizes not to use NAND flash but why?
>
> [1] http://rauc.readthedocs.io/en/latest/updating.html?highlight=nand
well, this is a general advice, not something RAUC-specific. RAUC can
handle NAND on the different layers, either for writing raw data with
`nandwrite` or by using 'NAND-filesystems' such as UBI(FS).
But, from ours and others daily experience and knowledge about the
technology the general conclusion is that raw NANDs, especially MLCs,
are very, very hard to handle.
There are many different and hardware-specific effects that you have to
deal with, and if you see how hard for example developers from the UBI
filesystem attempt to solve this, [1] you may also conclude that you
really want to avoid using NANDs on this level.
Our advice instead would be to use eMMCs instead, where all the critical
stuff is hidden and handled internally, by hardware-controllers designed
by those who (hopefully) really know about the quirks of their NAND chips.
I hope I could make that point a little clearer, I know that this
documentation chapter is not our most extensive one, yet. Patches are
always welcome ;)
Best regards
Enrico
[1]
http://free-electrons.com/pub/conferences/2016/elce/brezillon-ubi-mlc/ubi-mlc.pdf
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
prev parent reply other threads:[~2017-04-05 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 13:10 caglar.kilimci
2017-04-05 14:15 ` Enrico Joerns [this message]
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=4e01c63c-0a2a-42ae-17a3-c222017b6598@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=caglar.kilimci@accenture.com \
--cc=rauc@pengutronix.de \
/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