From: Jesus Alvarez <jalvarez@micromint.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AT91: NAND OOB and ECC in U-Boot vs Linux
Date: Wed, 18 Mar 2009 05:39:17 -0700 (PDT) [thread overview]
Message-ID: <22578266.post@talk.nabble.com> (raw)
In-Reply-To: <20090318103811.GC25814@game.jcrosoft.org>
> yes if they do not use the same ECC algo they will see the data corrupted
> and
> they will try to fix it
Thanks for your response. Yet I could not find CONFIG_ options in U-Boot
equivalent to the atmel_nand options in the kernel. It seems like the U-Boot
NAND writes and the kernel NAND writes (when CONFIG_MTD_NAND_ATMEL is
selected) will use different logic for ECC and OOB layout.
Should the U-Boot "nand write.jffs2" command be avoided with AT91 targets
using post-2.6.27 kernels? Or are there U-Boot CONFIG_ options compatible
with the atmel_nand options in the current kernels?
Regards,
Jesus Alvarez
--
View this message in context: http://www.nabble.com/-U-Boot--AT91%3A-NAND-OOB-and-ECC-in-U-Boot-vs-Linux-tp22572030p22578266.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-03-18 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 2:41 [U-Boot] AT91: NAND OOB and ECC in U-Boot vs Linux Jesus Alvarez
2009-03-18 10:38 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-18 12:39 ` Jesus Alvarez [this message]
2009-03-18 14:45 ` Nicolas Ferre
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=22578266.post@talk.nabble.com \
--to=jalvarez@micromint.com \
--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