From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] POST tests without OCM
Date: Mon, 17 Dec 2007 07:53:35 +0100 [thread overview]
Message-ID: <200712170753.36216.sr@denx.de> (raw)
In-Reply-To: <67BFAF42E016FC40ADE4EE73E07B706001024928@pks00005.kanatek.com>
On Saturday 15 December 2007, Craig Millen wrote:
> Yes I am using the 440EP. I was referring to all the code in
> cpu/ppc4xx/commproc.c, like this section:
>
> #if defined(CONFIG_POST) || defined(CONFIG_LOGBUFFER)
> void post_word_store (ulong a)
> {
> volatile void *save_addr = (volatile void *)(CFG_OCM_DATA_ADDR +
> CFG_POST_WORD_ADDR);
> *(volatile ulong *) save_addr = a;
> }
>
> ulong post_word_load (void)
> {
> volatile void *save_addr = (volatile void *)(CFG_OCM_DATA_ADDR +
> CFG_POST_WORD_ADDR);
> return *(volatile ulong *) save_addr;
> }
Yes, I was referring to this code too.
> There are a few more functions in there that refer to the OCM.
> What/where is the unused GPT that you are talking about?
GPT == General Purpose Timer. For example the GPT0_COMP6 register. But this is
of course application/OS dependant. Could be that your application (Linux
etc) is using this GPT register. But I doubt it.
BTW: We have an ACK from AMCC that the content of these registers is retained
even during reset.
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-12-17 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 16:32 [U-Boot-Users] POST tests without OCM Craig Millen
2007-12-17 6:53 ` Stefan Roese [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 19:32 Craig Millen
2007-12-14 21:03 ` Stefan Roese
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=200712170753.36216.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