UEFI 2.2 Spec!

最新推荐文章于 2024-09-23 15:33:36 发布
原创 最新推荐文章于 2024-09-23 15:33:36 发布 · 1.4k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

博客提及UEFI.org，但未提供更多详细内容。UEFI在信息技术领域有重要应用，可能涉及计算机启动等相关技术。
xtdumpling
关注
UEFI Spec chapter10 protocols-Device Path Protocol
china_seaman的博客
02-07 1466
提示：文章写完后，目录可以自动生成，如何生成可参考右边的帮助文档 文章目录 前言 一、pandas是什么？ 二、使用步骤 1.引入库 2.读入数据 总结 前言 本节包含设备路径协议的定义，以及在UEFI环境中构建和管理设备路径所需的信息。固件构造并使用设备路径来传递重要设备的位置，如引导设备和控制台，这与系统的软件可见拓扑结构一致。 提示：以下是本篇文章正文内容，下面案例可供参考 一、Device Path Overview 设备路径用于定义到设备的编程路径。设备路
UEFI 2.8协议规范(英文)---UEFI_Spec_2_8_final.pdf
03-11
This Unified Extensible Firmware Interface (hereafter known as UEFI) Specification describes an interface between the operating system (OS) and the platform firmware. UEFI was preceded by the Extensible Firmware Interface Specification 1.10 (EFI). As a result, some code and certain protocol names retain the EFI designation. Unless otherwise noted, EFI designations in this specification may be assumed to be part of UEFI. The interface is in the form of data tables that contain platform-related information, and boot and runtime service calls that are available to the OS loader and the OS. Together, these provide a standard environment for booting an OS. This specification is designed as a pure interface specification. As such, the specification defines the set of interfaces and structures that platform firmware must implement. Similarly, the specification defines the set of interfaces and structures that the OS may use in booting. How either the firmware developer chooses to implement the required elements or the OS developer chooses to make use of those interfaces and structures is an implementation decision left for the developer. The intent of this specification is to define a way for the OS and platform firmware to communicate only information necessary to support the OS boot process. This is accomplished through a formal and complete abstract specification of the software-visible interface presented to the OS by the platform and firmware. Using this formal definition, a shrink-wrap OS intended to run on platforms compatible with supported processor specifications will be able to boot on a variety of system designs without further platform or OS customization. The definition will also allow for platform innovation to introduce new features and functionality that enhance platform capability without requiring new code to be written in the OS boot sequence. Furthermore, an abstract specification opens a route to replace legacy devices and firmware code over time. New device types and associated code can provide equivalent functionality through the same defined abstract interface, again without impact on the OS boot support code. The specification is applicable to a full range of hardware platforms from mobile systems to servers. The specification provides a core set of services along with a selection of protocol interfaces. The selection of protocol interfaces can evolve over time to be optimized for various platform market segments. At the same time, the specification allows maximum extensibility and customization abilities for OEMs to allow differentiation. In this, the purpose of UEFI is to define an evolutionary path from the traditional “PC-AT”- style boot world into a legacy-API free environment.
所有的UEFI Spec文档
03-24
所有做UEFI开发的饭碗
UEFI_Spec_2_8_A_Feb14.pdf
03-11
This Unified Extensible Firmware Interface (UEFI) Specification describes an interface between the operating system (OS) and the platform firmware. UEFI was preceded by the Extensible Firmware Interface Specification 1.10 (EFI). As a result, some code and certain protocol names retain the EFI designation. Unless otherwise noted, EFI designations in this specification may be assumed to be part of UEFI. The interface is in the form of data tables that contain platform-related information, and boot and runtime service calls that are available to the OS loader and the OS. Together, these provide a standard environment for booting an OS. This specification is designed as a pure interface specification. As such, the specification defines the set of interfaces and structures that platform firmware must implement. Similarly, the specification defines the set of interfaces and structures that the OS may use in booting. How either the firmware developer chooses to implement the required elements or the OS developer chooses to make use of those interfaces and structures is an implementation decision left for the developer. The intent of this specification is to define a way for the OS and platform firmware to communicate only information necessary to support the OS boot process. This is accomplished through a formal and complete abstract specification of the software-visible interface presented to the OS by the platform and firmware. Using this formal definition, a shrink-wrap OS intended to run on platforms compatible with supported processor specifications will be able to boot on a variety of system designs without further platform or OS customization. The definition will also allow for platform innovation to introduce new features and functionality that enhance platform capability without requiring new code to be written in the OS boot sequence. Furthermore, an abstract specification opens a route to replace legacy devices and firmware code over time. New device types and associated code can provide equivalent functionality through the same defined abstract interface, again without impact on the OS boot support code. The specification is applicable to a full range of hardware platforms from mobile systems to servers. The specification provides a core set of services along with a selection of protocol interfaces. The selection of protocol interfaces can evolve over time to be optimized for various platform market segments. At the same time, the specification allows maximum extensibility and customization abilities for OEMs to allow differentiation. In this, the purpose of UEFI is to define an evolutionary path from the traditional “PC-AT”- style boot world into a legacy-API free environment.
UEFI Spec，2.3.1，2011-06最新版
11-15
UEFI BIOS平台的详细规范，2.3.1版本，2011年6月
UEFI 2.2 spec
08-06
根据给定的文件信息，我们可以深入探讨UEFI（Unified Extensible Firmware Interface）2.2规格以及与之相关的UEFI BIOS运行环境。UEFI是现代计算机系统中替代传统BIOS（基本输入/输出系统）的一项技术，它提供了一个...
UEFI Spec 2.2
04-25
《UEFI规范2.2详解》 统一可扩展固件接口（UEFI）规范2.2是BIOS系统中的一项重要标准，它旨在提供一个更加现代化、安全且高效的引导环境，替代传统的BIOS系统。UEFI规范定义了硬件平台与操作系统之间的接口，包括...
精选资源
uefi dsc spec
06-14
UEFI DSC Spec UEFI DSC（Device Specific Configuration）spec是EDK II（Extensible Firmware Interface）平台描述文件的specification，用于描述基于UEFI firmware的平台配置。该spec主要用于指导开发者创建符合...
UEFI Spec2.2
10-15
UEFI Spec 2.2是UEFI论坛发布的规范版本，提供了详细的UEFI实现指南和技术标准。这个2000多页的PDF文档包含了关于UEFI的所有核心组件、接口、协议和程序设计的详尽信息，对于开发者、系统集成商和研究者来说是不可或...
UEFI 平台初始化 (PI) 规范中文版第 1 卷：Pre-EFI 初始化核心接口.pdf
12-05
PI 规范中文翻译版本，机器翻译，但可读性高尚可，推荐配合原文阅读。
UEFI_Spec_2_9_2021_03_18.pdf
12-09
统一可扩展固件接口(UEFI)规范描述了操作系统和平台固件之间的接口。UEFI之前是可扩展固件接口规范1.10 (EFI)。因此，一些代码和某些协议名称保留了EFI名称。除非另有说明，本规范中的EFI名称可能被认为是UEFI的一部分。 接口采用数据表的形式，其中包含与平台相关的信息，以及OS加载器和OS可用的引导和运行时服务调用。它们共同提供了一个引导操作系统的标准环境。本规范是作为一个纯粹的接口规范设计的。因此，该规范定义了平台固件必须实现的接口和结构集。类似地，该规范定义了操作系统在引导时可能使用的一组接口和结构。固件开发人员如何选择实现所需的元素，或者操作系统开发人员如何选择利用这些接口和结构，这是留给开发人员的实现决策。 该规范的目的是定义一种方法，使操作系统和平台固件仅通信支持操作系统引导过程所必需的信息。这是通过平台和固件提供给操作系统的软件可见接口的正式和完整的抽象规范来实现的。 使用这一正式定义，旨在运行在与受支持的处理器规范兼容的平台上的收缩包装操作系统将能够在各种系统设计上启动，而无需进一步的平台或操作系统定制。该定义还允许平台创新引入新特性和功能，以增强平台的能力，而不需要按照操作系统的引导顺序编写新代码。 此外，抽象规范开辟了一条替代遗留设备和固件代码的路径。新的设备类型和相关代码可以通过相同定义的抽象接口提供同等的功能，同样不会影响OS引导支持代码。 该规范适用于从移动系统到服务器的所有硬件平台。该规范提供了一组核心服务以及一组协议接口。协议接口的选择可以随着时间的推移而发展，并针对不同的平台市场细分进行优化。与此同时，该规范允许oem提供最大限度的可扩展性和定制能力，以实现差异化。在这方面，UEFI的目的是定义一个从传统的“PC-AT”风格的引导世界到一个没有遗留api的环境的进化路径。
UEFI_Spec_2_8_2021.zip
03-10
UEFI Spec 2.8 规范 修正版
UEFI_Spec_2_8_final.pdf
01-09
UEFI_Spec_2_8_final.pdf
UEFI EDKII Build Spec
07-29
This document describes the EDK II Build Architecture. This specification was designed to support new build requirements for building EDK components within the EDK II build infrastructure. EDK II Build utilities described in this document use INI style text based meta-data files to describe components, modules, libraries, platforms, firmware volumes and firmware device images.
UEFI spec V2.8 A
12-19
UEFI Specification Version 2.8 (Errata A) (released February 2020) UEFI 组织2020年发布的文档，由于项目中排查uboot格式化分区与qnx系统中的格式化分区的问题，搜索了下国内的UEFI标准，都太旧并且要50个币？？？ 都是搬运工，最多5个币
uefi怎么念_UEFI规范导读
weixin_33557333的博客
12-24 550
UEFI规范第一章Introduction这一章是整个UEFI的设计思想进行概要性介绍，提到UEFI规范的设计目标。对规范本身的一些名词术语的用法，文本的编排等做了一些说明。并且还简单讲了讲对legacy系统的兼容性问题。这一章属于总体性的说明，我强力建议大家首先通读这一章。UEFI规范第二章Overview这一章是对UEFIBIOS的一些基本组件的介绍，以及一些基本概念(如Handle，Pro...
【UEFI Spec笔记】Boot Manager
Mutouyugi的博客
07-12 1570
后续有更深理解，会继续补充。学艺不精，错误请指正；如有侵权，请联系删除。参考文档： 《UEFI_Spec_2_9_2021_03_18》
【BIOS/UEFI】HII 基本框架及概述
weixin_45258382的博客
12-23 7486
HII（Human Interface Infrastructure ）定义了一套管理用户输入的基础框架。HII数据库主要提供用户安装、卸载以及使用各种字符串、字体和图片等资源的接口。驱动程序和应用程序将元素（如字体、字符串、图像和表单）安装到 HII 数据库中，该数据库充当整个平台的中央存储库。Forms Browser 使用这些元素在显示设备上呈现用户界面，并通过 HID 设备从用户接收信息。
UEFI Spec 学习笔记 章节一
最新发布
JUSTIN_TYL的博客
09-23 1079
简单介绍UEFI 的内容和由来
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值