SetupDesignGuide.pdf - Firmware Encoding Index

Setup Design Guide
DRAFT
4.2.16 string
This command allows for the typing of a text string. This could take the form of a modem initialization
string, or any other piece of informational human-readable data.
Example: string
endstring;
varid = NvRamMap.MyStringData,
prompt = STR_MY_STRING_PROMPT,
help = STR_MY_STRING_HELP,
minsize = 6,
maxsize = 60,
A second example shows how one would create a string command which required interaction with a
hardware driver. Note from the first example that the key and flags settings are optional for this
command. This example is not compatible with exporting data to runtime, and thus should only be
used in cases where the calling application is intended to be a pre-boot only utility. For further
information on the DYNAMIC and INTERACTIVE flags, see sections 4.3.3 and 4.3.4.
Example: string
endstring;
varid = NULL.ModemString,
prompt = STR_MODEM_STRING_PROMPT,
help = STR_MODEM_STRING_HELP,
minsize = 1,
maxsize = 60,
flags = INTERACTIVE,
key = MODEM_STRING_KEY,
More information about interacting with hardware is contained in section 2.6.
4.2.17 password
This command allows for the entry of a system password. It does not dictate system policy; the actual
prompting for a power-on password is not done from the setup infrastructure. However, if a password
is already set, the user will be prompted for the original password prior to allowing the user to change
the password.
Additionally, the storage format of the password is defined both by the VFR password encoding
setting and the infrastructure itself. If the encoding is set to a zero value, the password will be stored
in it’s Unicode format without encryption. The reference implementation provides a very rudimentary
sample of an encryption mechanism which would be enabled by setting the encoding flag to one.
Example: password
varid = NvRamMap.Password,
prompt = STR_PASSWORD_PROMPT,
help = STR_PASSWORD_HELP,
35