From: Nicholas Kinar <n.kinar@usask.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting kernel from NAND flash on AT91SAM9 custom board using fsload
Date: Tue, 29 Mar 2011 14:57:01 -0600 [thread overview]
Message-ID: <4D92479D.8000805@usask.ca> (raw)
In-Reply-To: <20110329154638.052e5cca@schlenkerla.am.freescale.net>
On 29/03/2011 2:46 PM, Scott Wood wrote:
> On Tue, 29 Mar 2011 14:35:26 -0600
> Nicholas Kinar<n.kinar@usask.ca> wrote:
>
>> I have two additional questions associated with booting the kernel from
>> NAND flash on my custom hardware:
>>
>> (1) Does replacing jffs2_1pass.c with jffs2_nand_1pass.c in the fs/jffs2
>> directory influence the robustness of the fsload code?
>>
>> (2) Does it take a long time to load the Linux kernel from a JFFS2
>> filesystem on NAND flash using the fsload command (i.e.
>> http://old.nabble.com/Performance-in-Booting-Linux-w--Device-Tree-via-U-Boot-out-of-JFFS2-on-NAND-td15879327.html),
>> or has this been cleaned up in the current u-boot-2010.09 code?
> I haven't used U-Boot's jffs2 support (the previous answer was from reading
> the source code), so I can't help here, sorry.
>
> -Scott
>
>
That is fine, Scott; your previous answer was extremely helpful, and I
think that I am now well on my way to booting the Linux kernel from NAND
flash on my new embedded system.
Thanks again,
Nicholas
next prev parent reply other threads:[~2011-03-29 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 16:14 [U-Boot] Booting kernel from NAND flash on AT91SAM9 custom board using fsload Nicholas Kinar
2011-03-29 17:37 ` Nicholas Kinar
2011-03-29 17:56 ` Scott Wood
2011-03-29 20:35 ` Nicholas Kinar
2011-03-29 20:46 ` Scott Wood
2011-03-29 20:57 ` Nicholas Kinar [this message]
2011-03-29 21:05 ` Wolfgang Denk
2011-03-29 21:46 ` Nicholas Kinar
2011-03-29 21:51 ` Wolfgang Denk
2011-04-02 17:38 ` Nicholas Kinar
2011-04-03 1:50 ` Nicholas Kinar
2011-04-04 1:25 ` Nicholas Kinar
2011-03-30 7:17 ` Joakim Tjernlund
2011-03-30 8:54 ` Wolfgang Denk
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=4D92479D.8000805@usask.ca \
--to=n.kinar@usask.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.