mirror of
				https://git.proxmox.com/git/mirror_edk2
				synced 2025-10-31 07:17:27 +00:00 
			
		
		
		
	 9344f09215
			
		
	
	
		9344f09215
		
	
	
	
	
		
			
			https://bugzilla.tianocore.org/show_bug.cgi?id=1373 Replace BSD 2-Clause License with BSD+Patent License. This change is based on the following emails: https://lists.01.org/pipermail/edk2-devel/2019-February/036260.html https://lists.01.org/pipermail/edk2-devel/2018-October/030385.html RFCs with detailed process for the license change: V3: https://lists.01.org/pipermail/edk2-devel/2019-March/038116.html V2: https://lists.01.org/pipermail/edk2-devel/2019-March/037669.html V1: https://lists.01.org/pipermail/edk2-devel/2019-March/037500.html Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> Reviewed-by: Liming Gao <liming.gao@intel.com>
		
			
				
	
	
		
			67 lines
		
	
	
		
			2.5 KiB
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			67 lines
		
	
	
		
			2.5 KiB
		
	
	
	
		
			C
		
	
	
	
	
	
| /** @file
 | |
|   Boot Device Selection Architectural Protocol as defined in PI spec Volume 2 DXE
 | |
| 
 | |
|   When the DXE core is done it calls the BDS via this protocol.
 | |
| 
 | |
|   Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
 | |
|   SPDX-License-Identifier: BSD-2-Clause-Patent
 | |
| 
 | |
| **/
 | |
| 
 | |
| #ifndef __ARCH_PROTOCOL_BDS_H__
 | |
| #define __ARCH_PROTOCOL_BDS_H__
 | |
| 
 | |
| ///
 | |
| /// Global ID for the BDS Architectural Protocol
 | |
| ///
 | |
| #define EFI_BDS_ARCH_PROTOCOL_GUID \
 | |
|   { 0x665E3FF6, 0x46CC, 0x11d4, {0x9A, 0x38, 0x00, 0x90, 0x27, 0x3F, 0xC1, 0x4D } }
 | |
| 
 | |
| ///
 | |
| /// Declare forward reference for the BDS Architectural Protocol
 | |
| ///
 | |
| typedef struct _EFI_BDS_ARCH_PROTOCOL   EFI_BDS_ARCH_PROTOCOL;
 | |
| 
 | |
| /**
 | |
|   This function uses policy data from the platform to determine what operating
 | |
|   system or system utility should be loaded and invoked.  This function call
 | |
|   also optionally make the use of user input to determine the operating system
 | |
|   or system utility to be loaded and invoked.  When the DXE Core has dispatched
 | |
|   all the drivers on the dispatch queue, this function is called.  This
 | |
|   function will attempt to connect the boot devices required to load and invoke
 | |
|   the selected operating system or system utility.  During this process,
 | |
|   additional firmware volumes may be discovered that may contain addition DXE
 | |
|   drivers that can be dispatched by the DXE Core.   If a boot device cannot be
 | |
|   fully connected, this function calls the DXE Service Dispatch() to allow the
 | |
|   DXE drivers from any newly discovered firmware volumes to be dispatched.
 | |
|   Then the boot device connection can be attempted again.  If the same boot
 | |
|   device connection operation fails twice in a row, then that boot device has
 | |
|   failed, and should be skipped.  This function should never return.
 | |
| 
 | |
|   @param  This             The EFI_BDS_ARCH_PROTOCOL instance.
 | |
| 
 | |
|   @return None.
 | |
| 
 | |
| **/
 | |
| typedef
 | |
| VOID
 | |
| (EFIAPI *EFI_BDS_ENTRY)(
 | |
|   IN EFI_BDS_ARCH_PROTOCOL  *This
 | |
|   );
 | |
| 
 | |
| ///
 | |
| /// The EFI_BDS_ARCH_PROTOCOL transfers control from DXE to an operating
 | |
| /// system or a system utility.  If there are not enough drivers initialized
 | |
| /// when this protocol is used to access the required boot device(s), then
 | |
| /// this protocol should add drivers to the dispatch queue and return control
 | |
| /// back to the dispatcher.  Once the required boot devices are available, then
 | |
| /// the boot device can be used to load and invoke an OS or a system utility.
 | |
| ///
 | |
| struct _EFI_BDS_ARCH_PROTOCOL {
 | |
|   EFI_BDS_ENTRY Entry;
 | |
| };
 | |
| 
 | |
| extern EFI_GUID gEfiBdsArchProtocolGuid;
 | |
| 
 | |
| #endif
 |