From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC] Change ECC algorithm from userspace
Date: Fri, 28 Oct 2011 13:51:27 +0200 [thread overview]
Message-ID: <4EAA973F.8060104@parrot.com> (raw)
In-Reply-To: <CAAwP0s32AJCm_AjxubDSu8ikzhXeRWUqqsPrBmygUHPkRvtv8g@mail.gmail.com>
Javier Martinez Canillas a écrit :
> On Fri, Oct 28, 2011 at 12:30 PM, Matthieu CASTET
> <matthieu.castet@parrot.com> wrote:
>> PS : note that some OMAP ROM support a better protection than Hamming (but the
>> details are not public AFAIK)
>>
>> From OMAP34xx Multimedia Device, Silicon Revision 3.1.x, public version :
>>
>> Pages can contain errors caused by memory alteration. To correct these errors,
>> the ROM code uses ECC,
>> based on Hamming codes for SLC NAND and BCH (Bose, Ray-Chaudhuri, Hocquenghem)
>> code for
>> multilevel cell (MLC) devices. The computed ECC is compared to ECC stored in the
>> spare area of the
>> corresponding page. If there are uncorrectable errors, the ROM code returns with
>> FAIL.
>>
>
> Yes I've read that on the DM3730 TRM but as far as I understand only
> applies to MLC devices, but ours is SLC.
>
It also works on SLC devices. We are using it on micron slc that need 4 bits ECC.
Matthieu
WARNING: multiple messages have this Message-ID (diff)
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Enric Balletbo i Serra <eballetbo@iseebcn.com>
Subject: Re: [RFC] Change ECC algorithm from userspace
Date: Fri, 28 Oct 2011 13:51:27 +0200 [thread overview]
Message-ID: <4EAA973F.8060104@parrot.com> (raw)
In-Reply-To: <CAAwP0s32AJCm_AjxubDSu8ikzhXeRWUqqsPrBmygUHPkRvtv8g@mail.gmail.com>
Javier Martinez Canillas a écrit :
> On Fri, Oct 28, 2011 at 12:30 PM, Matthieu CASTET
> <matthieu.castet@parrot.com> wrote:
>> PS : note that some OMAP ROM support a better protection than Hamming (but the
>> details are not public AFAIK)
>>
>> From OMAP34xx Multimedia Device, Silicon Revision 3.1.x, public version :
>>
>> Pages can contain errors caused by memory alteration. To correct these errors,
>> the ROM code uses ECC,
>> based on Hamming codes for SLC NAND and BCH (Bose, Ray-Chaudhuri, Hocquenghem)
>> code for
>> multilevel cell (MLC) devices. The computed ECC is compared to ECC stored in the
>> spare area of the
>> corresponding page. If there are uncorrectable errors, the ROM code returns with
>> FAIL.
>>
>
> Yes I've read that on the DM3730 TRM but as far as I understand only
> applies to MLC devices, but ours is SLC.
>
It also works on SLC devices. We are using it on micron slc that need 4 bits ECC.
Matthieu
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-28 11:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 9:42 [RFC] Change ECC algorithm from userspace Javier Martinez Canillas
2011-10-28 9:42 ` Javier Martinez Canillas
2011-10-28 10:30 ` Matthieu CASTET
2011-10-28 10:30 ` Matthieu CASTET
2011-10-28 11:10 ` Javier Martinez Canillas
2011-10-28 11:10 ` Javier Martinez Canillas
2011-10-28 11:51 ` Matthieu CASTET [this message]
2011-10-28 11:51 ` Matthieu CASTET
2011-10-28 12:00 ` Javier Martinez Canillas
2011-10-28 12:00 ` Javier Martinez Canillas
2011-10-31 9:02 ` Florian Fainelli
2011-10-31 9:02 ` Florian Fainelli
2011-10-28 10:33 ` Jon Povey
2011-10-28 10:33 ` Jon Povey
2011-10-28 10:40 ` Matthieu CASTET
2011-10-28 10:40 ` Matthieu CASTET
2011-10-28 11:13 ` Javier Martinez Canillas
2011-10-28 11:13 ` Javier Martinez Canillas
2011-11-01 4:18 ` DaVinci NAND writing utility release, was: " Jon Povey
2011-11-01 4:18 ` Jon Povey
2011-11-01 10:34 ` Javier Martinez Canillas
2011-11-01 10:34 ` Javier Martinez Canillas
2011-10-31 8:04 ` Ricard Wanderlof
2011-10-31 8:04 ` Ricard Wanderlof
2011-10-28 10:43 ` Atlant Schmidt
2011-10-28 10:43 ` Atlant Schmidt
2011-10-28 11:13 ` Angus CLARK
2011-10-28 11:21 ` Javier Martinez Canillas
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=4EAA973F.8060104@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=eballetbo@iseebcn.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.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.