From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] registering QEMU ACPI ID
Date: Tue, 23 Jun 2015 16:22:33 +0200 [thread overview]
Message-ID: <20150623162145-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CAFEAcA82Ahet=eKLR3AhOuTYez4ZO+Fe_rhGrYCxvWWc4HCWcw@mail.gmail.com>
On Tue, Jun 23, 2015 at 03:18:38PM +0100, Peter Maydell wrote:
> On 23 June 2015 at 15:07, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Hello!
> > QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
> > it generates. This is a bit of a spec violation:
> > all IDs must be registered with the ASWG.
> >
> > From the ASWG point of view, things are easier if a legal entity owns a
> > vendor ID, so Red Hat could ask to own the ID on behalf of the
> > community.
> >
> > I intend to ask the ASWG to register this ID for Red Hat 2 weeks from
> > now, July 7th.
>
> RedHat already officially "own" our PCI ID space (see
> docs/specs/pci-ids.txt) so having them also deal with ACPI IDs
> seems a reasonable plan to me.
>
> Is the plan that we register "QEMU" as the vendor ID, or are the
> ASWG likely to require a different ID string?
>
> thanks
> -- PMM
Yes, I'd like to register "QEMU" since we are already using it.
A bit less work for everyone involved. It seems free at this point.
--
MST
next prev parent reply other threads:[~2015-06-23 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:29 [Qemu-devel] register QEMU ACPI ID Michael S. Tsirkin
[not found] ` <DFF7383D242A84439AD17BCBA41787FE9206C62A@ORSMSX109.amr.corp.intel.com>
[not found] ` <20150510115413-mutt-send-email-mst@redhat.com>
2015-05-10 18:52 ` [Qemu-devel] [aswg-chair] " Doran, Mark
2015-07-15 20:02 ` Michael S. Tsirkin
2015-06-23 14:07 ` [Qemu-devel] registering " Michael S. Tsirkin
2015-06-23 14:18 ` Peter Maydell
2015-06-23 14:22 ` Michael S. Tsirkin [this message]
2015-07-15 19:56 ` Michael S. Tsirkin
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=20150623162145-mutt-send-email-mst@redhat.com \
--to=mst@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).