public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/2] imx: fix exception vectors relocation in imx27
Date: Thu, 20 Nov 2014 13:08:47 +0100	[thread overview]
Message-ID: <20141120130847.6bdcd7d2@lilith> (raw)
In-Reply-To: <546602A4.1030404@denx.de>

Hello Stefano,

On Fri, 14 Nov 2014 14:24:52 +0100, Stefano Babic <sbabic@denx.de>
wrote:
> Hi Albert,
> 
> On 14/11/2014 13:10, Albert ARIBAUD wrote:
> >> I'll have a look at the i.MX25, i.MX31 and i.MX35 reference manuals,
> >> but at most that will only tell me if they have the same problem as
> >> i.MX27 has about ROM/RAM and low/high vectors; it probably won't tell
> >> me how their ROM code handles exceptions.
> > 
> > According to the i.MX25, i.MX31 and i.MX35 RM, all three SoCs have ROM
> > at address 0x00000000 and no RAM at address 0xffff0000, so they most
> > certainly have the same kind of issue as i.MX27, but there is no
> > indication that the indirect vectors table is always the same, and it
> > is quite probable that it is located at a different place for each SoC.
> > 
> > So in order to solve the issue, we would need a dump (or better yet a
> > disassembly) of ROM addresses 0x00000000 to 0x0000001F for each of the
> > three SoCs.
> > 
> 
> ok - I have a MX35 based board, and I can do some tests, maybe in the
> week-end.

(thanks for applying my patch) Did you do the tests on i.MX35? Should
there be a followup patch to fix i.MX35 as i.MX27 i now fixed?

> Best regards,
> Stefano

Amicalement,
-- 
Albert.

  parent reply	other threads:[~2014-11-20 12:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 16:46 [U-Boot] [PATCH v1 0/2] Fix SoC-specific exception handling Albert ARIBAUD
2014-11-11 16:46 ` [U-Boot] [PATCH v1 1/2] cosmetic: arm: fix whitespace in arch/arm/lib/relocate.S Albert ARIBAUD
2014-11-11 16:46 ` [U-Boot] [PATCH v1 2/2] imx: fix exception vectors relocation in i.MX27 Albert ARIBAUD
2014-11-11 18:02   ` trem
2014-11-11 18:13     ` Albert ARIBAUD
2014-11-11 18:19 ` [U-Boot] [PATCH v2 0/2] Fix SoC-specific exception handling Albert ARIBAUD
2014-11-11 18:19   ` [U-Boot] [PATCH v2 1/2] cosmetic: arm: fix whitespace in arch/arm/lib/relocate.S Albert ARIBAUD
2014-11-11 18:19   ` [U-Boot] [PATCH v2 2/2] imx: fix exception vectors relocation in imx27 Albert ARIBAUD
2014-11-13 16:59   ` [U-Boot] [PATCH v3 0/2] Fix SoC-specific exception handling Albert ARIBAUD
2014-11-13 16:59     ` [U-Boot] [PATCH v3 1/2] cosmetic: arm: fix whitespace in arch/arm/lib/relocate.S Albert ARIBAUD
2014-11-21  9:01       ` Albert ARIBAUD
2014-11-21  9:04         ` Albert ARIBAUD
2014-11-13 16:59     ` [U-Boot] [PATCH v3 2/2] imx: fix exception vectors relocation in imx27 Albert ARIBAUD
2014-11-14  9:13       ` Stefano Babic
2014-11-14 11:49         ` Albert ARIBAUD
2014-11-14 12:10           ` Albert ARIBAUD
2014-11-14 13:24             ` Stefano Babic
2014-11-14 21:20               ` Fabio Estevam
2014-11-20 12:08               ` Albert ARIBAUD [this message]
2014-11-21  9:08                 ` Stefano Babic
2014-11-14 18:13       ` Philippe Reynes
2014-11-14 18:29       ` Philippe Reynes
2014-11-20  9:35       ` Stefano Babic
2014-11-13 17:05     ` [U-Boot] [PATCH v3 0/2] Fix SoC-specific exception handling 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=20141120130847.6bdcd7d2@lilith \
    --to=albert.u.boot@aribaud.net \
    --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