qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: armbru@redhat.com, qemu-devel@nongnu.org, marcel.a@redhat.com
Cc: borntraeger@de.ibm.com, aliguori@amazon.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v4 02/10] sysbus: Set cannot_instantiate_with_device_add_yet
Date: Sun, 15 Dec 2013 21:16:00 +0100	[thread overview]
Message-ID: <52AE0E00.7010606@suse.de> (raw)
In-Reply-To: <1385656023-11519-3-git-send-email-armbru@redhat.com>

Am 28.11.2013 17:26, schrieb armbru@redhat.com:
> diff --git a/hw/core/sysbus.c b/hw/core/sysbus.c
> index 146f50a..ed0477b 100644
> --- a/hw/core/sysbus.c
> +++ b/hw/core/sysbus.c
> @@ -257,6 +257,13 @@ 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 unconncected, and could not possibly work.

"unconnected" - fixed.

Andreas

> +     */
> +    k->cannot_instantiate_with_device_add_yet = true;
>  }
>  
>  static const TypeInfo sysbus_device_type_info = {

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-12-15 20:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 16:26 [Qemu-devel] [PATCH v4 00/10] Clean up and fix no_user armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 01/10] qdev: Replace no_user by cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 02/10] sysbus: Set cannot_instantiate_with_device_add_yet armbru
2013-12-15 20:16   ` Andreas Färber [this message]
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 03/10] cpu: Document why cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 04/10] apic: " armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 05/10] pci-host: Consistently set cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 06/10] ich9: Document why cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 07/10] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 08/10] vt82c686: " armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 09/10] isa: " armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 10/10] qdev: Do not let the user try to device_add when it cannot work armbru
2013-12-15 20:25   ` Andreas Färber
2013-12-16  7:28     ` Markus Armbruster
2013-12-15 20:37 ` [Qemu-devel] [PATCH v4 00/10] Clean up and fix no_user Andreas Färber
2013-12-16  8:21   ` Markus Armbruster
2013-12-16  8:21   ` Marcel Apfelbaum
2013-12-19 16:40     ` 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=52AE0E00.7010606@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=marcel.a@redhat.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).