From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: bugfix: Move vector table before jumping relocated code
Date: Mon, 25 Jun 2012 09:10:26 -0600 [thread overview]
Message-ID: <4FE87F62.6060200@wwwdotorg.org> (raw)
In-Reply-To: <4FE85C59.1010400@kmckk.co.jp>
On 06/25/2012 06:40 AM, Tetsuyuki Kobayashi wrote:
> Interrupts and exceptions doesn't work in relocated code.
> It badly use IRQ_STACK_START_IN in rom area as interrupt stack.
> It is because the vecotr table is not moved to ram area.
> This patch moves vector table before jumping relocated code.
>
> Signed-off-by: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
CC'ing in some Tegra people.
Tetsuyuki, you probably want to CC some OMAP people too.
> ---
> arch/arm/cpu/armv7/start.S | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm/cpu/armv7/start.S b/arch/arm/cpu/armv7/start.S
> index 52f7f6e..5098f7b 100644
> --- a/arch/arm/cpu/armv7/start.S
> +++ b/arch/arm/cpu/armv7/start.S
> @@ -277,6 +277,18 @@ jump_2_ram:
> mcr p15, 0, r0, c7, c10, 4 @ DSB
> mcr p15, 0, r0, c7, c5, 4 @ ISB
> #endif
> +/*
> + * Move vector table
> + */
> +#if !defined(CONFIG_TEGRA2)
> +#if !(defined(CONFIG_OMAP44XX) && defined(CONFIG_SPL_BUILD))
> + /* Set vector address in CP15 VBAR register */
> + ldr r0, =_start
> + add r0, r0, r9
> + mcr p15, 0, r0, c12, c0, 0 @Set VBAR
> +#endif
> +#endif /* !Tegra2 */
> +
> ldr r0, _board_init_r_ofs
> adr r1, _start
> add lr, r0, r1
next prev parent reply other threads:[~2012-06-25 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:40 [U-Boot] [PATCH] arm: bugfix: Move vector table before jumping relocated code Tetsuyuki Kobayashi
2012-06-25 15:10 ` Stephen Warren [this message]
2012-06-26 1:03 ` Tetsuyuki Kobayashi
2012-06-26 16:24 ` Stephen Warren
2012-07-05 9:27 ` Albert ARIBAUD
2012-06-27 18:23 ` Tom Rini
2012-06-28 1:27 ` Tetsuyuki Kobayashi
2012-12-21 15:17 ` Joel A Fernandes
2012-12-25 23:18 ` Tetsuyuki Kobayashi
2012-12-26 0:08 ` Joel A Fernandes
2012-07-05 12:00 ` Albert ARIBAUD
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=4FE87F62.6060200@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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