From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot for Mips 4KEC
Date: Wed, 03 Nov 2004 15:58:11 +0100 [thread overview]
Message-ID: <20041103145816.33530C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 03 Nov 2004 18:10:00 +0530." <cmajjb$oie$1@sea.gmane.org>
Dear Pooja,
in message <cmajjb$oie$1@sea.gmane.org> you wrote:
>
> In the process of porting U-boot for Malta which uses mips 4Kec I
> discovered that the stack required for intial C environment can neither
> be obtained by some on-chip memory (IMMR in MPC8xx ) nor by using DCACHE
> in locked mode. Mips 4KC has the DCache locked mode support but Mips
> 4KEC has it only through external pin interface.
I have o admit that I don't know the details of this specirfic CPU,
but are you _really_ sure that there is no way to lock (parts of) the
data cache? I would be relly suprised if this was the case...
> I am looking for a way of not using the C code till code has started
> running from RAM. But how do I get the value of gd(global data pointer)
This "way" is a major redesign and rewrite of U-Boot.
> which U-boot expects? README file does not mention anything about mips
> registers which are specifially used for this purpose.
No matter what you do, sooner or later you will find that you need
some preliminary stack and eventually storage space for a few
variables. So instead of creating several new problems, I recommend
to try to fix the root problem first, and all the rest will fall in
place.
Best regards,
Wolfgang Denk
--
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
An Elephant is a mouse with an Operating System. - Knuth
next prev parent reply other threads:[~2004-11-03 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 12:40 [U-Boot-Users] U-boot for Mips 4KEC calvin
2004-11-03 14:58 ` Wolfgang Denk [this message]
2004-11-03 16:13 ` Thomas Lange
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=20041103145816.33530C1430@atlas.denx.de \
--to=wd@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