From: Peter Korsgaard <jacmet@sunsite.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 6/8] omap_gpmc: BCH8 support (ELM based)
Date: Sat, 17 Nov 2012 20:13:52 +0100 [thread overview]
Message-ID: <87haoot53j.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50A79AD2.7060504@googlemail.com> ("Andreas Bießmann"'s message of "Sat, 17 Nov 2012 15:10:26 +0100")
>>>>> "Andreas" == Andreas Bie?mann <andreas.devel@googlemail.com> writes:
Hi,
>> No, please not. Having more than 1 OOB layout on the same NAND device
>> leads to all kind of complications. There has also been kernel patches
>> posted for the ELM, so IMHO the only sane option for am33xx is BCH8
>> everywhere (with the ROM layout).
Andreas> Ok, I understand your point here. But there are device
Andreas> combinations out there that do not match! We have an AM37xx
Andreas> with some micron NAND that requires 1bit ECC for the first
Andreas> page (if less than 1000 erase cycle). But 4bit ECC for the
Andreas> rest of the device. With the 1bit for first page it does fit
Andreas> to the ROM requirements of that SoC but unfortunately we can
Andreas> not use the same OOB layout on the whole device, cause the ROM
Andreas> can only do the 1bit hamming ECC. I think there are other
Andreas> boards out there facing the same problem. I have to recheck
Andreas> for example the devkit8000 which is a mainlined development
Andreas> device some users based their products on (as we do).
Sure, reality tends to be more complicated than that. The different
SoCs, Nand devices and projects have different requirements. Notice that
this patch is specifically about the Error Location Module present on
E.G. am33xx and omap4, where the ROM also uses BCH encoding.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-11-17 19:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 23:06 [U-Boot] [PATCH v2 0/8] NAND support for AM33XX Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 1/8] OMAP: include sys_proto.h from boot-common Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 2/8] am335x_evm: add nand pinmux definition Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 3/8] am33xx: NAND support Ilya Yanok
2012-11-08 9:33 ` Peter Korsgaard
2012-11-15 20:21 ` Ilya Yanok
2012-11-15 22:26 ` Peter Korsgaard
2012-11-21 16:59 ` Tom Rini
2012-11-06 23:06 ` [U-Boot] [PATCH v2 4/8] am335x_evm: enable " Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 5/8] am33xx: add ELM support Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 6/8] omap_gpmc: BCH8 support (ELM based) Ilya Yanok
2012-11-15 13:25 ` Andreas Bießmann
[not found] ` <CAA3CPjX0pHtU6y6kAtzVmdZq-akGAXhKcpkq92BwBJtb0HbRgw@mail.gmail.com>
2012-11-16 10:24 ` Andreas Bießmann
2012-11-16 15:59 ` Peter Korsgaard
2012-11-17 14:10 ` Andreas Bießmann
2012-11-17 19:13 ` Peter Korsgaard [this message]
2012-11-21 17:04 ` Tom Rini
2012-11-21 20:51 ` Andreas Bießmann
2012-11-06 23:06 ` [U-Boot] [PATCH v2 7/8] am33xx_spl_bch: simple SPL nand loader for AM33XX Ilya Yanok
2012-11-06 23:06 ` [U-Boot] [PATCH v2 8/8] am335x_evm: enable SPL NAND support Ilya Yanok
2012-12-10 20:18 ` [U-Boot] [PATCH v2 0/8] NAND support for AM33XX Tom Rini
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=87haoot53j.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=u-boot@lists.denx.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