Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 93 of 94
#### Description
RD2
The remote-control action is initiated immediately after the alert-sending device
sends the associated Byte Write SMBus message.
Required
RD3
The device supports its associated remote-control action as described in section
6.3.3.
Required
RD4 The device supports SMBus PEC protocols. Optional
C.6 System Firmware
The following table identifies the required and optional features for a managed client’s firmware
ASF implementation.
Table D-6 System Firmware Checklist for ASF Implementations
#### Description
SF1
System includes an SMBIOS implementation, compliant with v2.3 or later of
[SMBIOS].
Required
SF2 System includes an ACPI implementation, compliant with v1.0b or later of [ACPI] Required
SF3
The system’s ACPI implementation contains a single ASF device with PnP ID of
“ASF0001” and provides support for the GPWT and SPWT control methods.
Required
SF4
The system’s ACPI implementation includes the ASF_INFO information record in
its ASF! ACPI description table.
Required
SF5
If the system includes legacy alert-source devices, and those devices’ alerts are
to be handled by an ASF-aware alerting device, the ACPI ASF! description table
includes an ASF_ALRT information record.
Required
SF6
If the system includes devices that provide ASF RMCP system actions to an ASF-
aware alerting device, the system’s ACPI ASF! description table includes an
ASF_RCTL information record.
Required
SF7
If the system includes SMBus devices that are not discoverable, the system’s
ACPI ASF! description table includes an ASF_ADDR information record.
Required
SF8
If feature SF6 is implemented, at most one (1) of these information records is
present, and that structure can specify at most eight (8) device alerts.
Required
SF9
The system’s SMBIOS implementation contains a System Information structure
that provides the system’s UUID/GUID.
Required
SF11
If the system supports ASF RMCP capabilities, the system’s ACPI ASF!
description table contains an ASF_RMCP information record.
Required
SF20 The system firmware implements one or more System Firmware Error Events. Optional
SF21 The system firmware implements one or more System Firmware Progress Events. Optional
SF22
The system firmware issues the SMBus Stop Watchdog Timer message within
Minimum Watchdog Timer Reset Value seconds to disable the initial boot-failure
watchdog timer in the alert-sending device.
Required
SF23
If the system supports ASF RMCP capabilities, the system firmware issues the
SMBus Get Boot Options message as early as possible in its boot process to
retrieve the boot options sent with the last received RMCP command, and
subsequently issues the SMBus Clear Boot Options message to signify that the
firmware has retrieved the options for the current boot. Boot Options information
retrieved from the Get Boot Options message is reported by the firmware in the
system’s ACPI ASF_RMCP structure.
Required
SF24
The system firmware locates the alert-sending devices in the system by issuing
the SMBus Device Type Poll Message and examining the results of that
message.
Required
SF25
The system firmware issues the SMBus Set System State Message on system
sleeping-state transitions.
Optional