qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org
Cc: alistair.francis@xilinx.com, alistair23@gmail.com,
	edgar.iglesias@xilinx.com, edgar.iglesias@gmail.com
Subject: [Qemu-devel] [PATCH v1 0/5] Expose the secure property to the machine
Date: Thu, 17 Aug 2017 11:51:59 -0700	[thread overview]
Message-ID: <cover.1502993370.git.alistair.francis@xilinx.com> (raw)

The EL2 and EL3 work is working well now and interanlly we now have
tests that expect to start in EL3 and transition through EL2 to EL1. To
make this easy to run let's expose the secure property to the machine
and then use that to enable EL2.

This series also does some machine/name tidying up and makes the first
move to deprecating the EP108 machine, which was just an early access
development board.

Alistair Francis (5):
  xlnx-ep108: Rename to ZCU102
  xlnx-zcu102: Manually create the machines
  xlnx-zcu102: Add a machine level secure property
  xlnx-zynqmp: Allow the secure prop to enable EL2
  xlnx-zcu102: Mark the EP108 machine as deprecated

 hw/arm/Makefile.objs                   |   2 +-
 hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} | 131 ++++++++++++++++++++++++++++-----
 hw/arm/xlnx-zynqmp.c                   |   2 +-
 3 files changed, 114 insertions(+), 21 deletions(-)
 rename hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} (51%)

-- 
2.11.0

             reply	other threads:[~2017-08-17 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 18:51 Alistair Francis [this message]
2017-08-17 18:52 ` [Qemu-devel] [PATCH v1 2/5] xlnx-zcu102: Manually create the machines Alistair Francis
2017-08-22 17:26   ` Edgar E. Iglesias
2017-08-17 18:52 ` [Qemu-devel] [PATCH v1 4/5] xlnx-zynqmp: Allow the secure prop to enable EL2 Alistair Francis
2017-08-17 18:52 ` [Qemu-devel] [PATCH v1 5/5] xlnx-zcu102: Mark the EP108 machine as deprecated Alistair Francis
2017-08-22 17:24 ` [Qemu-devel] [PATCH v1 0/5] Expose the secure property to the machine Edgar E. Iglesias
2017-08-22 17:57   ` Alistair Francis
2017-08-22 18:05     ` 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=cover.1502993370.git.alistair.francis@xilinx.com \
    --to=alistair.francis@xilinx.com \
    --cc=alistair23@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.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).