From: Jerry Van Baren <vanbaren_gerald@si.com>
To: Dan Malek <dan@netx4.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PLPRCR & Checkstop reset
Date: Tue, 27 Jun 2000 15:35:20 -0400 [thread overview]
Message-ID: <4.3.2.20000627151503.00b6abc0@falcon.si.com> (raw)
In-Reply-To: <3958FD77.97001F7A@netx4.com>
It is unfortunate that there apparently is no standard. The only item
that I'm concerned with at the moment is the 8260 IMMR which is
readable but only if you know where it is first, in which case there is
no need to read it. :-(
Due to (a) laziness and (b) heredity (the board's, not mine), the power
up IMMR value on the systems I'm using is not the proper value for
running linux so we change it as part of our custom startup. This code
cannot be re-run on a warm start because the IMMR is already moved. If
there is no standard way to distinguish a warm start from a cold start
(e.g. different entry points), we will have to stash a special flag in
RAM that, if it is set to a magic number, tells us not to mess with the
IMMR because it is already correct.
gvb
At 03:16 PM 6/27/00 -0400, Dan Malek wrote:
>Jerry Van Baren wrote:
>
> > It would be better to not jump to the reset vector on a warm
> > start.
>
>Yes, but there isn't any standard among the 8xx boot roms.
>
>This seems to work on all of the boards I have ever tested. If
>it doesn't work for you, let's discuss it and find something that
>does.
>
>
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-27 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-25 21:33 PLPRCR & Checkstop reset Mark S. Mathews
2000-06-26 19:13 ` Dan Malek
2000-06-27 17:41 ` Mark S. Mathews
2000-06-27 17:11 ` Dan Malek
2000-06-27 17:50 ` Dan Malek
2000-06-27 18:50 ` Jerry Van Baren
2000-06-27 19:16 ` Dan Malek
2000-06-27 19:35 ` Jerry Van Baren [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=4.3.2.20000627151503.00b6abc0@falcon.si.com \
--to=vanbaren_gerald@si.com \
--cc=dan@netx4.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).