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