All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: Ivan Djelic <ivan.djelic@parrot.com>
Cc: "Bigler, Stefan" <Stefan.Bigler@keymile.com>,
	Christopher Harvey <charvey@matrox.com>,
	"Brunck, Holger" <Holger.Brunck@keymile.com>,
	Ricard Wanderlof <ricard.wanderlof@axis.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: state of support for "external ECC hardware"
Date: Wed, 14 Nov 2012 11:12:34 +0100	[thread overview]
Message-ID: <50A36E92.7070204@keymile.com> (raw)
In-Reply-To: <20121112185231.GA6843@parrot.com>

Hi Ivan,

thanks once more.
Speaking of compatibility, I was wondering: doesn't a NAND flash have 
*any* spare storage space at all, where software could store some 
information about the current OOB layout and/or ECC mechanism?
Partition tables on hard drives for instance have a "partition type" 
byte which provides some hints about what to expect from the data within 
a partition.

This would be especially useful for *future* compatibility (i.e. old 
software reading a NAND "formatted" with unknown mechanism could simply 
stop working, or force read-only mode disabling ECC altogether).

Feasibility aside, would that make any sense?

Thank you,
Gerlando

On 11/12/2012 07:52 PM, Ivan Djelic wrote:
> On Mon, Nov 12, 2012 at 05:39:45PM +0000, Gerlando Falauto wrote:
>> Hi Ivan,
>>
>> wonderful, thanks a lot!
>> If you also happen to have an opionion to using it for chips only
>> needing 1-bit correction, I'd love to hear that...
>
> I would recommend using the strongest ECC your hardware can provide without
> hurting performance too much. This is what I do on my hardware (e.g. 8-bit
> correction on current 4-bit devices). I find it has 2 advantages:
> - increased reliability
> - seamless transition to newer devices with stronger ecc requirements
> The latter is important, because changing ECC strength can be painful: it
> means changing the OOB layout, impacting bootloader and kernel, thus breaking
> compatibility, etc.
> HTH,
> --
> Ivan

  reply	other threads:[~2012-11-14 10:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 20:42 state of support for "external ECC hardware" Christopher Harvey
2012-11-08 11:02 ` Gerlando Falauto
2012-11-08 15:21   ` Christopher Harvey
2012-11-08 16:32     ` Gerlando Falauto
2012-11-08 16:37       ` Gerlando Falauto
2012-11-08 17:03         ` Christopher Harvey
2012-11-08 17:02       ` Christopher Harvey
2012-11-08 19:07       ` Ivan Djelic
2012-11-09  8:46       ` Ricard Wanderlof
2012-11-12 17:19         ` Gerlando Falauto
2012-11-12 17:35           ` Ivan Djelic
2012-11-12 17:39             ` Gerlando Falauto
2012-11-12 18:52               ` Ivan Djelic
2012-11-14 10:12                 ` Gerlando Falauto [this message]
2012-11-14 13:24                   ` Angus CLARK
2012-11-14 14:48                     ` Matthieu CASTET
2012-11-14 20:22                     ` Ivan Djelic
2012-11-20 11:13         ` Calvin Johnson
2012-11-20 11:35           ` Gerlando Falauto
2012-11-20 12:12             ` Calvin Johnson
2012-11-20 16:16           ` Ricard Wanderlof
2012-11-08 18:59     ` Ivan Djelic
2012-11-08 19:22       ` Christopher Harvey
2012-11-08 19:33         ` Ivan Djelic
2012-11-08 18:04   ` Ivan Djelic
2012-11-14 10:59 ` Angus CLARK

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=50A36E92.7070204@keymile.com \
    --to=gerlando.falauto@keymile.com \
    --cc=Holger.Brunck@keymile.com \
    --cc=Stefan.Bigler@keymile.com \
    --cc=charvey@matrox.com \
    --cc=ivan.djelic@parrot.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.com \
    /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.