Path: blob/main/sys/contrib/edk2/Include/Protocol/Bds.h
96339 views
/** @file1Boot Device Selection Architectural Protocol as defined in PI spec Volume 2 DXE23When the DXE core is done it calls the BDS via this protocol.45Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>6SPDX-License-Identifier: BSD-2-Clause-Patent78**/910#ifndef __ARCH_PROTOCOL_BDS_H__11#define __ARCH_PROTOCOL_BDS_H__1213///14/// Global ID for the BDS Architectural Protocol15///16#define EFI_BDS_ARCH_PROTOCOL_GUID \17{ 0x665E3FF6, 0x46CC, 0x11d4, {0x9A, 0x38, 0x00, 0x90, 0x27, 0x3F, 0xC1, 0x4D } }1819///20/// Declare forward reference for the BDS Architectural Protocol21///22typedef struct _EFI_BDS_ARCH_PROTOCOL EFI_BDS_ARCH_PROTOCOL;2324/**25This function uses policy data from the platform to determine what operating26system or system utility should be loaded and invoked. This function call27also optionally make the use of user input to determine the operating system28or system utility to be loaded and invoked. When the DXE Core has dispatched29all the drivers on the dispatch queue, this function is called. This30function will attempt to connect the boot devices required to load and invoke31the selected operating system or system utility. During this process,32additional firmware volumes may be discovered that may contain addition DXE33drivers that can be dispatched by the DXE Core. If a boot device cannot be34fully connected, this function calls the DXE Service Dispatch() to allow the35DXE drivers from any newly discovered firmware volumes to be dispatched.36Then the boot device connection can be attempted again. If the same boot37device connection operation fails twice in a row, then that boot device has38failed, and should be skipped. This function should never return.3940@param This The EFI_BDS_ARCH_PROTOCOL instance.4142@return None.4344**/45typedef46VOID47(EFIAPI *EFI_BDS_ENTRY)(48IN EFI_BDS_ARCH_PROTOCOL *This49);5051///52/// The EFI_BDS_ARCH_PROTOCOL transfers control from DXE to an operating53/// system or a system utility. If there are not enough drivers initialized54/// when this protocol is used to access the required boot device(s), then55/// this protocol should add drivers to the dispatch queue and return control56/// back to the dispatcher. Once the required boot devices are available, then57/// the boot device can be used to load and invoke an OS or a system utility.58///59struct _EFI_BDS_ARCH_PROTOCOL {60EFI_BDS_ENTRY Entry;61};6263extern EFI_GUID gEfiBdsArchProtocolGuid;6465#endif666768