[U-Boot-Users] fsload questions

[Wolfgang Denk]

In message <A590D28B5042C041BCC880094CB6172E33DF45 at mail1irv.inside.istor.com> you wrote:
> 
> But it takes almost 2 minutes to scan the flash before the fsload
> completes and loads the uImage. So, this adds an additional 2 minutes to

How big is your file system, and how heavily fragmented might  it  be
(how  long  have  you been using it, especially appending to existing
files?). And which version of the MTD code are you using?

> the boot of the embedded system, which is clearly a problem.

Indeed. This is why I try to avoid loading a Linux kernel image  from
a  JFFS2  file  system  (not to mention the fact that it makes little
sense to compress and already compressed image - it just adds to  the
delay).

> The flash was formatted in Linux using the flash_eraseall utility. I am
> hoping that you, or someone else, can tell me that there is some
> configuration constant missing or that the flash may be formatted in a
> way that is not quite consistent with U-Boot's needs.

There are a lot of  potential  causes.  Enable  debugging  and  check
what's taking so much time...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Our universe is a fragile house of atoms, held together by the mortar
of cause-and-effect. One magician would be two too many.
                        - Terry Pratchett, _The Dark Side of the Sun_