-\r
- @param This Pointer to the EFI_IP4_CONFIG_PROTOCOL instance.\r
- @param DoneEvent Event that will be signaled when the EFI IPv4 Protocol driver\r
- configuration policy completes execution. This event must be of\r
- type EVT_NOTIFY_SIGNAL.\r
- @param ReconfigEvent Event that will be signaled when the EFI IPv4 Protocol driver\r
- configuration needs to be updated. This event must be of type\r
- EVT_NOTIFY_SIGNAL.\r
-\r
- @retval EFI_SUCCESS The configuration policy for the EFI IPv4 Protocol driver is now\r
- running.\r
- @retval EFI_INVALID_PARAMETER This, DoneEvent, or ReconfigEvent is NULL.\r
- @retval EFI_OUT_OF_RESOURCES Required system resources could not be allocated.\r
- @retval EFI_ALREADY_STARTED The configuration policy for the EFI IPv4 Protocol driver was\r
- already started.\r
- @retval EFI_DEVICE_ERROR An unexpected system error or network error occurred.\r
- @retval EFI_UNSUPPORTED This interface does not support the EFI IPv4 Protocol driver\r
- configuration.\r
+ \r
+ The Start() function is called to determine and to begin the platform \r
+ configuration policy by the EFI IPv4 Protocol driver. This determination may \r
+ be as simple as returning EFI_UNSUPPORTED if there is no EFI IPv4 Protocol \r
+ driver configuration policy. It may be as involved as loading some defaults \r
+ from nonvolatile storage, downloading dynamic data from a DHCP server, and \r
+ checking permissions with a site policy server.\r
+ Starting the configuration policy is just the beginning. It may finish almost \r
+ instantly or it may take several minutes before it fails to retrieve configuration \r
+ information from one or more servers. Once the policy is started, drivers \r
+ should use the DoneEvent parameter to determine when the configuration policy \r
+ has completed. EFI_IP4_CONFIG_PROTOCOL.GetData() must then be called to \r
+ determine if the configuration succeeded or failed.\r
+ Until the configuration completes successfully, EFI IPv4 Protocol driver instances \r
+ that are attempting to use default configurations must return EFI_NO_MAPPING.\r
+ Once the configuration is complete, the EFI IPv4 Configuration Protocol driver \r
+ signals DoneEvent. The configuration may need to be updated in the future. \r
+ Note that in this case the EFI IPv4 Configuration Protocol driver must signal \r
+ ReconfigEvent, and all EFI IPv4 Protocol driver instances that are using default \r
+ configurations must return EFI_NO_MAPPING until the configuration policy has \r
+ been rerun.\r
+\r
+ @param This The pointer to the EFI_IP4_CONFIG_PROTOCOL instance.\r
+ @param DoneEvent Event that will be signaled when the EFI IPv4 \r
+ Protocol driver configuration policy completes \r
+ execution. This event must be of type EVT_NOTIFY_SIGNAL.\r
+ @param ReconfigEvent Event that will be signaled when the EFI IPv4 \r
+ Protocol driver configuration needs to be updated. \r
+ This event must be of type EVT_NOTIFY_SIGNAL.\r
+ \r
+ @retval EFI_SUCCESS The configuration policy for the EFI IPv4 Protocol \r
+ driver is now running.\r
+ @retval EFI_INVALID_PARAMETER One or more of the following parameters is NULL:\r
+ This\r
+ DoneEvent\r
+ ReconfigEvent\r
+ @retval EFI_OUT_OF_RESOURCES Required system resources could not be allocated.\r
+ @retval EFI_ALREADY_STARTED The configuration policy for the EFI IPv4 Protocol \r
+ driver was already started.\r
+ @retval EFI_DEVICE_ERROR An unexpected system error or network error occurred.\r
+ @retval EFI_UNSUPPORTED This interface does not support the EFI IPv4 Protocol \r
+ driver configuration.\r