From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: ARM: LPC32XX SLC ECC Handling
Date: Wed, 08 Aug 2012 11:16:05 +0200 [thread overview]
Message-ID: <50222E55.5070204@embedded-brains.de> (raw)
Hi,
the LPC32XX SLC controller has a ECC feature that covers only the main data
area, but not the OOB data. Is it the responsibility of the user to protect
its OOB data via an ECC? The LPC32XX MLC controller on the other hand covers
the complete OOB data with its ECC. How can a user determine if it has to
protect its OOB data?
--
Sebastian Huber, embedded brains GmbH
Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone : +49 89 18 90 80 79-6
Fax : +49 89 18 90 80 79-9
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next reply other threads:[~2012-08-08 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 9:16 Sebastian Huber [this message]
2012-08-24 11:38 ` ARM: LPC32XX SLC ECC Handling Artem Bityutskiy
2012-08-24 12:54 ` Roland Stigge
2012-08-29 8:33 ` Artem Bityutskiy
2012-08-29 11:52 ` Roland Stigge
2012-09-15 3:59 ` 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=50222E55.5070204@embedded-brains.de \
--to=sebastian.huber@embedded-brains.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;
as well as URLs for NNTP newsgroup(s).