From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>
Subject: [Qemu-devel] [PULL for-2.0 11/13] spapr_vio: Fix firmware names
Date: Thu, 20 Mar 2014 02:48:53 +0100 [thread overview]
Message-ID: <1395280135-10644-12-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1395280135-10644-1-git-send-email-afaerber@suse.de>
From: Alexey Kardashevskiy <aik@ozlabs.ru>
This changes VIO bridge fw name from spapr-vio-bridge to vdevice and
vscsi/veth node names from QEMU object names to VIO specific device tree
names.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
hw/ppc/spapr_vio.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/ppc/spapr_vio.c b/hw/ppc/spapr_vio.c
index 4e33f46..2ae06a3 100644
--- a/hw/ppc/spapr_vio.c
+++ b/hw/ppc/spapr_vio.c
@@ -68,6 +68,7 @@ static void spapr_vio_bus_class_init(ObjectClass *klass, void *data)
BusClass *k = BUS_CLASS(klass);
k->get_dev_path = spapr_vio_get_dev_name;
+ k->get_fw_dev_path = spapr_vio_get_dev_name;
}
static const TypeInfo spapr_vio_bus_info = {
@@ -529,7 +530,9 @@ static int spapr_vio_bridge_init(SysBusDevice *dev)
static void spapr_vio_bridge_class_init(ObjectClass *klass, void *data)
{
SysBusDeviceClass *k = SYS_BUS_DEVICE_CLASS(klass);
+ DeviceClass *dc = DEVICE_CLASS(klass);
+ dc->fw_name = "vdevice";
k->init = spapr_vio_bridge_init;
}
--
1.8.4.5
next prev parent reply other threads:[~2014-03-20 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 1:48 [Qemu-devel] [PULL for-2.0-rc1 00/13] PowerPC patch queue 2014-03-20 #2 Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 01/13] target-ppc: Add missing 'static' and 'const' attributes Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 02/13] spapr_hcall: Fix h_enter to loop correctly Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 03/13] target-ppc: Reset SPRs on CPU reset Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 04/13] target-ppc: Fix overallocation of opcode tables Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 05/13] target-ppc: Force CPU threads count to be a power of 2 Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 06/13] target-ppc: Introduce powerisa-207-server flag Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 07/13] spapr_hcall: Fix little-endian resource handling in H_SET_MODE Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 08/13] vl.c: Extend get_boot_devices_list() to ignore suffixes Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 09/13] qdev: Introduce FWPathProvider interface Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 10/13] spapr_llan: Add to boot device list Andreas Färber
2014-03-20 1:48 ` Andreas Färber [this message]
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 12/13] spapr: QOM'ify pseries machine Andreas Färber
2014-03-20 1:48 ` [Qemu-devel] [PULL for-2.0 13/13] spapr: Implement interface to fix device pathname Andreas Färber
2014-03-20 12:17 ` [Qemu-devel] [PULL for-2.0-rc1 00/13] PowerPC patch queue 2014-03-20 #2 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=1395280135-10644-12-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).