From: Peter Maydell <peter.maydell@linaro.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] target_arm: Make the reset rom_ptr a property
Date: Thu, 21 Aug 2014 09:01:29 +0100 [thread overview]
Message-ID: <CAFEAcA-ymT8Kb_Ewf=6beJCWTdYERzJTk5svWpZ-PAE8bm3=Xw@mail.gmail.com> (raw)
In-Reply-To: <7dadfa99c7a31615e6df922fb6e2084837e08033.1408584788.git.alistair23@gmail.com>
On 21 August 2014 02:36, Alistair Francis <alistair23@gmail.com> wrote:
> This allows the board to set the reset address, which is required
> for some boards (the Netduino Plus 2 for example)
>
> Signed-off-by: Alistair Francis <alistair23@gmail.com>
This looks a bit odd -- I'm pretty sure the hardware doesn't
get only the reset address from an IMPDEF location.
Are you sure this board doesn't actually have an IMPDEF
reset value for the vector table offset register VTOR?
Which CPU core is this, anyway? Googling suggests
it's a Cortex-M4, and the M4 TRM suggests that VTOR
always resets to 0.
thanks
-- PMM
next prev parent reply other threads:[~2014-08-21 8:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 1:36 [Qemu-devel] [PATCH v1 1/1] target_arm: Make the reset rom_ptr a property Alistair Francis
2014-08-21 1:40 ` Alistair Francis
2014-08-21 3:37 ` Peter Crosthwaite
2014-08-21 4:13 ` Alistair Francis
2014-08-21 10:55 ` Andreas Färber
2014-08-21 12:33 ` Peter Maydell
2014-08-21 12:37 ` Peter Crosthwaite
2014-08-21 12:40 ` Peter Maydell
2014-08-21 12:43 ` Peter Crosthwaite
2014-08-21 13:15 ` Christopher Covington
2014-08-21 13:18 ` Peter Maydell
2014-08-21 8:01 ` Peter Maydell [this message]
2014-08-21 8:35 ` Alistair Francis
2014-08-21 9:14 ` Peter Maydell
2014-08-21 12:09 ` Alistair Francis
2014-08-21 12:22 ` Peter Crosthwaite
2014-08-21 12:26 ` Alistair Francis
2014-08-21 12:24 ` Peter Maydell
2014-08-21 12:35 ` Peter Crosthwaite
2014-08-21 12:37 ` Alistair Francis
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='CAFEAcA-ymT8Kb_Ewf=6beJCWTdYERzJTk5svWpZ-PAE8bm3=Xw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair23@gmail.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).