From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Shannon Zhao <shannon.zhao@linaro.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
G Gregory <graeme.gregory@linaro.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] virtio_mmio: add ACPI probing
Date: Wed, 29 Jul 2015 21:03:14 +0300 [thread overview]
Message-ID: <20150729210114-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CAFEAcA-HZVJCa44g0-emN06-_a1DgsjtT4cC2_BBQgEyz-=akw@mail.gmail.com>
On Wed, Jul 29, 2015 at 06:52:29PM +0100, Peter Maydell wrote:
> On 28 July 2015 at 11:33, G Gregory <graeme.gregory@linaro.org> wrote:
> > We assigned LNRO in ASWG to avoid collisions with our prototypes/real
> > platforms so it makes sense to me to switch to QEMUXXXX.
>
> So just to check, if we switch virtio-mmio from an LNRO0005 ID
> to a QEMUxxxx ID we aren't going to break any existing widely
> shipped or deployed code, right?
>
> If we can change the ID without breaking anything significant
> then I think the QEMU ID makes more sense; but it doesn't
> really gain us much beyond tidiness.
>
> PS: https://www.kernel.org/doc/Documentation/arm64/arm-acpi.txt
> uses virtio-mmio and LNRO0005 as its code example, so if
> we change this then it might be nice to update the docs
> as a followup.
>
> thanks
> -- PMM
So this is the proposed patch. I agree it's merely about tidyness.
Pls ack or nack - we need to decide before 2.4 is out.
-->
arm: change vendor ID for virtio-mmio
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index f365140..d10bd69 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("QEMU0005")));
aml_append(dev, aml_name_decl("_UID", aml_int(i)));
Aml *crs = aml_resource_template();
next prev parent reply other threads:[~2015-07-29 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438076642-12080-1-git-send-email-graeme.gregory@linaro.org>
2015-07-28 10:08 ` [PATCH] virtio_mmio: add ACPI probing Michael S. Tsirkin
2015-07-28 10:12 ` Peter Maydell
[not found] ` <CAFEAcA9H6_oEFKFFNhcGW-8Yy8ng9iNnPbweTvMC46fwLmwA0w@mail.gmail.com>
2015-07-28 10:27 ` Michael S. Tsirkin
2015-07-28 10:33 ` G Gregory
2015-07-28 20:12 ` Peter Maydell
2015-07-28 20:28 ` G Gregory
[not found] ` <CAGCh1+kRyGNOH9mxRuEBLN+Ap4eJGS0wCC3YroBDuGnh8FsNKw@mail.gmail.com>
2015-07-28 21:10 ` Peter Maydell
2015-07-29 2:01 ` Shannon Zhao
[not found] ` <55B833FF.20107@linaro.org>
2015-07-29 10:01 ` Michael S. Tsirkin
[not found] ` <CAGCh1+=4am4xHXark=EMLT-BD-92oWFvvWE4N7TEf=YwMAUCzQ@mail.gmail.com>
2015-07-29 17:52 ` Peter Maydell
2015-07-29 18:03 ` Michael S. Tsirkin [this message]
2015-07-29 18:17 ` Michael S. Tsirkin
[not found] ` <20150729211637-mutt-send-email-mst@redhat.com>
2015-08-27 14:55 ` Graeme Gregory
2015-07-28 9:44 Graeme Gregory
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=20150729210114-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=graeme.gregory@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=shannon.zhao@linaro.org \
--cc=virtualization@lists.linux-foundation.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