From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] gpmi-nand driver and jffs2 support
Date: Mon, 2 Sep 2013 13:32:33 +0200 [thread overview]
Message-ID: <201309021332.34063.marex@denx.de> (raw)
In-Reply-To: <5224670F.6000703@freescale.com>
Dear Huang Shijie,
> ? 2013?09?02? 18:10, Hector Palacios ??:
> > 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
>
> For the gpmi nand controller, the uboot is not proper to write a jffs2 now.
>
> > kernel? What is exactly the difference? Does it only affect Freescale
> > NAND controllers?
>
> I think there are many difference. Just diff the nand_base.c, you can
> see there are many patches merged in
> the kernel's mtd code, but not exit in the uboot's mtd code.
This makes not much sense to me. If what you claim is true, than JFFS2 in U-Boot
and Linux would be incompatible for all MTD drivers. This would also mean that
JFFS2 in Linux 3.7 is incompatible with Linux-next (since 3.7 was the last sync
point between U-Boot and Linux MTD). Is that really the case?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-09-02 11:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <522062B4.4080709@digi.com>
[not found] ` <52206C05.8020701@freescale.com>
[not found] ` <5220AB35.9080409@digi.com>
[not found] ` <20130831025344.GA9971@gmail.com>
[not found] ` <5220B8F6.3080405@digi.com>
[not found] ` <20130831033438.GA13704@gmail.com>
[not found] ` <5220C8C4.5010305@digi.com>
[not found] ` <CAOMZO5CTQZBmvQc4y761kGHWYWRXr7GwVrTuTPE+JU=bmjq62w@mail.gmail.com>
[not found] ` <5220CB56.7040505@digi.com>
[not found] ` <20130831133728.GA22069@gmail.com>
[not found] ` <52244886.8060205@digi.com>
[not found] ` <52244B22.3020605@freescale.com>
[not found] ` <52244F85.4030904@digi.com>
[not found] ` <52245171.3050900@freescale.com>
2013-09-02 10:10 ` [U-Boot] gpmi-nand driver and jffs2 support Hector Palacios
2013-09-02 10:23 ` Huang Shijie
2013-09-02 11:32 ` Marek Vasut [this message]
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
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=201309021332.34063.marex@denx.de \
--to=marex@denx.de \
--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