Home
last modified time | relevance | path

Searched refs:UEFI (Results 1 – 25 of 138) sorted by relevance

123456

/openbmc/linux/Documentation/arch/arm/
H A Duefi.rst2 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
10 UEFI are used somewhat interchangeably in this document and associated
11 source code. As a rule, anything new uses 'UEFI', whereas 'EFI' refers
14 UEFI support in Linux
16 Booting on a platform with firmware compliant with the UEFI specification
19 - UEFI Runtime Services
21 interface of UEFI configuration tables. (ACPI, SMBIOS, ...)
[all …]
/openbmc/openbmc-test-automation/redfish/systems/
H A Dtest_boot_devices.robot39 ... UEFI=BIOS EFI boot
51 Once Hdd UEFI
52 Once Pxe UEFI
53 Once Diags UEFI
54 Once Cd UEFI
55 Once BiosSetup UEFI
56 Once None UEFI
71 Continuous Hdd UEFI
72 Continuous Pxe UEFI
73 Continuous Diags UEFI
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dxen.txt22 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 Dpython3-uefi-firmware_1.12.bb1 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/linux/Documentation/arch/x86/x86_64/
H A Duefi.rst7 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 Dboot.rst41 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/bmcweb/redfish-core/include/generated/enums/
H A Dsignature.hpp12 UEFI, enumerator
17 {SignatureTypeRegistry::UEFI, "UEFI"},
/openbmc/linux/Documentation/driver-api/firmware/efi/
H A Dindex.rst4 UEFI Support
7 UEFI stub library functions
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/
H A D0001-Platform-Corstone1000-Align-capsule-UEFI-structs.patch4 Subject: [PATCH 1/9] Platform: Corstone1000: Align capsule UEFI structs
6 The UEFI capsules are generated using the U-Boot mkeficapsule tool.
7 U-Boot uses packed struct for the UEFI and FMP structures, see [1].
37 @@ -29,21 +30,21 @@ Update Capsule Structure (UEFI spec 2.9 1004)
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/u-boot/u-boot/
H A Duefi-secureboot.cfg9 CONFIG_PREBOOT="setenv bootmenu_0 UEFI Boot Manager=bootefi bootmgr; setenv bootmenu_1 UEFI Mainten…
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/
H A D0040-fix-runtime-capsule-update-flags-checks.patch23 + /* 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/openbmc/poky/meta/classes-recipe/
H A Duki.bbclass3 # This bbclass merges kernel, initrd etc as a UKI standard UEFI binary,
4 # to be loaded with UEFI firmware and systemd-boot on target HW.
14 # - UEFI stub
15 # The linux kernel can generate a UEFI stub, however the one from systemd-boot can fetch
28 # - requires UEFI compatible firmware on target, e.g. qemuarm64-secureboot u-boot based
49 # - for UEFI secure boot, systemd-boot and uki (including kernel) can
55 # - at runtime, UEFI firmware will load and boot systemd-boot which
/openbmc/linux/Documentation/filesystems/
H A Defivarfs.rst22 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 Defivar_39.bb1 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 DKconfig.debug13 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 Dreport.txt28 [X] ACS - BSA - UEFI
33 [X] ACS - UEFI Shell dumps
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/
H A D0016-Isolate-common-uefi-variable-authentication-steps.patch62 + * UEFI: Page 246
83 + * UEFI: Page 253
96 + * UEFI: Page 253
151 * UEFI: Page 253
175 - * UEFI: Page 246
196 - * UEFI: Page 253
209 - * UEFI: Page 253
H A D0017-Implement-Private-Authenticated-Variable-verificatio.patch200 + * UEFI: Page 254
272 -set(SMM_GATEWAY_MAX_UEFI_VARIABLES 40 CACHE STRING "Maximum UEFI variable count")
273 +set(SMM_GATEWAY_MAX_UEFI_VARIABLES 35 CACHE STRING "Maximum UEFI variable count")
285 -set(SMM_GATEWAY_MAX_UEFI_VARIABLES 40 CACHE STRING "Maximum UEFI variable count")
286 +set(SMM_GATEWAY_MAX_UEFI_VARIABLES 35 CACHE STRING "Maximum UEFI variable count")
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-firmware-efi-esrt6 the UEFI UpdateCapsule mechanism described in section 7.5 of
7 the UEFI Standard.
43 3 UEFI Driver
/openbmc/libcper/
H A DREADME.md3 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/libcper/generator/
H A DREADME.md5 definitions present within UEFI Specification Appendix N.
30 included in UEFI Appendix N) generally do not have their structures to
/openbmc/linux/Documentation/networking/devlink/
H A Dsfc.rst53 multiple images (e.g. PXE and UEFI), this is the specifically the PXE boot
57 - UEFI driver version (No UNDI support).
/openbmc/linux/Documentation/arch/arm64/
H A Darm-acpi.rst14 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.
290 is that UEFI will leave the device in a reasonable default state, including
335 Device properties that have not been registered with the UEFI Forum can be used
340 as DT bindings, or the UEFI Forum as device properties. While we do not want
352 registered with the UEFI Forum [4], which will review it again for consistency
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/
H A Dsoftware-architecture.rst194 For UEFI Secure Boot, authenticated variables can be accessed from the secure flash.
195 The feature has been integrated in U-Boot, which authenticates the images as per the UEFI
250 Image (the initramfs bundle). The new images are accepted in the form of a UEFI capsule.
259 that can start writing UEFI capsule into the flash.
264 images in the flash. The communication between the UEFI Capsule update
287 UEFI Runtime Support in U-Boot
290 Implementation of UEFI boottime and runtime APIs require variable storage.
291 In Corstone-1000, these UEFI variables are stored in the Protected Storage
292 service. The below diagram presents the data flow to store UEFI variables.
293 The U-Boot implementation of the UEFI subsystem uses the U-Boot FF-A driver to
/openbmc/u-boot/lib/efi_loader/
H A DKconfig44 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

123456