From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] powerpc/mpc85xx: Don't relocate exception vectors
Date: Mon, 20 Apr 2015 14:00:56 -0700 [thread overview]
Message-ID: <55356908.7040907@freescale.com> (raw)
In-Reply-To: <1428456001-1938-1-git-send-email-scottwood@freescale.com>
On 04/07/2015 06:20 PM, Scott Wood wrote:
> Booke does not require exception vectors to be located at address zero.
> U-Boot was doing so anyway, simply because that's how it had been done
> on other PPC. The downside of this is that once the OS is loaded to
> address zero, the exception vectors have been overwritten -- which
> makes it difficult to diagnose a crash that happens after that point.
>
> The IVOR setup and trap entry code is simplified somewhat as a result.
>
> Also, there is no longer a need to align individual exceptions on 0x100
> byte boundaries.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
Applied to mpc85xx master, awaiting upstream.
York
prev parent reply other threads:[~2015-04-20 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 1:20 [U-Boot] [PATCH 1/2] powerpc/mpc85xx: Don't relocate exception vectors Scott Wood
2015-04-08 1:20 ` [U-Boot] [PATCH 2/2] powerpc/mpc85xx: Remove some dead code Scott Wood
2015-04-20 21:01 ` York Sun
2015-04-20 21:00 ` York Sun [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=55356908.7040907@freescale.com \
--to=yorksun@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox