From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] no flush_cache() call at the end of do_fat_fsload?
Date: Thu, 29 Jan 2009 16:44:05 +0100 [thread overview]
Message-ID: <200901291644.05934.sr@denx.de> (raw)
In-Reply-To: <43EB80E07C42E1408726E4905FB96B04C0728A@CYBORG3.cyclone.com>
Hi Scott,
On Thursday 29 January 2009, Scott Coulter wrote:
> Maybe a stupid question, but does anyone no why there is no call to
> flush_cache() at the end of do_fat_fsload()?
A bug perhaps?
> I haven't tried it on the
> latest u-boot, but I had an issue the other day where I was trying to
> load a VxWorks image from a Compact Flash card on a MPC8572-based board.
> The same image booted fine with tftpboot, but when I loaded the image
> off of the CF card using the fatload command, the image didn't boot. I
> confirmed that image was copied faithfully into DRAM. I then noticed
> that the tftpload command (netboot_common) has a call to flush_cache()
> after the download to memory completes, so I added the following to the
> end of do_fat_fsload():
>
> ...
>
> /* flush cache */
> flush_cache(offset, size);
>
> return 0;
> }
>
> Then the image booted...
Makes perfect sense. Best would be if you could send a proper patch to fix
this.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2009-01-29 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:47 [U-Boot] no flush_cache() call at the end of do_fat_fsload? Scott Coulter
2009-01-29 15:44 ` Stefan Roese [this message]
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=200901291644.05934.sr@denx.de \
--to=sr@denx.de \
--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.