From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alexander Graf <agraf@suse.de>,
Rob Herring <rob.herring@calxeda.com>,
qemu-devel@nongnu.org, Grant Likely <grant.likely@secretlab.ca>,
Paul Brook <paul@codesourcery.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Jeremy Kerr <jeremy.kerr@canonical.com>,
John Williams <john.williams@petalogix.com>
Subject: Re: [Qemu-devel] [PATCH v2] arm: add device tree support
Date: Wed, 1 Feb 2012 13:10:50 +0000 [thread overview]
Message-ID: <CAFEAcA89A1SBezb2DEbMWL5qD+Me3_uXufmneHyxwz4Kj8dBeA@mail.gmail.com> (raw)
In-Reply-To: <4F29384F.6070404@codemonkey.ws>
On 1 February 2012 13:04, Anthony Liguori <anthony@codemonkey.ws> wrote:
> How does it race? Devices normally never touch memory so a loader device
> will be the only thing mucking with memory.
The obvious one is "loader reset function wants to set starting PC to
entry point of kernel/etc" vs "CPU device reset wants to set starting
PC to hardware-mandated reset vector". We have this at the moment, of
course, and I think we implicitly rely on reset handlers being called
in order of registration...
(The other irritating case is where the CPU device reset wants
to read the starting PC out of memory, like the Cortex-M3, but
really that one is because we don't distinguish "going into reset"
from "coming out of reset".)
-- PMM
next prev parent reply other threads:[~2012-02-01 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 0:11 [Qemu-devel] [PATCH v2] arm: add device tree support Grant Likely
2012-02-01 1:10 ` Alexander Graf
2012-02-01 1:35 ` Paul Brook
2012-02-01 1:44 ` Alexander Graf
2012-02-01 2:37 ` Anthony Liguori
2012-02-01 2:40 ` John Williams
2012-02-01 13:04 ` Anthony Liguori
2012-02-01 13:10 ` Peter Maydell [this message]
2012-02-01 13:25 ` Anthony Liguori
2012-02-01 13:32 ` Alexander Graf
2012-02-01 13:44 ` Anthony Liguori
2012-02-01 13:49 ` Alexander Graf
2012-02-01 13:52 ` Anthony Liguori
2012-02-01 13:55 ` Alexander Graf
2012-02-01 15:13 ` Anthony Liguori
2012-02-01 17:38 ` Grant Likely
2012-02-01 20:59 ` Alexander Graf
2012-02-01 2:35 ` Anthony Liguori
2012-02-22 19:42 ` Peter Maydell
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=CAFEAcA89A1SBezb2DEbMWL5qD+Me3_uXufmneHyxwz4Kj8dBeA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=edgar.iglesias@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=jeremy.kerr@canonical.com \
--cc=john.williams@petalogix.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@calxeda.com \
/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).