
18 Mar
2009
18 Mar
'09
1:39 p.m.
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-t...
Sent from the Uboot - Users mailing list archive at Nabble.com.