public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Poosapalli, Karunakar via groups.io" <KarunakarPoosapalli=Dell.com@groups.io>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"POLUDOV, FELIX" <felixp@ami.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] 回复: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?
Date: Wed, 20 Sep 2023 04:41:22 +0000	[thread overview]
Message-ID: <SA1PR19MB5572FF12E6A800CEE26FF22F8BF9A@SA1PR19MB5572.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB4929675D8062D68215D8BDD5D2FAA@CO1PR11MB4929.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 5807 bytes --]

Hi @Kinney, Michael D<mailto:michael.d.kinney@intel.com>,

Thanks for sharing your inputs. Agree with your point.

As latest tianocore edk2 already added some of the interfaces or functionalities implemented from v2.8 by different communities,
Can we say it’s compliant with v2.8? but as there is no analysis done to see whether all updates from 2.8 is implemented or not we can’t say it’s fully 2.8 Supported ?

Thanks & Regards
Karunakar Poosapalli
Firmware Principal Engineer, Client BIOS
Customer BIOS | Dell Core BIOS
CPG Software Engineering | Dell Technologies
Mobile +91 9951902957
Karunakar_poosapalli@Dell.Com<mailto:Karunakar_poosapalli@Dell.Com>



Internal Use - Confidential
From: Kinney, Michael D <michael.d.kinney@intel.com>
Sent: Wednesday, September 20, 2023 2:34 AM
To: devel@edk2.groups.io; Poosapalli, Karunakar; POLUDOV, FELIX; Yao, Jiewen
Cc: Kinney, Michael D
Subject: RE: [edk2-devel] 回复: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?


[EXTERNAL EMAIL]
I do not think anyone has done the complete analysis since UEFI 2.7.  Some updates from newer specs
have been added as needed by different community members.

Unless there are dedicated tasks to review and verify that every spec change has been added to edk2, the version can not be updated.

Mike

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Poosapalli, Karunakar via groups.io
Sent: Tuesday, September 19, 2023 11:18 AM
To: Poosapalli, Karunakar <KarunakarPoosapalli@Dell.com<mailto:KarunakarPoosapalli@Dell.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; POLUDOV, FELIX <felixp@ami.com<mailto:felixp@ami.com>>; Yao, Jiewen <jiewen.yao@intel.com<mailto:jiewen.yao@intel.com>>
Subject: Re: [edk2-devel] 回复: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?

Hi All,

Can you please share your thoughts if any idea in EDK2 compliance with UEFI 2.8 Support ?

From UEFI sources and latest edk2 master branch is still at 2.7. Same for latest stable tag edk2-stable202308.
https://github.com/tianocore/edk2.git [github.com]<https://urldefense.com/v3/__https:/github.com/tianocore/edk2.git__;!!LpKI!nIohUbt0OghPJnCKOpCtgOh1X26Ds1hTOXDuhgvA7ameCb6qMli7Zw8P-z0ruFYDjM8sum-VJAV7sB8_8FzbvKH80JAhH-G8$>
#define EFI_SYSTEM_TABLE_REVISION       EFI_2_70_SYSTEM_TABLE_REVISION
#define EFI_SPECIFICATION_VERSION       EFI_SYSTEM_TABLE_REVISION


But we could see some of the features from 2.8 is already available and UEFI 2.9 spec also released but system table in edk2 is still pointing to 2.7.

Curious to know, Whether latest edk2 is not fully compliance with 2.8 or only system table update is missing for 2.8

Thanks & Regards
Karunakar Poosapalli
Firmware Principal Engineer, Client BIOS
Customer BIOS | Dell Core BIOS
CPG Software Engineering | Dell Technologies
Mobile +91 9951902957
Karunakar_poosapalli@Dell.Com<mailto:Karunakar_poosapalli@Dell.Com>

From: karunakar_poosapalli via groups.io <karunakar_poosapalli=dell.com@groups.io<mailto:karunakar_poosapalli=dell.com@groups.io>>
Sent: Tuesday, September 19, 2023 10:41 PM
To: Poosapalli, Karunakar; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] 回复: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?


[EXTERNAL EMAIL]

In latest tianocore edk2 (https://github.com/tianocore/edk2 [github.com]<https://urldefense.com/v3/__https:/github.com/tianocore/edk2__;!!LpKI!mQ_BG3pFqn4l_WXu4-SMapIb2kzSZmeFEwZ9PNGLNx6j_YdYF6DUWQBuLZwoJhMzMQIiKG1dMBmDJH6eqgKzHbK-JfJWjjqXU1bQ$> ), we can see System table is still pointing to 2.70 Version(EFI_2_70_SYSTEM_TABLE_REVISION)

https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Uefi/UefiSpec.h [github.com]<https://urldefense.com/v3/__https:/github.com/tianocore/edk2/blob/master/MdePkg/Include/Uefi/UefiSpec.h__;!!LpKI!mQ_BG3pFqn4l_WXu4-SMapIb2kzSZmeFEwZ9PNGLNx6j_YdYF6DUWQBuLZwoJhMzMQIiKG1dMBmDJH6eqgKzHbK-JfJWjvHlQENb$>

//

// EFI Runtime Services Table

//

#define EFI_SYSTEM_TABLE_SIGNATURE      SIGNATURE_64 ('I','B','I',' ','S','Y','S','T')

#define EFI_2_80_SYSTEM_TABLE_REVISION  ((2 << 16) | (80))

#define EFI_2_70_SYSTEM_TABLE_REVISION  ((2 << 16) | (70))

#define EFI_2_60_SYSTEM_TABLE_REVISION  ((2 << 16) | (60))

#define EFI_2_50_SYSTEM_TABLE_REVISION  ((2 << 16) | (50))

#define EFI_2_40_SYSTEM_TABLE_REVISION  ((2 << 16) | (40))

#define EFI_2_31_SYSTEM_TABLE_REVISION  ((2 << 16) | (31))

#define EFI_2_30_SYSTEM_TABLE_REVISION  ((2 << 16) | (30))

#define EFI_2_20_SYSTEM_TABLE_REVISION  ((2 << 16) | (20))

#define EFI_2_10_SYSTEM_TABLE_REVISION  ((2 << 16) | (10))

#define EFI_2_00_SYSTEM_TABLE_REVISION  ((2 << 16) | (00))

#define EFI_1_10_SYSTEM_TABLE_REVISION  ((1 << 16) | (10))

#define EFI_1_02_SYSTEM_TABLE_REVISION  ((1 << 16) | (02))

#define EFI_SYSTEM_TABLE_REVISION       EFI_2_70_SYSTEM_TABLE_REVISION

#define EFI_SPECIFICATION_VERSION       EFI_SYSTEM_TABLE_REVISION



#define EFI_RUNTIME_SERVICES_SIGNATURE  SIGNATURE_64 ('R','U','N','T','S','E','R','V')

#define EFI_RUNTIME_SERVICES_REVISION   EFI_SPECIFICATION_VERSION



Does it mean latest tianocore is still not UEFI 2.8 version support or it supports 2.8 functionalities but the table version number is not yet updated?


Internal Use - Confidential



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108912): https://edk2.groups.io/g/devel/message/108912
Mute This Topic: https://groups.io/mt/81906348/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 19403 bytes --]

  reply	other threads:[~2023-09-20 13:59 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 ` [edk2-devel] " Nhi Pham
2021-04-07  1:37   ` 回复: " 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 [this message]
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=SA1PR19MB5572FF12E6A800CEE26FF22F8BF9A@SA1PR19MB5572.namprd19.prod.outlook.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