From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx35: Fix boot hang by avoiding vector relocation
Date: Sun, 01 Mar 2015 16:45:09 +0100 [thread overview]
Message-ID: <54F33405.50704@denx.de> (raw)
In-Reply-To: <1424693349-12252-2-git-send-email-fabio.estevam@freescale.com>
Hi Fabio,
On 23/02/2015 13:09, Fabio Estevam wrote:
> Since commit 3ff46cc42b9d73d0 ("arm: relocate the exception vectors") mx35
> does not boot anymore.
>
> Add a specific relocate_vectors macro that skips the vector relocation, as the
> i.MX35 SoC does not provide RAM at the high vectors address (0xFFFF0000), and
> (0x00000000) maps to ROM.
>
> This allows mx35 to boot again.
>
> Cc: Sebastian Priebe <sebastian.priebe@cadcon.de>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Sebastian,
>
> I don't have access to a mx35 board.
>
> Could you please test this patch?
>
> Thanks
>
Thanks for the patch !
I have found again a mx35pdk and I could test your patch. 2015.04-rc1
is running on that.
Tested-by: Stefano Babic <sbabic@denx.de>
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2015-03-01 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:09 [U-Boot] [PATCH 1/2] mx31: Fix boot hang by avoiding vector relocation Fabio Estevam
2015-02-23 12:09 ` [U-Boot] [PATCH 2/2] mx35: " Fabio Estevam
2015-03-01 15:45 ` Stefano Babic [this message]
2015-02-23 13:03 ` [U-Boot] [PATCH 1/2] mx31: " Anatolij Gustschin
2015-02-24 17:40 ` Magnus Lilja
2015-03-02 9:45 ` Stefano Babic
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=54F33405.50704@denx.de \
--to=sbabic@denx.de \
--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