From: Hector Palacios <hector.palacios@digi.com>
To: Huang Shijie <b32955@freescale.com>
Cc: "fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Marek Vasut <marex@denx.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: gpmi-nand driver and jffs2 support
Date: Fri, 30 Aug 2013 16:24:53 +0200 [thread overview]
Message-ID: <5220AB35.9080409@digi.com> (raw)
In-Reply-To: <52206C05.8020701@freescale.com>
Dear Huang,
On 08/30/2013 11:55 AM, Huang Shijie wrote:
> 于 2013年08月30日 17:15, Hector Palacios 写道:
>> Hello,
>>
>> Working on my custom platform based on i.MX28 (and also with the
>> MX28EVK) I checked that I cannot mount JFFS2 nand partitions because
>> I'm getting this error:
>>
>> jffs2: inconsistent device description
>>
>> which seems to have to do with the OOB area of the NAND.
>> I saw patchset [1] from Huang Shijie which seems to be related to the
>> issue. I just wanted to confirm if other people has the same problem
>> and if the patchset really aims to solve this, or mine is a different
>> issue.
>>
> yes, this patch set aims to solve this.
>
> You can try the SLC on the imx28.
>
> I only tested the SLC On the imx6q.
I applied the patchset but I still get the same error when trying to mount a JFFS2
filesystem. My nand is:
[ 0.819654] ONFI param page 0 valid
[ 0.823179] ONFI flash detected
[ 0.826344] NAND device: Manufacturer ID: 0x2c,Chip ID: 0xaa (Micron MT29F2G08ABBEAH4)
[ 0.834455] NAND device: 256MiB, SLC, page size: 2048, OOB size: 64
The same happens on the MX28EVK where I use nand:
[ 0.894127] NAND device: Manufacturer ID: 0xec,Chip ID: 0xdc (Samsung NAND 512MiB
3,3V 8-bit)
[ 0.902876] NAND device: 512MiB, SLC, page size: 2048, OOB size: 64
~# mount -t jffs2 /dev/mtdblock4 /media/nand/
[ 26.821947] jffs2: inconsistent device description
mount: mounting /dev/mtdblock4 on /media/nand/ failed: Invalid argument
Am I missing anything?
Best regards,
--
Hector Palacios
next prev parent reply other threads:[~2013-08-30 14:25 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 [this message]
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
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=5220AB35.9080409@digi.com \
--to=hector.palacios@digi.com \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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