From: "Nhi Pham" <nhi@os.amperecomputing.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"derek.lin2@hpe.com" <derek.lin2@hpe.com>,
"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?
Date: Tue, 6 Apr 2021 12:12:40 +0000 [thread overview]
Message-ID: <DM6PR01MB58494063FED97E908FE58D4F96769@DM6PR01MB5849.prod.exchangelabs.com> (raw)
In-Reply-To: <yJY1.1617169953080992993.UVDo@groups.io>
+ Liming Gao
I'm also interested in the plan for the edk2 in compliance with UEFI 2.8 specification.
-Nhi
________________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Lin, Derek (HPS SW) via groups.io <derek.lin2=hpe.com@groups.io>
Sent: Wednesday, March 31, 2021 12:52 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?
Hi,
In UefiSpec.h, we define the UEFI version 2.7 in system table.
#define EFI_2_70_SYSTEM_TABLE_REVISION ((2 << 16) | (70))
#define EFI_SYSTEM_TABLE_REVISION EFI_2_70_SYSTEM_TABLE_REVISION
#define EFI_SPECIFICATION_VERSION EFI_SYSTEM_TABLE_REVISION
#define EFI_RUNTIME_SERVICES_REVISION EFI_SPECIFICATION_VERSION
In Linux dmesg
[ 0.000000] efi: EFI v2.70 by EDK II
Shall it be updated to v2.8 to align with UEFI spec?
Thanks,
Derek
next prev parent reply other threads:[~2021-04-06 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 5:52 UEFI spec version in system table, shall we update it to 2.8? Lin, Derek (HPS SW)
2021-04-06 12:12 ` Nhi Pham [this message]
2021-04-07 1:37 ` 回复: [edk2-devel] " gaoliming
2023-09-19 17:08 ` [edk2-devel] " karunakar_poosapalli via groups.io
2023-09-19 17:11 ` karunakar_poosapalli via groups.io
2023-09-19 18:18 ` Poosapalli, Karunakar via groups.io
2023-09-19 21:04 ` Michael D Kinney
2023-09-20 4:41 ` Poosapalli, Karunakar via groups.io
2023-09-20 18:59 ` Michael D Kinney
2023-09-20 19:12 ` Poosapalli, Karunakar via groups.io
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=DM6PR01MB58494063FED97E908FE58D4F96769@DM6PR01MB5849.prod.exchangelabs.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