public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "karunakar_poosapalli via groups.io" <karunakar_poosapalli=dell.com@groups.io>
To: karunakar_poosapalli@dell.com,devel@edk2.groups.io
Subject: Re: [edk2-devel] 回复: [edk2-devel] UEFI spec version in system table, shall we update it to 2.8?
Date: Tue, 19 Sep 2023 10:11:24 -0700	[thread overview]
Message-ID: <10392.1695143484764785480@groups.io> (raw)
In-Reply-To: <17815.1695143324467068704@groups.io>

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

In latest tianocore edk2 ( https://github.com/tianocore/edk2 ), 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

//

// 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?


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108853): https://edk2.groups.io/g/devel/message/108853
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: 5667 bytes --]

  reply	other threads:[~2023-09-19 17:11 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 [this message]
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=10392.1695143484764785480@groups.io \
    --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