} DEVICE_PATH_STACK_ITEM;\r
\r
/**\r
- Push a controller device path into a globle device path list\r
+ Push a controller device path into a globle device path list.\r
\r
@param DevicePath The controller device path to push into stack\r
\r
);\r
\r
/**\r
+ Update the FV file device path if it is not valid.\r
+\r
According to a file GUID, check a Fv file device path is valid. If it is invalid,\r
try to return the valid device path.\r
FV address maybe changes for memory layout adjust from time to time, use this funciton\r
);\r
\r
/**\r
+ Gets the data and size of a variable.\r
+\r
Read the EFI variable (VendorGuid/Name) and return a dynamically allocated\r
buffer, and the size of the buffer. If failure return NULL.\r
\r
);\r
\r
/**\r
+ Connect to the handle to a device on the device path.\r
+\r
This function will create all handles associate with every device\r
path node. If the handle associate with one device path node can not\r
be created success, then still give one chance to do the dispatch,\r