From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesus Alvarez Date: Wed, 18 Mar 2009 05:39:17 -0700 (PDT) Subject: [U-Boot] AT91: NAND OOB and ECC in U-Boot vs Linux In-Reply-To: <20090318103811.GC25814@game.jcrosoft.org> References: <06c701c9a773$12112180$36336480$@com> <20090318103811.GC25814@game.jcrosoft.org> Message-ID: <22578266.post@talk.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > 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.