From: Marek Vasut <marex@denx.de>
To: Huang Shijie <b32955@freescale.com>
Cc: "fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Huang Shijie <shijie8@gmail.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Hector Palacios <hector.palacios@digi.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
scottwood@freescale.com, Fabio Estevam <festevam@gmail.com>
Subject: Re: gpmi-nand driver and jffs2 support
Date: Wed, 4 Sep 2013 16:00:36 +0200 [thread overview]
Message-ID: <201309041600.37107.marex@denx.de> (raw)
In-Reply-To: <52269A56.4030808@freescale.com>
Dear Huang Shijie,
> 于 2013年09月03日 19:53, Marek Vasut 写道:
> > questions comes to mind. Is JFFS2 support in Linux 3.7 not compatible
> > with JFFS2 in Linux -next? Is this true? Can I not mount JFFS2 partition
> > under Linux-next
>
> The jffs2 does not changed since the linux 3.7.
> All the changes happened in the drivers and mtd code.
OK, JFFS2 aside then, let's focus on MTD core code.
> The gpmi does not support the jffs2 all the time. Only apply the slc/mlc
> patch set,
> the gpmi can support the jffs2.
How come hector was then able to write his JFFS2 partition ?
> So the jffs2 support is compatiable all the time.
Is the old Freescale 2.6.35 GPMI NAND format compatible with the one after
applying this patchset?
> > that I could mount with Linux 3.7 and earlier?
>
> I think the mount can be succeeded.
Ok, does that mean that we need this patchset in U-Boot in order to properly
write JFFS2 onto GPMI NAND there? Is that the message you wanted to relay to us?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-09-04 14:01 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
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 [this message]
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=201309041600.37107.marex@denx.de \
--to=marex@denx.de \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=hector.palacios@digi.com \
--cc=linux-mtd@lists.infradead.org \
--cc=scottwood@freescale.com \
--cc=shijie8@gmail.com \
--cc=u-boot@lists.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