| /freebsd/sys/contrib/edk2/Include/Protocol/ |
| H A D | VariableWrite.h | 2 Variable Write Architectural Protocol as defined in PI Specification VOLUME 2 DXE 5 This protocol must be produced by a runtime DXE driver and may be consumed only 6 by the DXE Foundation. 8 The DXE driver that produces this protocol must be a runtime driver. This driver 13 interface pointer. The installation of this protocol informs the DXE Foundation 15 and that the DXE Foundation must update the 32-bit CRC of the UEFI Runtime Services 17 until both this protocol and EFI_VARIABLE_ARCH_PROTOCOL are installed. DXE drivers 20 DXE drivers that require write access to nonvolatile environment variables must
|
| H A D | Variable.h | 2 Variable Architectural Protocol as defined in PI Specification VOLUME 2 DXE 5 protocol must be produced by a runtime DXE driver and may be consumed only by 6 the DXE Foundation. The DXE driver that produces this protocol must be a runtime 12 a NULL interface pointer. The installation of this protocol informs the DXE Foundation 14 now available and that the DXE Foundation must update the 32-bit CRC of the UEFI 17 installed. DXE drivers that require read-only access or read/write access to volatile 19 expressions. DXE drivers that require write access to nonvolatile environment
|
| H A D | Security.h | 2 Security Architectural Protocol as defined in PI Specification VOLUME 2 DXE 6 portable DXE Core Dispatcher will call into the Security Architectural 13 The SAP can also change system behavior by having the DXE core put a driver 35 policy from the DXE core response to an attempt to use a file that returns a 46 AuthenticationStatus is safe for the DXE Core to use, then EFI_SUCCESS is returned. 49 AuthenticationStatus is not safe for the DXE Core to use under any circumstances, 53 AuthenticationStatus is not safe for the DXE Core to use right now, but it 66 platform policy dictates that the DXE Core may use File. 72 with a call to the Trust() DXE Service. 88 /// from the DXE core. This includes locking flash upon failure to authenticate,
|
| H A D | Runtime.h | 2 Runtime Architectural Protocol as defined in PI Specification VOLUME 2 DXE 4 Allows the runtime functionality of the DXE Foundation to be contained 5 in a separate driver. It also provides hooks for the DXE Foundation to 7 services to the DXE Foundation to manage runtime drivers and events. 11 must be produced by a runtime DXE driver and may only be consumed by the DXE Foundation. 98 /// Allows the runtime functionality of the DXE Foundation to be contained in a 99 /// separate driver. It also provides hooks for the DXE Foundation to export 100 /// information that is needed at runtime. As such, this protocol allows the DXE 105 /// by a runtime DXE driver and may only be consumed by the DXE Foundation.
|
| H A D | Bds.h | 2 Boot Device Selection Architectural Protocol as defined in PI spec Volume 2 DXE 4 When the DXE core is done it calls the BDS via this protocol. 29 or system utility to be loaded and invoked. When the DXE Core has dispatched 33 additional firmware volumes may be discovered that may contain addition DXE 34 drivers that can be dispatched by the DXE Core. If a boot device cannot be 35 fully connected, this function calls the DXE Service Dispatch() to allow the 36 DXE drivers from any newly discovered firmware volumes to be dispatched. 53 /// The EFI_BDS_ARCH_PROTOCOL transfers control from DXE to an operating
|
| H A D | Security2.h | 2 Security2 Architectural Protocol as defined in PI Specification1.2.1 VOLUME 2 DXE 4 Abstracts security-specific functions from the DXE Foundation of UEFI Image Verification, 6 consoles. This protocol must be produced by a boot service or runtime DXE driver. 37 The DXE Foundation uses this service to measure and/or verify a UEFI image. 40 Secure boot, and UEFI User Identity infrastructure. For the former two, the DXE Foundation 60 that the DXE Foundation may use the file. 63 policy dictates that the DXE Foundation may execute the image in 72 authenticate, and the platform policy dictates that the DXE 91 /// DXE Foundation. This includes measuring the PE/COFF image prior to invoking, comparing the
|
| H A D | Capsule.h | 2 Capsule Architectural Protocol as defined in PI1.0a Specification VOLUME 2 DXE 4 The DXE Driver that produces this protocol must be a runtime driver. 10 the DXE Foundation that the Capsule related services are now available and 11 that the DXE Foundation must update the 32-bit CRC of the UEFI Runtime Services Table.
|
| H A D | Timer.h | 2 Timer Architectural Protocol as defined in PI Specification VOLUME 2 DXE 4 This code is used to provide the timer tick for the DXE core. 27 function executes at TPL_HIGH_LEVEL. The DXE Core will register a function 60 function executes at TPL_HIGH_LEVEL. The DXE Core will
|
| H A D | StatusCode.h | 2 Status code Runtime Protocol as defined in PI Specification 1.4a VOLUME 2 DXE 45 /// This protocol must be produced by a runtime DXE driver.
|
| H A D | Metronome.h | 2 Metronome Architectural Protocol as defined in PI SPEC VOLUME 2 DXE 4 This code abstracts the DXE core to provide delay services.
|
| H A D | Cpu.h | 2 CPU Architectural Protocol as defined in PI spec Volume 2 DXE 4 This code abstracts the DXE core from processor implementation details. 254 /// The EFI_CPU_ARCH_PROTOCOL is used to abstract processor-specific functions from the DXE
|
| H A D | MonotonicCounter.h | 2 Monotonic Counter Architectural Protocol as defined in PI SPEC VOLUME 2 DXE
|
| H A D | Reset.h | 2 Reset Architectural Protocol as defined in PI Specification VOLUME 2 DXE
|
| H A D | FirmwareVolume2.h | 5 the system during the DXE phase. The Firmware Volume Protocol also provides 209 during the DXE phase. The actual binary encoding of the file in 714 /// DXE that are not directly involved with managing the firmware
|
| H A D | WatchdogTimer.h | 2 Watchdog Timer Architectural Protocol as defined in PI Specification VOLUME 2 DXE
|
| /freebsd/sys/contrib/edk2/Include/Pi/ |
| H A D | PiDependency.h | 17 /// EFI_DEP_BEFORE may be used by DXE and SMM drivers. 23 /// EFI_DEP_AFTER may be used by DXE and SMM drivers. 37 /// EFI_DEP_SOR is only used by DXE driver.
|
| H A D | PiStatusCode.h | 228 /// PCI Host Bridge DXE initialization. 233 /// North Bridge DXE initialization. 238 /// North Bridge specific SMM initialization in DXE. 248 /// South Bridge DXE initialization 253 /// South Bridge specific SMM initialization in DXE. 786 /// Software Class DXE Core Subclass Progress Code definitions. 797 /// Software Class DXE BS Driver Subclass Progress Code definitions. 954 /// Software Class EFI DXE Services Subclass Progress Code definitions 1038 /// Software Class DXE Foundation Subclass Error Code definitions. 1045 /// Software Class DXE Boot Service Driver Subclass Error Code definitions. [all …]
|
| /freebsd/sys/contrib/edk2/Include/Guid/ |
| H A D | DxeServices.h | 2 GUID used to identify the DXE Services Table 16 // The DXE Services Table shall be stored in memory of type
|
| /freebsd/sys/contrib/device-tree/Bindings/remoteproc/ |
| H A D | qcom,wcnss-pil.txt | 17 Definition: must specify the base address and size of the CCU, DXE and 23 Definition: must be "ccu", "dxe", "pmu" 123 reg-names = "ccu", "dxe", "pmu";
|
| H A D | qcom,wcnss-pil.yaml | 32 The base address and size of the CCU, DXE and PMU register blocks 37 - const: dxe 257 reg-names = "ccu", "dxe", "pmu";
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/qcom/ |
| H A D | qcom,wcnss.txt | 21 Definition: reference to a node specifying the wcnss "ccu" and "dxe" 129 reg-names = "ccu", "dxe", "pmu";
|
| H A D | qcom,wcnss.yaml | 30 Reference to a node specifying the wcnss "ccu" and "dxe" register blocks.
|
| /freebsd/sys/contrib/edk2/Include/Library/ |
| H A D | UefiBootServicesTableLib.h | 3 Only available to DXE and UEFI module types.
|
| /freebsd/sys/contrib/edk2/ |
| H A D | MdePkg.dec | 63 # Only available to DXE and UEFI module types. 67 # Only available to DXE and UEFI module types. 71 # Only available to DXE and UEFI module types. 75 …libraryclass Module entry point library for UEFI drivers, DXE Drivers, DXE SMM Driver and DXE Run… 82 # Only available to DXE and UEFI module types. 171 …## @libraryclass Provides services to create and parse HOBs. Only available for PEI and DXE modu… 174 ## @libraryclass Provides a service to retrieve a pointer to the DXE Services Table. 175 # Only available to DXE module types. 179 ## @libraryclass Module entry point library for DXE core. 210 ## @libraryclass Provides a set of PI library functions and macros for DXE phase. [all …]
|
| /freebsd/sys/contrib/edk2/Include/Uefi/ |
| H A D | UefiMultiPhase.h | 2 This includes some definitions introduced in UEFI that will be used in both PEI and DXE phases.
|