From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ppc: using d-cache for C stack and as cache at the same time?
Date: Wed, 01 Apr 2009 11:42:41 +0200 [thread overview]
Message-ID: <49D33711.9040806@tqs.de> (raw)
In-Reply-To: <20090401091436.7163683797DC@gemini.denx.de>
Dear Wolfgang Denk,
Wolfgang Denk schrieb:
> Dear Jens Gehrlein,
>
> In message <49D323E5.9080100@tqs.de> you wrote:
>> AFAIK, while running from flash, u-boot uses (part of) d-cache on some
>> platforms for the C stack. I think, it's on MPC83xx and MPC85xx?
>>
>> Does anybody know, if I can use the remaining part of the d-cache
>> as normal d-cache, e.g. to generate bursts on the SDRAM interface
>> while testing the RAM?
>
> On which platform?
>
> Note that implementing a memory test that actually triggers burst
> mode accesses is really, really tricky. You probably do NOT want to
> do this while running from flash (i. e. from a very restrictive
> envrionment).
Why not? Of course, it's only possible if I can use a part of the
D-Cache as C stack (or another internal RAM if available). This must
be separately checked for each processor.
> You might want to have a look at examples/test_burst*
> but note that this code was written for a MPC8xx system, so changes
> will be required for 83xx or 85xx.
Thank you for the hint. I'll have a look.
> Also note that a much more reliable test for burst mode errors is to
> boot Linux with root file system over NFS and then compile the Linux
> kernel on the target.
I agree.
Kind regards,
Jens
prev parent reply other threads:[~2009-04-01 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 8:20 [U-Boot] ppc: using d-cache for C stack and as cache at the same time? Jens Gehrlein
2009-04-01 9:14 ` Wolfgang Denk
2009-04-01 9:29 ` [U-Boot] ppc: using d-cache for C stack and as cache at thesame time? Liu Dave-R63238
2009-04-01 9:47 ` Jens Gehrlein
2009-04-01 14:48 ` Peter Tyser
2009-04-01 15:03 ` Jens Gehrlein
2009-04-01 9:42 ` Jens Gehrlein [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=49D33711.9040806@tqs.de \
--to=sew_s@tqs.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.