linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: dedekind1@gmail.com
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
	Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: ARM: LPC32XX SLC ECC Handling
Date: Fri, 24 Aug 2012 14:54:33 +0200	[thread overview]
Message-ID: <50377989.1050401@antcom.de> (raw)
In-Reply-To: <1345808311.2848.286.camel@sauron.fi.intel.com>

Hi!

On 24/08/12 13:38, Artem Bityutskiy wrote:
>> 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?
> 
> I guess it is good idea to CC the author of the drivers.

Thanks for CC'ing, would have missed it.

Yes, it's exactly as Sebastian described - only the MLC controller
covers OOB in ECC.

At this point, I need to give back the question to the MTD
maintainers: Is there an API how we can help users at this point? I
would be happy to implement it.

Thanks,

Roland

  reply	other threads:[~2012-08-24 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  9:16 ARM: LPC32XX SLC ECC Handling Sebastian Huber
2012-08-24 11:38 ` Artem Bityutskiy
2012-08-24 12:54   ` Roland Stigge [this message]
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=50377989.1050401@antcom.de \
    --to=stigge@antcom.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sebastian.huber@embedded-brains.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;
as well as URLs for NNTP newsgroup(s).