| /openbmc/linux/Documentation/arch/arm/ |
| H A D | uefi.rst | 2 The Unified Extensible Firmware Interface (UEFI)
5 UEFI, the Unified Extensible Firmware Interface, is a specification
7 maintained by the UEFI Forum - http://www.uefi.org/.
9 UEFI is an evolution of its predecessor 'EFI', so the terms EFI and
14 UEFI support in Linux
19 - UEFI Runtime Services
21 interface of UEFI configuration tables. (ACPI, SMBIOS, ...)
31 UEFI stub
39 booting in non-UEFI environments.
41 UEFI kernel support on ARM
[all …]
|
| /openbmc/openbmc-test-automation/redfish/systems/ |
| H A D | test_boot_devices.robot | 39 ... UEFI=BIOS EFI boot
151 Hdd UEFI
152 Pxe UEFI
153 Diags UEFI
154 Cd UEFI
155 None UEFI
169 Hdd UEFI
170 Pxe UEFI
171 Diags UEFI
172 Cd UEFI
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | xen.txt | 22 To support UEFI on Xen ARM virtual platforms, Xen populates the FDT "uefi" node
28 xen,uefi-system-table | 64-bit | Guest physical address of the UEFI System
31 xen,uefi-mmap-start | 64-bit | Guest physical address of the UEFI memory
34 xen,uefi-mmap-size | 32-bit | Size in bytes of the UEFI memory map
37 xen,uefi-mmap-desc-size | 32-bit | Size in bytes of each entry in the UEFI
59 Documentation/arch/arm/uefi.rst, which are provided by the regular UEFI stub. However
61 of UEFI runtime services implemented via hypercalls, see
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-uefi-firmware_1.11.bb | 1 SUMMARY = "Various data structures and parsing tools for UEFI firmware."
2 DESCRIPTION = "This package contains Python UEFI firmware parser tool. The \
3 UEFI firmware parser is a simple module and set of scripts for parsing, \
4 extracting, and recreating UEFI firmware volumes. This includes parsing \
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | signature.hpp | 10 UEFI, enumerator
15 {SignatureTypeRegistry::UEFI, "UEFI"},
|
| /openbmc/linux/Documentation/driver-api/firmware/efi/ |
| H A D | index.rst | 4 UEFI Support
7 UEFI stub library functions
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | uefi.rst | 7 The nomenclature EFI and UEFI are used interchangeably in this document.
13 1. UEFI specification: http://www.uefi.org
15 2. Booting Linux kernel on UEFI x86_64 platform requires bootloader
18 3. x86_64 platform with EFI/UEFI firmware.
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | boot.rst | 41 as per the devicetree specification and/or the UEFI specification.
56 using the ``$a1`` register, or when booting with UEFI, it can be passed using the
77 UEFI section in Pre-kernel Requirements and Constraints
80 UEFI memory map argument
83 When booting with UEFI, the RISC-V kernel will use only the EFI memory map to
86 The UEFI firmware must parse the subnodes of the ``/reserved-memory`` devicetree
89 (refer to section "3.5.4 /reserved-memory and UEFI" of the devicetree
95 When booting with UEFI, the EFI stub requires the boot hartid in order to pass argument
113 When booting with UEFI, the devicetree is supplemented (or created) by the EFI
115 "UEFI kernel support on ARM" in Documentation/arch/arm/uefi.rst.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0040-fix-runtime-capsule-update-flags-checks.patch | 23 + /* According to UEFI specs when the flag is CAPSULE_FLAGS_PERSIST_ACROSS_RESET,
31 + /*According to UEFI specs a capsule which has the CAPSULE_FLAGS_POPULATE_SYSTEM_TABLE
41 + /* According to UEFI specs, a capsule which has the CAPSULE_FLAGS_INITIATE_RESET
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | efivarfs.rst | 22 UEFI variables causes the system firmware to fail to POST, efivarfs
29 When a content of an UEFI variable in /sys/firmware/efi/efivars is
31 4 bytes of the output represent the UEFI variable attributes,
|
| /openbmc/openbmc/poky/meta/recipes-bsp/efivar/ |
| H A D | efivar_39.bb | 1 SUMMARY = "Tools to manipulate UEFI variables"
2 DESCRIPTION = "efivar provides a simple command line interface to the UEFI variable facility"
|
| /openbmc/linux/arch/arm64/ |
| H A D | Kconfig.debug | 13 bool "UEFI debugging"
17 UEFI firmware
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/dynamic-layers/meta-arm-systemready/recipes-test/arm-systemready-acs/files/fvp-base/ |
| H A D | report.txt | 28 [X] ACS - BSA - UEFI
33 [X] ACS - UEFI Shell dumps
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/uefi/ |
| H A D | edk2-firmware-n1sdp.inc | 9 # UEFI EDK2 on N1SDP is unable to detect FS2 during boot resulting in launching of
24 file://0009-Platform-ARM-N1Sdp-Reserve-OP-TEE-Region-from-UEFI.patch;patchdir=edk2-platforms \
|
| H A D | edk2-firmware_%.bbappend | 1 # Include machine specific configurations for UEFI EDK2
|
| /openbmc/libcper/generator/ |
| H A D | README.md | 5 definitions present within UEFI Specification Appendix N.
30 included in UEFI Appendix N) generally do not have their structures to
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-efi-esrt | 6 the UEFI UpdateCapsule mechanism described in section 7.5 of
7 the UEFI Standard.
43 3 UEFI Driver
|
| /openbmc/libcper/ |
| H A D | README.md | 3 This repository specifies a structure for representing UEFI CPER records (as
4 described in UEFI Specification Appendix N) in a human-readable JSON format, in
59 [UEFI Specification Appendix N](https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_0…
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | sfc.rst | 53 multiple images (e.g. PXE and UEFI), this is the specifically the PXE boot
57 - UEFI driver version (No UNDI support).
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/ |
| H A D | ts-sp-smm-gateway_git.bb | 1 DESCRIPTION = "Trusted Services service provider for UEFI SMM services"
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | arm-acpi.rst | 14 it refers to are managed by the UEFI Forum. The specification is
65 ACPI governance into the UEFI forum has significantly opened up the
126 is via the UEFI system configuration table. Just so it is explicit, this
127 means that ACPI is only supported on platforms that boot via UEFI.
141 In order for the kernel to load and use ACPI tables, the UEFI implementation
149 the kernel by the ACPI core, using the address provided by UEFI.
353 within the registry. This may require iteration. The UEFI Forum, though,
356 It may make sense to provide notice to the UEFI Forum that there is the
421 UEFI, in this case -- to some working value before control is handed over
511 Participation in this group is open to all UEFI members. Please see
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | software-architecture.rst | 170 Image (the initramfs bundle). The new images are accepted in the form of a UEFI capsule.
179 that can start writing UEFI capsule into the flash. Once this operation finishes
183 images in the flash. The communication between the UEFI Capsule update
204 UEFI Runtime Support in U-Boot
207 Implementation of UEFI boottime and runtime APIs require variable storage.
208 In Corstone-1000, these UEFI variables are stored in the Protected Storage
209 service. The below diagram presents the data flow to store UEFI variables.
210 The U-Boot implementation of the UEFI subsystem uses the U-Boot FF-A driver to
|
| /openbmc/u-boot/lib/efi_loader/ |
| H A D | Kconfig | 44 allows UEFI applications to draw fancy menus and hook strings using
47 U-Boot implements enough of its features to be able to run the UEFI
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | FaultLogType.interface.yaml | 11 UEFI Common Platform Error Record.
|
| /openbmc/linux/Documentation/fb/ |
| H A D | efifb.rst | 5 This is a generic EFI platform driver for systems with UEFI firmware. The
17 - ARM/ARM64/X86 systems with UEFI firmware
|