ACPI Component Architecture Downloads (Previous Releases 2022)

774876
3/29/2023

Introduction

Allow disabling of -Werror. For distro maintainers having `-Werror` can delay update of GCC. Since every GCC release might add new warnings that were not yet captured, it might break the build of packages.

Available Downloads

  • Unix*
  • Size: 1.8 MB
  • SHA256: 33A2E394ACA0CA57D4018AFE3DA340DFAD5EB45B1B9300E81DD595FDA07CF1C5
  • Unix*
  • Size: 1.6 MB
  • SHA256: 1253B8B3A4F18A206852480D8F34AA1A1419E2C03211DDEFF25598F6DB39A234
  • Unix*
  • Size: 2.1 MB
  • SHA256: CE010D310CC58E970EA99B7894FC32D004475B5A95196E609E8706783C05D278
  • Microsoft Windows*
  • Size: 1.1 MB
  • SHA256: 1822C081020CCB78A8E5763014DC3F053C3C9359F23181A4347437FB22191A42
  • Microsoft Windows*
  • Size: 3 MB
  • SHA256: E0E2ACDFFAD92ECA67B3432007829E49C67A873F9A649DEED1F7611B579C95FE
  • Microsoft Windows*
  • Size: 3.6 MB
  • SHA256: 298E8487F536D3888B8701422708DDE4000FD37E9FA21B234E5669F66B71EF5A

Detailed Description

20 October 2022. Summary of changes for version 20221020:


This release is available at https://acpica.org/downloads

0) Global changes:

Allow disabling of -Werror. For distro maintainers, having `-Werror` can delay the update of GCC. Since every GCC release might add new warnings that were not yet captured, it might break the build of packages. With this change, distros can now build with `NOWERROR=TRUE` instead of patching either the errors or the makefiles. The default behavior keeps on using `-Werror`.

1) ACPICA kernel-resident subsystem:

Added support for FFH Operation Region special context data. FFH(Fixed Function Hardware) Opregion is approved to be added in ACPI 6.5 via code code-first approach[1]. It requires special context data similar to GPIO and Generic Serial Bus, as it needs to know platform-specific offset and length.

Reverted this commit "executer/exsystem: Warn about sleeps greater than 10 ms." Due to user complaints about valid sleeps greater than 10ms observed on some existing machines, generating many warnings.

Do not touch VGA memory when EBDA < 1KiB. The ACPICA code assumes the EBDA region must be at least 1 KiB in size. Because this is not guaranteed, it might happen that while scanning the memory for the RSDP pointer, the kernel touches memory above 640KiB. This is unwanted as the VGA memory range may not be decoded or even present when running under virtualization.

Check that the EBDA pointer is in valid memory. If the memory at 0x40e is uninitialized, the retrieved physical memory address of EBDA may be beyond the low memory (i.e., above 640K). If so, the kernel may unintentionally access the VGA memory, which might not be decoded or even present in the case of virtualization.

2) iASL Compiler/Disassembler and ACPICA tools:

Completed the existing partial support for the CDAT "table". Although this isn't technically an ACPI table (It doesn't go into the XSDT), it is possible to support this table in the Data Table compiler. Created one new file, "utilities/utcksum.c", used to centralize checksum generation/validation into one location. Includes changes to makefiles and MSVC project files.

Updated support for the IORT table - update to version E.e

Added CXL 3.0 structures (CXIMS & RDPAS) to the CEDT table

iASL: Added CCEL table to both compiler/disassembler.

iASL: NHLT table: Fixed compilation of optional undocumented fields

iASL: Fix iASL compile error due to ACPI_TDEL_OFFSET. Commit # 10e4763 ("iASL: Add CCEL table to both compiler/disassembler") introduced the iASL build issue. The issue is due to using ACPI_TDEL_OFFSET for the CCEL table member reference. To fix it, change ACPI_TDEL_OFFSET to ACPI_CCEL_OFFSET.

Date: 

20 October, 2022

Disclaimers1

Product and Performance Information

1

Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.