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>, Huang Shijie <shijie8@gmail.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"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: Mon, 2 Sep 2013 12:10:41 +0200 [thread overview]
Message-ID: <52246421.1020900@digi.com> (raw)
In-Reply-To: <52245171.3050900@freescale.com>
Dear Huang,
On 09/02/2013 10:50 AM, Huang Shijie wrote:
> 于 2013年09月02日 16:42, Hector Palacios 写道:
>> I am writing the JFFS2 partition from my custom U-Boot. Do you mean
>> that they way it writes it could not be compatible with what the new
>> driver expects? That sounds really bad.
>
> The mtd code(as well as the gpmi driver) has merge many patch to the kernel,
> BUT, the relative patches are not submitted to uboot maillist. So the
> code is not aligned between the
> uboot and the kernel.
Ok, I just rewrote the JFFS2 partition using the mtd-utils and now it mounts correctly
and without any error.
So does this mean that U-Boot is now unable to properly write a JFFS2 partition for it
to be understood by the linux-next kernel? What is exactly the difference? Does it
only affect Freescale NAND controllers?
I'm including the U-Boot mailing list in CC.
The complete thread for reference: http://patchwork.ozlabs.org/patch/271322/
Best regards,
--
Hector Palacios
next prev parent reply other threads:[~2013-09-02 10:11 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 [this message]
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=52246421.1020900@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=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