From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1.bemta12.messagelabs.com ([216.82.251.17]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1VFRmR-0004qk-Qz for linux-mtd@lists.infradead.org; Fri, 30 Aug 2013 16:42:40 +0000 Message-ID: <5220CB56.7040505@digi.com> Date: Fri, 30 Aug 2013 18:41:58 +0200 From: Hector Palacios MIME-Version: 1.0 To: Fabio Estevam Subject: Re: gpmi-nand driver and jffs2 support References: <522062B4.4080709@digi.com> <52206C05.8020701@freescale.com> <5220AB35.9080409@digi.com> <20130831025344.GA9971@gmail.com> <5220B8F6.3080405@digi.com> <20130831033438.GA13704@gmail.com> <5220C8C4.5010305@digi.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: "fabio.estevam@freescale.com" , Huang Shijie , Marek Vasut , Huang Shijie , "linux-mtd@lists.infradead.org" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Fabio, On 08/30/2013 06:37 PM, Fabio Estevam wrote: > Hi Hector, > > On Fri, Aug 30, 2013 at 1:31 PM, Hector Palacios > wrote: >> Ok I merged the linux-next MTD patches. >> This is what I get from the printk: >> >> [ 0.841333] [ set_geometry_by_ecc_info ] 36, 28 >> >> The partition now partially mounts (I can see a few of the folders and >> files) but I get thousands of errors like these: >> >> [ 118.210985] jffs2: mtd->read(0x100 bytes from 0x0) returned ECC error >> [ 118.255424] jffs2: mtd->read(0x1ff20 bytes from 0xe0) returned ECC error >> [ 118.255561] jffs2: jffs2_scan_inode_node(): CRC failed on node at >> 0x000001ec: Read 0x00000000, calculated 0xa587e8ba >> [ 118.255602] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not >> found at 0x00000234: 0x1cf7 instead > > This error is most likely because you generated a jffs2 rootfs with a > eraseblock size that does not match the one of your NAND device. No. I used 128k erase block that matches my NAND. I also checked that I can mount the jffs2 partition correctly using my v2.6.35 kernel, so the partition seems to be correctly written. Best regards, -- Hector Palacios