From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hector Palacios Date: Mon, 2 Sep 2013 12:10:41 +0200 Subject: [U-Boot] gpmi-nand driver and jffs2 support In-Reply-To: <52245171.3050900@freescale.com> References: <522062B4.4080709@digi.com> <52206C05.8020701@freescale.com> <5220AB35.9080409@digi.com> <20130831025344.GA9971@gmail.com> <5220B8F6.3080405@digi.com> <20130831033438.GA13704@gmail.com> <5220C8C4.5010305@digi.com> <5220CB56.7040505@digi.com> <20130831133728.GA22069@gmail.com> <52244886.8060205@digi.com> <52244B22.3020605@freescale.com> <52244F85.4030904@digi.com> <52245171.3050900@freescale.com> Message-ID: <52246421.1020900@digi.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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