From: Al Stone <ahs3@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
David Box <david.e.box@linux.intel.com>,
"Zheng, Lv" <lv.zheng@intel.com>
Subject: Re: question on possible functionality...
Date: Wed, 16 Dec 2015 13:47:44 -0700 [thread overview]
Message-ID: <5671CDF0.7070100@redhat.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37DA71480@ORSMSX112.amr.corp.intel.com>
On 12/16/2015 08:34 AM, Moore, Robert wrote:
> Yes, this is supported. Change the FADT version number to 5, and remove the version 6 field (Hypervisor Identity) from the source.
>
> [0004] Signature : "FACP" [Fixed ACPI Description Table (FADT)]
> [0004] Table Length : 00000114
> [0001] Revision : 05
Ooops. My bad. I thought I had sent this to the ACPICA devel
list. Sorry about the noise...
Thanks, Bob. I hadn't thought about doing it that way, but it's
pretty obvious now that you mention it. I guess I was thinking
about this from the other way around -- I would tell iasl what
spec release, and it would tell me that Revision X was required
for that table for that version of the spec, and then tell me
if I missed (or added) fields inappropriate to that version.
>> -----Original Message-----
>> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
>> Sent: Tuesday, December 15, 2015 7:19 PM
>> To: Al Stone
>> Cc: ACPI Devel Mailing List; David Box; Moore, Robert; Zheng, Lv
>> Subject: Re: question on possible functionality...
>>
>> On Tuesday, December 15, 2015 05:20:22 PM Al Stone wrote:
>>> Howdy.
>>>
>>> I have run into a couple of cases now where is would like to do
>>> something like the following:
>>>
>>> $ iasl --acpi-version=5.1 apic.asl
>>>
>>> to build a 5.1-compliant FADT, as compared to:
>>>
>>> $ iasl apic.asl
>>>
>>> which always expects a very recent definition of the tables being
>> defined.
>>>
>>> Is anyone working on such a thing? Or has it been contemplated in the
>>> past and discarded for some reason?
>>
>> CCing the ACPICA maintainers.
>>
>> Thanks,
>> Rafael
>
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
prev parent reply other threads:[~2015-12-16 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 0:20 question on possible functionality Al Stone
2015-12-16 3:18 ` Rafael J. Wysocki
2015-12-16 15:34 ` Moore, Robert
2015-12-16 20:47 ` Al Stone [this message]
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=5671CDF0.7070100@redhat.com \
--to=ahs3@redhat.com \
--cc=david.e.box@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.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).