From: Rob Herring <rob.herring@calxeda.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@suse.de>,
"Mark Langsdorf" <mark.langsdorf@calxeda.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] ahci: add support for non-PCI based controllers
Date: Thu, 05 Jan 2012 09:46:36 -0600 [thread overview]
Message-ID: <4F05C5DC.9050904@calxeda.com> (raw)
In-Reply-To: <CAFEAcA-Vshtd7sWBUhukP5SSDVPuAZkuvGezawbTg87VJefv5g@mail.gmail.com>
On 01/05/2012 09:32 AM, Peter Maydell wrote:
> On 5 January 2012 15:11, Rob Herring <rob.herring@calxeda.com> wrote:
>> Mark, there is not a qemu code dependency on Trustzone support, so we
>> don't need to wait for that to add highbank support.
>
> That's good, because Trustzone support is not going to land imminently
> I suspect, and it would be better not to have it as a dependency.
> (I'll consider minimal workarounds for lack-of-trustzone if we have to
> to get things booting.)
We don't need the full Trustzone secure and non-secure states to work.
We just need writes to the various secure config registers to be ignored
and not error out.
Rob
next prev parent reply other threads:[~2012-01-05 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 13:52 [Qemu-devel] [PATCH v3 1/2] ahci: convert ahci_reset to use AHCIState Mark Langsdorf
2012-01-05 13:52 ` [Qemu-devel] [PATCH v3 2/2] ahci: add support for non-PCI based controllers Mark Langsdorf
2012-01-05 14:16 ` Andreas Färber
2012-01-05 14:26 ` Alexander Graf
2012-01-05 14:32 ` Andreas Färber
2012-01-05 14:35 ` Mark Langsdorf
2012-01-05 15:11 ` Rob Herring
2012-01-05 15:13 ` Alexander Graf
2012-01-05 15:32 ` Peter Maydell
2012-01-05 15:40 ` Mark Langsdorf
2012-01-05 15:46 ` Rob Herring [this message]
2012-01-05 14:11 ` [Qemu-devel] [PATCH v3 1/2] ahci: convert ahci_reset to use AHCIState Andreas Färber
2012-01-05 14:17 ` Alexander Graf
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=4F05C5DC.9050904@calxeda.com \
--to=rob.herring@calxeda.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=kwolf@redhat.com \
--cc=mark.langsdorf@calxeda.com \
--cc=peter.maydell@linaro.org \
--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).