question on possible functionality...
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?
Thanks.
Signature · 8 lines
ciao, al ----------------------------------- Al Stone Software Engineer Red Hat, Inc. [email protected] -----------------------------------
Quoted 7 lines · Al Stone
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
Quoted 8 lines
to build a 5.1-compliant FADT, as compared to:
$ iasl apic.aslwhich 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
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
Quoted 29 lines
-----Original Message-----
From: Rafael J. Wysocki [mailto:[email protected]]
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...Quoted 5 lines · Al Stone
Howdy.
I have run into a couple of cases now where is would like to do something like the following:
Quoted 7 lines
$ iasl --acpi-version=5.1 apic.aslto build a 5.1-compliant FADT, as compared to:
$ iasl apic.aslwhich always expects a very recent definition of the tables being
defined.
Quoted 3 lines
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
Quoted 5 lines · Robert
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.
Quoted 30 lines
Quoted 29 lines
-----Original Message-----
From: Rafael J. Wysocki [mailto:[email protected]]
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...Quoted 5 lines · Al Stone
Howdy.
I have run into a couple of cases now where is would like to do something like the following:
Quoted 7 lines
$ iasl --acpi-version=5.1 apic.aslto build a 5.1-compliant FADT, as compared to:
$ iasl apic.aslwhich always expects a very recent definition of the tables being
defined.
Quoted 3 lines
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
Signature · 8 lines
ciao, al ----------------------------------- Al Stone Software Engineer Red Hat, Inc. [email protected] -----------------------------------