From: Hector Palacios <hector.palacios@digi.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Huang Shijie <b32955@freescale.com>, Marek Vasut <marex@denx.de>,
Huang Shijie <shijie8@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: gpmi-nand driver and jffs2 support
Date: Fri, 30 Aug 2013 18:41:58 +0200 [thread overview]
Message-ID: <5220CB56.7040505@digi.com> (raw)
In-Reply-To: <CAOMZO5CTQZBmvQc4y761kGHWYWRXr7GwVrTuTPE+JU=bmjq62w@mail.gmail.com>
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
> <hector.palacios@digi.com> 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
next prev parent reply other threads:[~2013-08-30 16:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 9:15 gpmi-nand driver and jffs2 support Hector Palacios
2013-08-30 9:55 ` Huang Shijie
2013-08-30 14:24 ` Hector Palacios
2013-08-31 2:53 ` Huang Shijie
2013-08-30 15:23 ` Hector Palacios
2013-08-31 3:34 ` Huang Shijie
2013-08-30 16:31 ` Hector Palacios
2013-08-30 16:37 ` Fabio Estevam
2013-08-30 16:41 ` Hector Palacios [this message]
2013-08-31 13:37 ` Huang Shijie
2013-09-02 8:12 ` Hector Palacios
2013-09-02 8:24 ` Huang Shijie
2013-09-02 8:42 ` Hector Palacios
2013-09-02 8:50 ` Huang Shijie
2013-09-02 10:10 ` Hector Palacios
2013-09-02 10:23 ` Huang Shijie
2013-09-02 11:32 ` Marek Vasut
2013-09-03 2:06 ` Huang Shijie
2013-09-03 11:53 ` Marek Vasut
2013-09-04 2:26 ` Huang Shijie
2013-09-04 14:00 ` Marek Vasut
2013-09-05 2:41 ` Huang Shijie
2013-09-04 14:38 ` Marek Vasut
2013-09-04 15:46 ` Hector Palacios
2013-09-05 6:01 ` Huang Shijie
2013-09-15 14:18 ` Marek Vasut
2013-09-16 2:35 ` Huang Shijie
2013-09-19 16:07 ` Marek Vasut
2013-09-19 16:13 ` Hector Palacios
2013-09-19 16:14 ` Hector Palacios
2013-09-19 16:16 ` Marek Vasut
2013-09-19 17:20 ` Marek Vasut
2013-09-15 14:12 ` Marek Vasut
2013-08-31 17:51 ` Huang Shijie
2013-09-24 9:50 ` Marek Vasut
2013-09-24 10:46 ` Huang Shijie
2013-09-24 12:53 ` Marek Vasut
2013-09-25 9:08 ` Huang Shijie
2013-09-29 22:52 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5220CB56.7040505@digi.com \
--to=hector.palacios@digi.com \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=shijie8@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox