SetupDesignGuide.pdf - Firmware Encoding Index

Setup Design Guide
DRAFT
#strdef
SPA STR_SUBTITLE_TEXT “Mi texto del subtítulo”
4.2.6 formset / endformset
This command is used to define the beginning and end of a set of forms.
If any of the keywords used in the VFR file have a DYNAMIC or an INTERACTIVE flag turned on,
then calls to the HII must pass in the pointer to the driver’s callback interface and the
drivercallback should be set to TRUE. The drivercallback field will be filled into the
byte-stream by the compiler, and is an optional field for the user to input. When this data is exported to
the HII database, a FALSE will be replaced with a zero, and a TRUE will be replaced with the value of
the driver’s callback interface pointer.
Example: formset guid = FORMSET_GUID,
title = STR_FORMSET_TITLE,
[drivercallback = TRUE,]
version = 2,
endformset;
4.2.7 nvstorage
This command is used to define the location of the non-volatile storage used for the choices made by
the user. If the NV storage will not be located in the system NV (e.g. Add-in card NV storage) then
access to the add-in card’s NV must be exposed via the EFI_FORM_CALLBACK_PROTOCOL
protocol. For more information on the EFI_FORM_CALLBACK_PROTOCOL protocol see section
7.3.The handle that contains the interface will be communicated via the nvstorage setting. The first
example shows how one might define an NV storage descriptor for the system variables.
Example: nvstorage handle = NULL,
devicepath = NULL,
key = NULL;
In the second example, the handle and devicepath are defined to be non-NULL to signify that
when this data is exported, there will be a callback done to fill in the two variables. The key value will
be retrieved from a VFR_NV_KEY() macro. It is intended to be a uniquely identified value so that the
callback to the driver will correctly identify the purpose of the callback and hand back the correct
information.
Example: nvstorage handle = 1,
devicepath = 1,
For more information about NV steering see section 6.2.
4.2.8 form / endform
key = RaidControllerMapDefine;
This command is used to define the beginning and end of a page of user interface data.
Example: form formid = PAGE_ONE,
title = STR_FORM_TITLE,
endform;
30