From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch] Disable icache before call the firstline of kernel in do_bootelf().
Date: Wed, 8 Aug 2007 20:19:15 +0200 [thread overview]
Message-ID: <200708082019.15585.sr@denx.de> (raw)
In-Reply-To: <20070808155405.B93A4352B18@atlas.denx.de>
On Wednesday 08 August 2007, Wolfgang Denk wrote:
> In message <200708081147.09111.rgetz@blackfin.uclinux.org> you wrote:
> > I think it is reasonable/prudent to turn off cache in all situations, on
> > all architectures.
>
> No, it is not. Some architectures / operating systems may require
> cache(s) being on. Some others may not care, except for boot speed
> which in turn is something some of the customers do care about.
>
> Finally, I don't want to fix a prblem where non exists.
I'm not totally sure here, but I remember seeing a problem with booting
VxWorks which could be related to having the icache still on. Or was it
QNX/Neutrino? Not sure anymore, too long ago. From my memory, all those other
OS'es I ever worked with, are much "happier" with interrupts and caches
disabled upon startup. It could be that we just forgot to disable the icache
in the initial port of the bootelf command.
Perhaps some users of those other OS'es (VxWorks, QNX...) could speak up and
suggest which implementation is recommended.
> If we know for sure that certain systems require caches disabeled,
> then let's provide them this environment; but please leave all the
> rest unchanged.
>
> > Instruction and data caches in U-Boot are a great thing, since it
> > decreases the time for a kernel or file system to be loaded,
> > decompressed, but once U-Boot looses control (the jump to the unknown
> > application), it shouldn't expect a return, or the hardware not to be
> > changed by the app.
>
> There is more than just Linux...
Yes. But the same reasons could apply to the other systems too. From my
understanding we are "on the safe side" with caches disabled.
> > go, bootm, boote, etc - should flush & turn off cache before the jump to
> > the application code (should also turn off what limited interrupts are
> > enabled) to be safe.
>
> I disagree.
I tend to agree with Robin here.
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
=====================================================================
next prev parent reply other threads:[~2007-08-08 18:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 5:50 [U-Boot-Users] [Patch] Disable icache before call the first line of kernel in do_bootelf() Sonic Zhang
2007-08-08 6:50 ` Wolfgang Denk
2007-08-08 7:21 ` Michal Simek
2007-08-08 15:47 ` [U-Boot-Users] [Patch] Disable icache before call the firstline " Robin Getz
2007-08-08 15:54 ` Wolfgang Denk
2007-08-08 18:19 ` Stefan Roese [this message]
2007-08-08 7:33 ` [U-Boot-Users] [Patch] Disable icache before call the first line " Sonic Zhang
2007-08-08 15:41 ` Wolfgang Denk
2007-08-13 14:52 ` Mike Frysinger
2007-08-13 15:50 ` Wolfgang Denk
2007-08-13 16:21 ` Mike Frysinger
2008-01-29 2:14 ` Mike Frysinger
2008-01-29 22:35 ` Wolfgang Denk
2008-01-30 0:12 ` Mike Frysinger
2008-01-30 15:36 ` Johannes Stezenbach
2008-02-01 15:42 ` Mike Frysinger
2008-02-01 15:44 ` [U-Boot-Users] [patch] allow ports to override bootelf behavior Mike Frysinger
2008-04-13 22:01 ` Wolfgang Denk
2008-02-01 15:58 ` [U-Boot-Users] [patch] allow ports to override go behavior Mike Frysinger
2008-02-01 16:36 ` Mike Frysinger
2008-04-13 22:01 ` Wolfgang Denk
2008-04-13 22:01 ` 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=200708082019.15585.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox