From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Erickson Date: Thu, 26 Jun 2008 09:55:52 -0700 Subject: [U-Boot-Users] Performance in Booting Linux w/ Device Tree via U-Boot out of JFFS2 on NAND In-Reply-To: <517DC3FCCF3D8D42BEF1F83F7A633FA80470DD56@svexch01.mvista.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 6/26/08 8:33 AM, Mark Craske wrote: > I have a custom board that only has NAND flash, so my JFFS2 file systems are > in NAND. > > You say in your mail item of Fri, 07 Mar 2008 17:09:42 -0800 that you are > using > u-boot/fs/jffs2/jffs2_nand_1pass.c from u-boot (1.3.2-rc3). However, when I > change > the u-boot/fs/jffs2/Makefile to build jffs2_nand_1pass.o instead of > jffs2_1pass.o it > does not build. > > Have you modified jffs2_nand_1pass.c from the version in 1.3.2-rc3? Mark: At this point, for performance reasons, I abandoned any effort to use JFFS2 out of u-boot to boot images via 'fsload'. So, as of today, I am running u-boot-1.3.3 and am booting a boot.itb "multi-image" containing a compressed Linux kernel + FDT DTB out of NAND using 'nboot': => printenv bootaddr bootcmd boot0 boot1 bootaddr=800000 bootcmd=run boot0 || run boot1 || reset boot0=nboot.i ${bootaddr} 0 0 && setenv bootargs root=/dev/mtdblock9 && run addjffs2 addtty && bootm ${bootaddr} boot1=nboot.i ${bootaddr} 0 1C00000 && setenv bootargs root=/dev/mtdblock11 && run addjffs2 addtty && bootm ${bootaddr} During the time I was evaluating JFFS2 on the AMCC PowerPC 405EXr Haleakala board, I do not recall having any compilation issues or having to tweak the build beyond the necessary CONFIG_/CFG_ settings. Regards, Grant