qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Phil Dennis-Jordan <phil@philjordan.eu>,
	Igor Mammedov <imammedo@redhat.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] acpi: add reset register to fadt
Date: Tue, 31 Jan 2017 20:08:25 +0100	[thread overview]
Message-ID: <b2c2b185-8443-2d0e-dbd4-f6759184d69c@redhat.com> (raw)
In-Reply-To: <20170131201333-mutt-send-email-mst@kernel.org>

On 01/31/17 19:17, Michael S. Tsirkin wrote:
> On Tue, Jan 31, 2017 at 05:28:57PM +0100, Laszlo Ersek wrote:
>> The ACPI 6.1 spec says,
>>
>> - DSDT: [...] If the X_DSDT field contains a non-zero value then this
>>   field must be zero.
>> - X_DSDT: [...] If the DSDT field contains a non-zero value then this
>>   field must be zero.
> 
> But that's only 6.1. 6.0 and earlier did not say this.
> The errata they wanted to address was:
> 1393 In FADT: if X_DSDT field is non-zero, DSDT
> field should be ignored or deprecated
> 
> I would class this as a spec bug.
> 

Process-wise, that's not a bad idea; it could be the only way (or the
best way) to argue for a corresponding change in edk2's
EFI_ACPI_TABLE_PROTOCOL implementation
(MdeModulePkg/Universal/Acpi/AcpiTableDxe).

Do you want to raise this on the ASWG list? I vaguely recall that you
subscribed; if not, I think you should be able to, as a Red Hatter
<http://members.uefi.org/kmembership_info/person_signup/>.

(I'd like to avoid being the middle man.)

Hm... It seems that the "Adopter Membership" is free, which could be
appropriate for individual observers:

http://uefi.org/join
http://members.uefi.org/home/

(Should Phil consider it.)

Thanks
Laszlo

  reply	other threads:[~2017-01-31 19:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 11:45 [Qemu-devel] [PATCH RFC] acpi: add reset register to fadt Phil Dennis-Jordan
2017-01-18 16:30 ` Michael S. Tsirkin
2017-01-18 17:19   ` Igor Mammedov
2017-01-31 14:31     ` Phil Dennis-Jordan
2017-01-31 14:58       ` Michael S. Tsirkin
2017-01-31 15:41         ` Igor Mammedov
2017-01-31 16:04           ` Phil Dennis-Jordan
2017-01-31 16:17             ` Igor Mammedov
2017-02-02 16:12             ` Michael S. Tsirkin
2017-01-31 16:28         ` Laszlo Ersek
2017-01-31 18:17           ` Michael S. Tsirkin
2017-01-31 19:08             ` Laszlo Ersek [this message]
2017-02-06 16:44               ` Phil Dennis-Jordan
2017-02-07  0:09                 ` Laszlo Ersek
2017-02-01 11:37             ` Igor Mammedov
2017-02-01 12:52               ` Laszlo Ersek
2017-02-01 13:03                 ` Laszlo Ersek
2017-02-01 15:16                   ` Igor Mammedov
2017-02-01 16:03                     ` Laszlo Ersek
2017-02-01 16:17                       ` Michael S. Tsirkin
2017-02-01 16:27                         ` Laszlo Ersek
2017-02-01 14:49               ` Michael S. Tsirkin
2017-02-06 16:30           ` Phil Dennis-Jordan
2017-02-07 19:54             ` Laszlo Ersek
2017-02-07 21:02               ` Phil Dennis-Jordan
2017-02-08  0:52                 ` Laszlo Ersek
2017-01-19 18:09   ` Phil Dennis-Jordan
2017-01-23 11:12     ` Igor Mammedov
2017-01-26 13:43       ` Phil Dennis-Jordan
2017-01-27 13:57         ` Igor Mammedov
2017-01-27 16:05           ` Paolo Bonzini

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=b2c2b185-8443-2d0e-dbd4-f6759184d69c@redhat.com \
    --to=lersek@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=phil@philjordan.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).