Issue : jffs2 and ecc layout

[Ghorai, Sukumar]

> -----Original Message-----
> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
> owner at vger.kernel.org] On Behalf Of Ghorai, Sukumar
> Sent: Tuesday, September 28, 2010 6:17 PM
> To: linux-mtd at lists.infradead.org
> Cc: linux-omap at vger.kernel.org
> Subject: Issue : jffs2 and ecc layout
> 
> Hi,
> I was using the following ecc layout which is not working to mount the
> jffs2 File-system. I was in 2.6.32 kernel and working; but same layout is
> not working with latest 2.6 kernel.
> 
> Observation is that - no read request issued to the driver (say omap2.c).
> 
> # mount -t jffs2 /dev/mtdblock4 /mnt/nand
> [   32.505218] cannot read OOB for EB at 00000000, requested 8 bytes, read
> 0 bytes, error -22
> mount: Mounting /dev/mtdblock4 on /mnt/nand failed: Input/output error
> 
> # dmesg
> <3>[   32.505218] cannot read OOB for EB at 00000000, requested 8 bytes,
> read 0 bytes, error -22
> 
> Code:
>  178 static struct nand_ecclayout hw_x16_romcode_oob_64 = {
>  179         .eccbytes = 12,
>  180         .eccpos = {
>  181                     2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
>  182                   },
>  183         .oobfree = {
>  184                         {.offset = 14,
>  185                          .length = 50}
>  186                    }
>  187 };
> 
>  1188              info->nand.ecc.layout = &hw_x16_romcode_oob_64;
[Ghorai] 
Does anyone using similar layout for Jffs2? i.e. ECC store at beginning of the spare area?


> 
> Regards,
> Ghorai
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html