From: "Oleksiy Yakovlev" <oleksiyy@ami.com>
To: <devel@edk2.groups.io>
Cc: <bob.c.feng@intel.com>, <liming.gao@intel.com>,
<michael.d.kinney@intel.com>, <Felixp@ami.com>,
<oleksiyy@ami.com>
Subject: [PATCH v4 5/7] MdePkg: Bootable NVDIMM namespaces
Date: Fri, 8 May 2020 17:46:09 -0400 [thread overview]
Message-ID: <20200508214611.70592-6-oleksiyy@ami.com> (raw)
In-Reply-To: <20200508214611.70592-1-oleksiyy@ami.com>
Provided a mechanism for UEFI FW to identify and hand off bootable
NVDIMM namespaces to the OS by standardizing the EFI device path.
EFI device path for physical NVDIMM devices changed from an ACPI
_ADR device to an ACPI NVDIMM device for correctness.
(UEFI 2.8 mantis 1858)
Signed-off-by: Oleksiy Yakovlev <oleksiyy@ami.com>
---
MdePkg/Include/Protocol/DevicePath.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/MdePkg/Include/Protocol/DevicePath.h b/MdePkg/Include/Protocol/DevicePath.h
index aaec0a6..4cf4b65 100644
--- a/MdePkg/Include/Protocol/DevicePath.h
+++ b/MdePkg/Include/Protocol/DevicePath.h
@@ -712,6 +712,18 @@ typedef struct {
UINT8 StopBits;
} UART_DEVICE_PATH;
+///
+/// NVDIMM Namespace Device Path SubType.
+///
+#define NVDIMM_NAMESPACE_DP 0x20
+typedef struct {
+ EFI_DEVICE_PATH_PROTOCOL Header;
+ ///
+ /// Namespace unique label identifier UUID.
+ ///
+ EFI_GUID Uuid;
+} NVDIMM_NAMESPACE_DEVICE_PATH;
+
//
// Use VENDOR_DEVICE_PATH struct
//
--
2.9.0.windows.1
Please consider the environment before printing this email.
The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
next prev parent reply other threads:[~2020-05-08 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 21:46 [PATCH v4 0/7] Add definitions introduced in UEFI 2.8 Oleksiy Yakovlev
2020-05-08 21:46 ` [PATCH v4 1/7] MdePkg: Extend SERIAL_IO with DeviceTypeGuid Oleksiy Yakovlev
2020-05-11 14:46 ` Liming Gao
2020-05-08 21:46 ` [PATCH v4 2/7] BaseTools: REST style formset Oleksiy Yakovlev
2020-05-08 21:46 ` [PATCH v4 3/7] MdePkg: " Oleksiy Yakovlev
2020-05-08 21:46 ` [PATCH v4 4/7] BaseTools: Bootable NVDIMM namespaces Oleksiy Yakovlev
2020-05-08 21:46 ` Oleksiy Yakovlev [this message]
2020-05-08 21:46 ` [PATCH v4 6/7] MdePkg: Add UEFI Spec Revision 2.8 Oleksiy Yakovlev
2020-05-08 21:46 ` [PATCH v4 7/7] MdePkg: UEFI JSON Capsule Support Oleksiy Yakovlev
2020-05-09 2:34 ` [edk2-devel] " Zhiguang Liu
2020-05-11 14:14 ` Liming Gao
[not found] ` <160DFEDDA3DFE660.21511@groups.io>
2020-05-11 14:48 ` Liming Gao
2020-05-11 15:04 ` Oleksiy Yakovlev
2020-05-11 15:10 ` Liming Gao
2020-05-11 14:52 ` [PATCH v4 0/7] Add definitions introduced in UEFI 2.8 Liming Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200508214611.70592-6-oleksiyy@ami.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox