From: Frank Smith <smith@amirix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RE: Virtex-II Pro and Instruction Prefetching
Date: Sat, 14 Jun 2003 13:05:38 -0300 [thread overview]
Message-ID: <03Jun14.125612adt.7305@dragon.appliedmicro.ns.ca> (raw)
In-Reply-To: <20030614153555.70C72C5FD7@atlas.denx.de>
> -----Original Message-----
> From: wd at denx.de [mailto:wd at denx.de]
> > there's a bug in cpu/ppc4xx/start.S I've pointed out previously that
> > nobody has rendered an opinion on as of yet :-)
>
> You mean the STD_EXCEPTION vs. CRIT_EXCEPTION ?
>
> I am waiting for Stefan to pick this up :-)
>
> But actually it should not matter at all: your code is never supposed
> to run into such an exception. If it's crashing anyway there is
> little difference if it's crashing "correctly" or not ;-)
The problem with it crashing incorrectly is that the Oops message
lies to you, as it's reporting the contents of SRR0/SRR1, not SRR2/SRR3
as it should be for a critical exception. Makes it more difficult to
debug when you think the wrong instruction is causing the exception.
Thanks,
-Frank.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 6/5/03
next prev parent reply other threads:[~2003-06-14 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 12:27 [U-Boot-Users] Virtex-II Pro and Instruction Prefetching Frank Smith
2003-06-14 12:48 ` Robert Schwebel
2003-06-14 13:45 ` [U-Boot-Users] " Wolfgang Denk
2003-06-14 14:04 ` Frank Smith
2003-06-14 15:35 ` Wolfgang Denk
2003-06-14 16:05 ` Frank Smith [this message]
2003-06-16 9:45 ` [U-Boot-Users] " Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2003-06-16 15:52 Kerl, John
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=03Jun14.125612adt.7305@dragon.appliedmicro.ns.ca \
--to=smith@amirix.com \
--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.