From: Huang Shijie <b32955@freescale.com>
To: Marek Vasut <marex@denx.de>
Cc: "fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Hector Palacios <hector.palacios@digi.com>,
linux-mtd@lists.infradead.org
Subject: Re: gpmi-nand driver and jffs2 support
Date: Tue, 24 Sep 2013 18:46:32 +0800 [thread overview]
Message-ID: <52416D88.6030906@freescale.com> (raw)
In-Reply-To: <201309241150.09313.marex@denx.de>
于 2013年09月24日 17:50, Marek Vasut 写道:
> Hello Huang,
>
> Can you please explain what is the exact difference between the NAND layout when
> using JFFS2 in FSL 2.6.35 and in mainline with your patches ?
In FSL 2.6.35, there are some free space in the OOB;
while in mainline we use all the free space in the OOB.
> Is there any way to mount JFFS2 written with FSL 2.6.35 on current mainline?
> Thus far, neither me nor Hector were able to mount such partition with the same
> result.
The gpmi driver in FSL 2.6.35 is different from the mainline.
The two drivers are not compatible to each other.
thanks
Huang Shijie
> Best regards,
> Marek Vasut
>
next prev parent reply other threads:[~2013-09-24 10:44 UTC|newest]
Thread overview: 58+ 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
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:10 ` [U-Boot] " Hector Palacios
2013-09-02 10:23 ` Huang Shijie
2013-09-02 10:23 ` [U-Boot] " Huang Shijie
2013-09-02 11:32 ` Marek Vasut
2013-09-02 11:32 ` [U-Boot] " Marek Vasut
2013-09-03 2:06 ` Huang Shijie
2013-09-03 2:06 ` [U-Boot] " Huang Shijie
2013-09-03 11:53 ` Marek Vasut
2013-09-03 11:53 ` [U-Boot] " Marek Vasut
2013-09-04 2:26 ` Huang Shijie
2013-09-04 2:26 ` [U-Boot] " Huang Shijie
2013-09-04 14:00 ` Marek Vasut
2013-09-04 14:00 ` [U-Boot] " Marek Vasut
2013-09-05 2:41 ` Huang Shijie
2013-09-05 2:41 ` [U-Boot] " Huang Shijie
2013-09-04 14:38 ` Marek Vasut
2013-09-04 14:38 ` [U-Boot] " Marek Vasut
2013-09-04 15:46 ` Hector Palacios
2013-09-04 15:46 ` [U-Boot] " Hector Palacios
2013-09-05 6:01 ` Huang Shijie
2013-09-05 6:01 ` [U-Boot] " Huang Shijie
2013-09-15 14:18 ` Marek Vasut
2013-09-15 14:18 ` [U-Boot] " Marek Vasut
2013-09-16 2:35 ` Huang Shijie
2013-09-16 2:35 ` [U-Boot] " Huang Shijie
2013-09-19 16:07 ` Marek Vasut
2013-09-19 16:07 ` [U-Boot] " Marek Vasut
2013-09-19 16:13 ` Hector Palacios
2013-09-19 16:13 ` [U-Boot] " Hector Palacios
2013-09-19 16:14 ` Hector Palacios
2013-09-19 16:14 ` [U-Boot] " Hector Palacios
2013-09-19 16:16 ` Marek Vasut
2013-09-19 16:16 ` [U-Boot] " Marek Vasut
2013-09-19 17:20 ` Marek Vasut
2013-09-19 17:20 ` [U-Boot] " Marek Vasut
2013-09-15 14:12 ` Marek Vasut
2013-09-15 14:12 ` [U-Boot] " Marek Vasut
2013-08-31 17:51 ` Huang Shijie
2013-09-24 9:50 ` Marek Vasut
2013-09-24 10:46 ` Huang Shijie [this message]
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=52416D88.6030906@freescale.com \
--to=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=hector.palacios@digi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.