]> git.proxmox.com Git - mirror_edk2.git/blame - OldMdePkg/Include/Dxe/ArchProtocol/Bds.h
Moved the MdePkg to OldMdePkg so that new code in MdePkg does not break existing...
[mirror_edk2.git] / OldMdePkg / Include / Dxe / ArchProtocol / Bds.h
CommitLineData
878ddf1f 1/** @file\r
2 Boot Device Selection Architectural Protocol as defined in DXE CIS\r
3\r
4 When the DXE core is done it calls the BDS via this protocol.\r
5\r
6 Copyright (c) 2006, Intel Corporation \r
7 All rights reserved. This program and the accompanying materials \r
8 are licensed and made available under the terms and conditions of the BSD License \r
9 which accompanies this distribution. The full text of the license may be found at \r
10 http://opensource.org/licenses/bsd-license.php \r
11\r
12 THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, \r
13 WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r
14\r
15 Module Name: Bds.h\r
16\r
17 @par Revision Reference:\r
18 Version 0.91B.\r
19\r
20**/\r
21\r
22#ifndef __ARCH_PROTOCOL_BDS_H__\r
23#define __ARCH_PROTOCOL_BDS_H__\r
24\r
25//\r
26// Global ID for the BDS Architectural Protocol\r
27//\r
28#define EFI_BDS_ARCH_PROTOCOL_GUID \\r
29 { 0x665E3FF6, 0x46CC, 0x11d4, {0x9A, 0x38, 0x00, 0x90, 0x27, 0x3F, 0xC1, 0x4D } }\r
30\r
31//\r
32// Declare forward reference for the BDS Architectural Protocol\r
33//\r
34typedef struct _EFI_BDS_ARCH_PROTOCOL EFI_BDS_ARCH_PROTOCOL;\r
35\r
36/**\r
37 This function uses policy data from the platform to determine what operating \r
38 system or system utility should be loaded and invoked. This function call \r
39 also optionally make the use of user input to determine the operating system \r
40 or system utility to be loaded and invoked. When the DXE Core has dispatched \r
41 all the drivers on the dispatch queue, this function is called. This \r
42 function will attempt to connect the boot devices required to load and invoke \r
43 the selected operating system or system utility. During this process, \r
44 additional firmware volumes may be discovered that may contain addition DXE \r
45 drivers that can be dispatched by the DXE Core. If a boot device cannot be \r
46 fully connected, this function calls the DXE Service Dispatch() to allow the \r
47 DXE drivers from any newly discovered firmware volumes to be dispatched. \r
48 Then the boot device connection can be attempted again. If the same boot \r
49 device connection operation fails twice in a row, then that boot device has \r
50 failed, and should be skipped. This function should never return.\r
51\r
0647c9ad 52 @param This The EFI_BDS_ARCH_PROTOCOL instance.\r
878ddf1f 53\r
54 @return None.\r
55\r
56**/\r
57typedef\r
58VOID\r
59(EFIAPI *EFI_BDS_ENTRY) (\r
60 IN EFI_BDS_ARCH_PROTOCOL *This\r
61 );\r
62\r
63/**\r
64 Interface stucture for the BDS Architectural Protocol.\r
65\r
66 @par Protocol Description:\r
67 The EFI_BDS_ARCH_PROTOCOL transfers control from DXE to an operating \r
68 system or a system utility. If there are not enough drivers initialized \r
69 when this protocol is used to access the required boot device(s), then \r
70 this protocol should add drivers to the dispatch queue and return control \r
71 back to the dispatcher. Once the required boot devices are available, then \r
72 the boot device can be used to load and invoke an OS or a system utility.\r
73\r
74 @par Protocol Parameters:\r
75 Entry - The entry point to BDS. This call does not take any parameters, \r
76 and the return value can be ignored. If it returns, then the \r
77 dispatcher must be invoked again, if it never returns, then an \r
78 operating system or a system utility have been invoked.\r
79\r
80**/\r
81struct _EFI_BDS_ARCH_PROTOCOL {\r
82 EFI_BDS_ENTRY Entry;\r
83};\r
84\r
85extern EFI_GUID gEfiBdsArchProtocolGuid;\r
86\r
87#endif\r