-Routine Description:\r
-\r
- NV read function for the iSCSI form callback protocol.\r
-\r
-Arguments:\r
-\r
- This - The EFI form callback protocol instance.\r
- VariableName - Name of the variable to read.\r
- VendorGuid - Guid of the variable to read.\r
- Attributes - The storage to get the attributes of the variable.\r
- DataSize - The size of the buffer to store the variable.\r
- Buffer - The buffer to store the variable to read.\r
-\r
-Returns:\r
-\r
- EFI_SUCCESS - The variable is read.\r
- EFI_BUFFER_TOO_SMALL - The buffer provided is too small to hold the variable.\r
+ Routine Description:\r
+ This function allows a caller to extract the current configuration for one\r
+ or more named elements from the target driver.\r
+\r
+ Arguments:\r
+ This - Points to the EFI_HII_CONFIG_ACCESS_PROTOCOL.\r
+ Request - A null-terminated Unicode string in <ConfigRequest> format.\r
+ Progress - On return, points to a character in the Request string.\r
+ Points to the string's null terminator if request was successful.\r
+ Points to the most recent '&' before the first failing name/value\r
+ pair (or the beginning of the string if the failure is in the\r
+ first name/value pair) if the request was not successful.\r
+ Results - A null-terminated Unicode string in <ConfigAltResp> format which\r
+ has all values filled in for the names in the Request string.\r
+ String to be allocated by the called function.\r
+\r
+ Returns:\r
+ EFI_SUCCESS - The Results is filled with the requested values.\r
+ EFI_OUT_OF_RESOURCES - Not enough memory to store the results.\r
+ EFI_INVALID_PARAMETER - Request is NULL, illegal syntax, or unknown name.\r
+ EFI_NOT_FOUND - Routing data doesn't match any storage in this driver.\r