From: Shannon Zhao <shannon.zhao@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Graeme Gregory" <graeme.gregory@linaro.org>,
"lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Shannon Zhao" <zhaoshenglong@huawei.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio
Date: Thu, 30 Jul 2015 09:23:20 +0800 [thread overview]
Message-ID: <55B97C88.6010004@linaro.org> (raw)
In-Reply-To: <1438196676-30255-1-git-send-email-mst@redhat.com>
On 2015/7/30 3:16, Michael S. Tsirkin wrote:
> ACPI spec 5.0 allows the use of PCI vendor IDs.
>
But virtio-mmio is not a PCI device, it's a platform device.
Why do we drop the previous way using "QEMUXXXX"? Something I missed?
> Since we have one for virtio, it seems neater to use that
> rather than LNRO. For the device ID, use 103F which is a legacy ID that
> isn't used in virtio PCI spec - seems to make sense since virtio-mmio is
> a legacy device but we don't know the correct device type.
>
> Guests should probably match everything in the range 1000-103F
> (just like legacy pci drivers do) which will allow us to pass in the
> actual ID in the future if we want to.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> hw/arm/virt-acpi-build.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> index f365140..dea61ba 100644
> --- a/hw/arm/virt-acpi-build.c
> +++ b/hw/arm/virt-acpi-build.c
> @@ -145,7 +145,7 @@ static void acpi_dsdt_add_virtio(Aml *scope,
>
> for (i = 0; i < num; i++) {
> Aml *dev = aml_device("VR%02u", i);
> - aml_append(dev, aml_name_decl("_HID", aml_string("LNRO0005")));
> + aml_append(dev, aml_name_decl("_HID", aml_string("1AF4103F")));
> aml_append(dev, aml_name_decl("_UID", aml_int(i)));
>
> Aml *crs = aml_resource_template();
>
--
Shannon
next prev parent reply other threads:[~2015-07-30 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:16 [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Michael S. Tsirkin
2015-07-30 1:23 ` Shannon Zhao [this message]
2015-07-30 8:04 ` Michael S. Tsirkin
2015-07-30 9:21 ` Shannon Zhao
2015-07-30 15:02 ` Michael S. Tsirkin
2015-07-30 9:24 ` Peter Maydell
2015-07-30 9:37 ` G Gregory
2015-07-30 9:43 ` G Gregory
2015-07-30 15:05 ` Michael S. Tsirkin
2015-07-31 12:37 ` Peter Maydell
2015-08-03 12:09 ` Andrew Jones
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=55B97C88.6010004@linaro.org \
--to=shannon.zhao@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=graeme.gregory@linaro.org \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zhaoshenglong@huawei.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 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).