diff mbox

[v1,1/1] zynqmp: Add the ZCU102 board

Message ID cc82eec026b2febfca252d73362bb7084616c1ad.1464213234.git.alistair.francis@xilinx.com (mailing list archive)
State New, archived
Headers show

Commit Message

Alistair Francis May 25, 2016, 9:57 p.m. UTC
Most Zynq UltraScale+ users will be targetting and using the ZCU102
board instead of the development focused EP108. To make our QEMU machine
names clearer add a ZCU102 machine model.

Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
---
There are differences between the two boards, but at the moment we don't
support those differences in QEMU so it doesn't make sense to use a new
init function. So for the time being this machine is the same as the
EP108 machine.

 hw/arm/xlnx-ep108.c | 8 ++++++++
 1 file changed, 8 insertions(+)

Comments

Peter Maydell June 6, 2016, 2:35 p.m. UTC | #1
On 25 May 2016 at 22:57, Alistair Francis <alistair.francis@xilinx.com> wrote:
> Most Zynq UltraScale+ users will be targetting and using the ZCU102
> board instead of the development focused EP108. To make our QEMU machine
> names clearer add a ZCU102 machine model.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---

Applied, thanks.

-- PMM
diff mbox

Patch

diff --git a/hw/arm/xlnx-ep108.c b/hw/arm/xlnx-ep108.c
index 40f7cc1..34b4641 100644
--- a/hw/arm/xlnx-ep108.c
+++ b/hw/arm/xlnx-ep108.c
@@ -114,3 +114,11 @@  static void xlnx_ep108_machine_init(MachineClass *mc)
 }
 
 DEFINE_MACHINE("xlnx-ep108", xlnx_ep108_machine_init)
+
+static void xlnx_zcu102_machine_init(MachineClass *mc)
+{
+    mc->desc = "Xilinx ZynqMP ZCU102 board";
+    mc->init = xlnx_ep108_init;
+}
+
+DEFINE_MACHINE("xlnx-zcu102", xlnx_zcu102_machine_init)