From: Wolfgang Denk <wd@denx.de>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: simple bootloader 2.6.10-rc3 8xx
Date: Tue, 28 Dec 2004 18:48:50 +0100 [thread overview]
Message-ID: <20041228174855.83AF4C14EC@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 28 Dec 2004 12:28:37 EST." <313680C9A886D511A06000204840E1CF0A647421@whq-msgusr-02.pit.comms.marconi.com>
In message <313680C9A886D511A06000204840E1CF0A647421@whq-msgusr-02.pit.comms.marconi.com> you wrote:
>
> I guess I need some more education - since I am getting my problem right at
> the boot - is
> I-Cache enabled (by default ?) for 8xx on 2.6 at the booting ? - I do not
They get turned on very early.
> see anything in .config
> which controls it (or I am missing it there ?)
No. This is not configurable.
> How (where and at what point during the boot)-) I could disable I-Cache ?
Search for IC_CST in "arch/ppc/kernel/head_8xx.S"
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Every program has at least one bug and can be shortened by at least
one instruction - from which, by induction, one can deduce that every
program can be reduced to one instruction which doesn't work.
next prev parent reply other threads:[~2004-12-28 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 17:28 simple bootloader 2.6.10-rc3 8xx Povolotsky, Alexander
2004-12-28 17:47 ` Steven Rostedt
2005-01-05 17:36 ` Tom Rini
2004-12-28 17:48 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 0:53 Povolotsky, Alexander
2004-12-28 9:51 Wolfgang Denk
2004-12-28 17:12 ` paul.bilke
2004-12-28 3:52 Povolotsky, Alexander
2004-12-27 20:38 Povolotsky, Alexander
2004-12-28 3:30 ` paul.bilke
2004-12-28 9:13 ` 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=20041228174855.83AF4C14EC@atlas.denx.de \
--to=wd@denx.de \
--cc=Alexander.Povolotsky@marconi.com \
--cc=linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).