[..snip..]
% mkfs.jffs2 --little-endian --no-cleanmarkers --pad 2048 --pagesize 2048
--eraseblock 131072 -d /tmp/tmp.h9dKGpcNFw -D root.devices -o root.jffs2
nand write.i ${loadaddr} 0x00c0 0x200
nand write.i ${loadaddr} 0x0420 0x200
[Ghorai] why you writing
software ECC in omap2.c NAND driver. Why?
Between 2.6.35 and 2.6.36 there have need quite a few changes in the NAND
driver, including a change from software to hardware ECC.
The new code has hardware ECC forced on by:
#define CONFIG_MTD_NAND_OMAP_HWECC
I am surprised
On 11/21/10 1:01 PM, Charles Manning wrote:
Just recompiling with the CONFIG_MTD_NAND_OMAP_HWECC define commented out did
not result in a working system. I suspect there is more tto the problem than
this.
FWIW, I had the exact same issues with my Mistral AM37x EVM board. I not
only had to
-Original Message-
From: Grant Erickson [mailto:maratho...@gmail.com]
Sent: Monday, November 22, 2010 11:39 AM
To: Charles Manning
Cc: linux-omap@vger.kernel.org; Grazvydas Ignotas; Ghorai, Sukumar
Subject: Re: No more software ECC in omap2.c NAND driver. Why?
On 11/21/10 1:01
in omap2.c NAND driver. Why?
On 11/21/10 1:01 PM, Charles Manning wrote:
Just recompiling with the CONFIG_MTD_NAND_OMAP_HWECC define commented
out did
not result in a working system. I suspect there is more tto the problem
than
this.
FWIW, I had the exact same issues with my Mistral AM37x EVM
[..snip..]
The board (Mistral AM37x) NAND (Micron 256 MiB) was originally
bootstrapped
over SD/MMC from u-boot using the following script:
[Ghorai] let me know the nand details - x8/x16, small/big page?
[..snip..]
nandecc sw
[..snip..]
fatload mmc 0 ${loadaddr} root.jff
: No more software ECC in omap2.c NAND driver. Why?
Between 2.6.35 and 2.6.36 there have need quite a few changes in the NAND
driver, including a change from software to hardware ECC.
The new code has hardware ECC forced on by:
#define CONFIG_MTD_NAND_OMAP_HWECC
I am surprised
-Original Message-
From: Grazvydas Ignotas [mailto:nota...@gmail.com]
Sent: Friday, November 19, 2010 4:06 PM
To: Ghorai, Sukumar
Cc: Charles Manning; linux-omap@vger.kernel.org
Subject: Re: No more software ECC in omap2.c NAND driver. Why?
On Thu, Nov 18, 2010 at 4:33 PM
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Charles Manning
Sent: Thursday, November 18, 2010 6:36 AM
To: linux-omap@vger.kernel.org
Subject: No more software ECC in omap2.c NAND driver. Why?
Between 2.6.35
Between 2.6.35 and 2.6.36 there have need quite a few changes in the NAND
driver, including a change from software to hardware ECC.
The new code has hardware ECC forced on by:
#define CONFIG_MTD_NAND_OMAP_HWECC
I am surprised that this was done. Surely this should have been a Kconfig
option
10 matches
Mail list logo
