769cbbf8af
On Alterlake and newer hardware the Platform Health Assessment Record data can be used by the IHV to debug why a specific capsule update failed. Any custom firmware loaded by the OEM can be identified and used to further debug the root cause. |
||
|---|---|---|
| .. | ||
| fu-acpi-phat-health-record.c | ||
| fu-acpi-phat-health-record.h | ||
| fu-acpi-phat-version-element.c | ||
| fu-acpi-phat-version-element.h | ||
| fu-acpi-phat-version-record.c | ||
| fu-acpi-phat-version-record.h | ||
| fu-acpi-phat.c | ||
| fu-acpi-phat.h | ||
| fu-plugin-acpi-phat.c | ||
| fu-self-test.c | ||
| meson.build | ||
| README.md | ||
Platform Health Assessment Table
Introduction
The PHAT is an ACPI table where a platform can expose health related telemetry that may be useful for software running within the constraints of an OS.
These elements are typically going to encompass things that are likely otherwise not enumerable during the OS runtime phase of operations, such as version of pre-OS components.
The daemon includes some of the PHAT data in the report data sent to the LVFS so that we can debug failures with the help of the IHV. This allows us to find the root cause of the problem, and so we know what other OEMs may be affected.
See https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/05_ACPI_Software_Programming_Model/ACPI_Software_Programming_Model.html#platform-health-assessment-table for more information.
External interface access
This plugin requires read access to /sys/firmware/acpi/tables.