From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: "Hong-Hua.Yin@freescale.com" <Hong-Hua.Yin@freescale.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Li Zhang <zhlcindy@linux.vnet.ibm.com>,
"agraf@suse.de" <agraf@suse.de>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] QEMU: PCI bus name on PowerPC platforms
Date: Wed, 05 Mar 2014 15:44:40 +0100 [thread overview]
Message-ID: <53173858.7020506@redhat.com> (raw)
In-Reply-To: <531736FD.907@suse.de>
Il 05/03/2014 15:38, Andreas Färber ha scritto:
>> >
>> > I believe so, yes. See
>> > https://github.com/afaerber/qemu-cpu/commit/ce1c9b4302a4458e73ae6a6a13f4e4ee121f79ea
> Err, on second thoughts that depends on the device not having an id=. If
> it does, then it's foo.0, not pci.0.
Yeah, but builtin devices created by the boards likely will not have
ids. This is what needs testing.
Paolo
next prev parent reply other threads:[~2014-03-05 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 10:42 [Qemu-devel] QEMU: PCI bus name on PowerPC platforms Hong-Hua.Yin
2014-03-05 11:43 ` Alexey Kardashevskiy
2014-03-05 13:35 ` Paolo Bonzini
2014-03-05 13:40 ` Daniel P. Berrange
2014-03-05 14:12 ` Paolo Bonzini
2014-03-05 14:21 ` Daniel P. Berrange
2014-03-05 14:33 ` Paolo Bonzini
2014-03-05 14:40 ` Daniel P. Berrange
2014-04-10 9:24 ` Daniel P. Berrange
2014-04-11 11:40 ` Alexey Kardashevskiy
2014-04-11 12:27 ` Eric Blake
2014-04-11 12:29 ` Alexander Graf
2014-03-05 14:35 ` Andreas Färber
2014-03-05 14:38 ` Andreas Färber
2014-03-05 14:44 ` Paolo Bonzini [this message]
2014-03-05 15:15 ` Alexey Kardashevskiy
2014-03-06 2:25 ` Hong-Hua.Yin
2014-03-06 7:04 ` Hong-Hua.Yin
2014-03-06 7:07 ` Alexey Kardashevskiy
2014-03-06 7:21 ` Hong-Hua.Yin
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=53173858.7020506@redhat.com \
--to=pbonzini@redhat.com \
--cc=Hong-Hua.Yin@freescale.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=zhlcindy@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.