From: Wolfgang Denk <wd@denx.de>
To: ADharankar@ATTBI.Com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Relocating PPCBoot into SRAM
Date: Sun, 16 Feb 2003 20:48:03 +0100 [thread overview]
Message-ID: <20030216194808.33949C5E20@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 16 Feb 2003 14:15:19 EST." <200302161415.19790.ADharankar@ATTBI.Com>
In message <200302161415.19790.ADharankar@ATTBI.Com> you wrote:
> Hello! Thanks for the nice reply!
You're welcome.
> To test the region of SDRAM where PPCBoot/U-Boot resides, how could
> a non-destructive test be implemented? Perhaps, would one way would be
> to do these test for that region of PPCBoot/U-Boot before it is
> relocated to SDRAM?
This is a good idea, especially since you also have to deal with the
exception vectors...
> Some of the x86 PC BIOSs/Bootloaders/Monitors seem to be able to do
> a full/destructive memory test without a reboot. That is what seems
> to be appealing to for PPCBoot/U-Boot.
Did you check how U-Boot's POST routines (especially post/memory.c)
work?
Don't re-invent the wheel.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
See us @ Embedded World, Nuremberg, Feb 18-20, Hall 12.0 Booth 12-442
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-02-16 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302161415.19790.ADharankar@ATTBI.Com>
2003-02-16 19:48 ` Wolfgang Denk [this message]
2003-02-18 23:27 Relocating PPCBoot into SRAM Kerl, John
2003-02-19 2:36 ` Arun Dharankar
-- strict thread matches above, loose matches on Subject: below --
2003-02-16 17:54 Arun Dharankar
2003-02-16 18:37 ` 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=20030216194808.33949C5E20@atlas.denx.de \
--to=wd@denx.de \
--cc=ADharankar@ATTBI.Com \
--cc=linuxppc-embedded@lists.linuxppc.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).