From: "alayrac" <christophe.alayrac@cresitt.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: RE : Reset cause API
Date: Thu, 8 Mar 2007 15:39:10 +0100 [thread overview]
Message-ID: <000501c7618f$89492bc0$c900a8c0@CRESITTLAB> (raw)
In-Reply-To: <3E32AE64-2BE2-4B74-8AEC-4A42AF888010@kernel.crashing.org>
The PPC405 recognizes three types of reset:
=95 Aprocessor reset affects the processor only, including the execution
units and cache units. External devices (on-chip and off-chip) are not
affected. This type of reset is sometimes referred to as a core reset.
=95 Achip reset affects the processor and all other devices or =
peripherals
located on the same chip as the processor.
=95 Asystem reset affects the processor chip and all other devices or
peripherals external to the processor chip that are connected to the
same system-reset network. The scope of a system reset depends on the
system implementation.
The type of reset is recorded in the most-recent reset field of the
debug-status register (DBSR[MRR]). System software can examine this
field if it needs to determine the cause of a reset. The effect of a
reset on the processor is always the same regardless of the type.
For more details you can see ppc-ref-guide.pdf (in EDK doc directory).
Chris
CRESITT INDUSTRIE
12 Rue de Blois, BP6744
45067 ORLEANS Cedex 2
Tel : 02.38.49.45.59
Fax :02.38.49.45.55
Email : christophe.alayrac@cresitt.com=20
Web : http://www.cresitt.com
<----> -----Message d'origine-----
<----> De=A0: linuxppc-embedded-
<----> bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org
[mailto:linuxppc-
<----> embedded-bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org] De =
la
<----> part de Kumar Gala
<----> Envoy=E9=A0: jeudi 8 mars 2007 15:30
<----> =C0=A0: bwarren@qstreams.com
<----> Cc=A0: linuxppc-embedded@ozlabs.org
<----> Objet=A0: Re: Reset cause API
<---->=20
<---->=20
<----> On Mar 5, 2007, at 3:22 PM, Ben Warren wrote:
<---->=20
<----> > Hello,
<----> >
<----> > Is there an API call, either Linux or PowerPC-specific, for
<----> > determining
<----> > the cause of the last reset? I can certainly read the RSR
myself,
<----> but
<----> > why bother if the information's available elsewhere.
<---->=20
<----> There isnt anything like this since we don't have any consistent
way
<----> of maintaining information across a reset.
<---->=20
<----> Something like kexec could possibly do something.
<---->=20
<----> - k
<----> _______________________________________________
<----> Linuxppc-embedded mailing list
<----> Linuxppc-embedded@ozlabs.org
<----> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2007-03-08 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 21:22 Reset cause API Ben Warren
2007-03-08 14:29 ` Kumar Gala
2007-03-08 14:39 ` alayrac [this message]
2007-03-08 15:20 ` RE : " Ben Warren
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='000501c7618f$89492bc0$c900a8c0@CRESITTLAB' \
--to=christophe.alayrac@cresitt.com \
--cc=linuxppc-embedded@ozlabs.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