From 33cd52b5d7b9adfd009e95f07e6c64dd88ae2a31 Mon Sep 17 00:00:00 2001 From: Alexander Graf Date: Tue, 1 Jul 2014 16:14:41 +0200 Subject: sysbus: Make devices spawnable via -device Now that we can properly map sysbus devices that haven't been connected to something forcefully by C code, we can allow the -device command line option to spawn them. For machines that don't implement dynamic sysbus assignment in their board files we add a new bool "has_dynamic_sysbus" to the machine class. When that property is false (default), we bail out when we see dynamically spawned sysbus devices, like we did before. Signed-off-by: Alexander Graf --- hw/core/sysbus.c | 7 ------- 1 file changed, 7 deletions(-) (limited to 'hw/core/sysbus.c') diff --git a/hw/core/sysbus.c b/hw/core/sysbus.c index 19437e6..7bfe381 100644 --- a/hw/core/sysbus.c +++ b/hw/core/sysbus.c @@ -283,13 +283,6 @@ static void sysbus_device_class_init(ObjectClass *klass, void *data) DeviceClass *k = DEVICE_CLASS(klass); k->init = sysbus_device_init; k->bus_type = TYPE_SYSTEM_BUS; - /* - * device_add plugs devices into suitable bus. For "real" buses, - * that actually connects the device. For sysbus, the connections - * need to be made separately, and device_add can't do that. The - * device would be left unconnected, and could not possibly work. - */ - k->cannot_instantiate_with_device_add_yet = true; } static const TypeInfo sysbus_device_type_info = { -- cgit v1.1