From: Grant Erickson <gerickson@nuovations.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Performance in Booting Linux w/ Device Tree via U-Boot out of JFFS2 on NAND
Date: Thu, 26 Jun 2008 09:55:52 -0700 [thread overview]
Message-ID: <C4891828.100A4%gerickson@nuovations.com> (raw)
In-Reply-To: <517DC3FCCF3D8D42BEF1F83F7A633FA80470DD56@svexch01.mvista.com>
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
next prev parent reply other threads:[~2008-06-26 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 15:33 [U-Boot-Users] Performance in Booting Linux w/ Device Tree via U-Boot out of JFFS2 on NAND Mark Craske
2008-06-26 16:55 ` Grant Erickson [this message]
[not found] <C3F56A1C.DD2F%gerickson@nuovations.com>
2008-03-08 1:09 ` Grant Erickson
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=C4891828.100A4%gerickson@nuovations.com \
--to=gerickson@nuovations.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