qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PULL 08/24] vt82c686: Clean up use of cannot_instantiate_with_device_add_yet
Date: Tue, 24 Dec 2013 17:57:01 +0100	[thread overview]
Message-ID: <1387904237-6941-9-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1387904237-6941-1-git-send-email-afaerber@suse.de>

From: Markus Armbruster <armbru@redhat.com>

A VT82C686B southbridge has multiple functions.  We model each
function as a separate qdev.  One of them need some special wiring set
up in mips_fulong2e_init() to work: the ISA bridge at 05.0.

The IDE controller at 05.1 (via-ide) has always had
cannot_instantiate_with_device_add_yet set, but there is no obvious
reason why device_add could not work for them.  Drop it.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
 hw/ide/via.c      | 1 -
 hw/isa/vt82c686.c | 6 +++++-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/hw/ide/via.c b/hw/ide/via.c
index b556c14..198123b 100644
--- a/hw/ide/via.c
+++ b/hw/ide/via.c
@@ -225,7 +225,6 @@ static void via_ide_class_init(ObjectClass *klass, void *data)
     k->revision = 0x06;
     k->class_id = PCI_CLASS_STORAGE_IDE;
     set_bit(DEVICE_CATEGORY_STORAGE, dc->categories);
-    dc->cannot_instantiate_with_device_add_yet = true; /* FIXME explain why */
 }
 
 static const TypeInfo via_ide_info = {
diff --git a/hw/isa/vt82c686.c b/hw/isa/vt82c686.c
index b06d15e..e639357 100644
--- a/hw/isa/vt82c686.c
+++ b/hw/isa/vt82c686.c
@@ -480,8 +480,12 @@ static void via_class_init(ObjectClass *klass, void *data)
     k->class_id = PCI_CLASS_BRIDGE_ISA;
     k->revision = 0x40;
     dc->desc = "ISA bridge";
-    dc->cannot_instantiate_with_device_add_yet = true; /* FIXME explain why */
     dc->vmsd = &vmstate_via;
+    /*
+     * Reason: part of VIA VT82C686 southbridge, needs to be wired up,
+     * e.g. by mips_fulong2e_init()
+     */
+    dc->cannot_instantiate_with_device_add_yet = true;
 }
 
 static const TypeInfo via_info = {
-- 
1.8.4

  parent reply	other threads:[~2013-12-24 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 16:56 [Qemu-devel] [PULL 00/24] QOM devices patch queue 2013-12-24 Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 01/24] qdev: Replace no_user by cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 02/24] sysbus: Set cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 03/24] cpu: Document why cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 04/24] apic: " Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 05/24] pci-host: Consistently set cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:56 ` [Qemu-devel] [PULL 06/24] ich9: Document why cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 07/24] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet Andreas Färber
2013-12-24 16:57 ` Andreas Färber [this message]
2013-12-24 16:57 ` [Qemu-devel] [PULL 09/24] isa: " Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 10/24] qdev: Do not let the user try to device_add when it cannot work Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 11/24] qdev-monitor: Avoid device_add crashing on non-device driver name Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 12/24] hw: cannot_instantiate_with_device_add_yet due to pointer props Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 13/24] qdev: Document that pointer properties kill device_add Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 14/24] qom: Split out object and class caches Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 15/24] qom: Do not register interface "types" in the type table and fix names Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 16/24] tests: Test QOM interface casting Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 17/24] qom: Detect bad reentrance during object_class_foreach() Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 18/24] qdev: Drop misleading qbus_free() function Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 19/24] apic: Cleanup for QOM'ification Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 20/24] apic: QOM'ify APIC Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 21/24] icc_bus: QOM'ify ICC Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 22/24] ioapic: Cleanup for QOM'ification Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 23/24] ioapic: QOM'ify ioapic Andreas Färber
2013-12-24 16:57 ` [Qemu-devel] [PULL 24/24] qdev-monitor: Improve error message for -device nonexistant Andreas Färber
2013-12-24 17:01 ` [Qemu-devel] [PULL 00/24] QOM devices patch queue 2013-12-24 Andreas Färber

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=1387904237-6941-9-git-send-email-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --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).