From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Alex Hung <alex.hung@canonical.com>,
Colin Ian King <colin.king@canonical.com>,
Ivan Hu <ivan.hu@canonical.com>,
linux-efi <linux-efi@vger.kernel.org>
Subject: Re: fwts: RuntimeServicesSupported variable
Date: Wed, 14 Oct 2020 19:45:09 +0200 [thread overview]
Message-ID: <4b74c0b7-7126-2829-29d3-ef5131c52b73@gmx.de> (raw)
In-Reply-To: <4898db16-7f9b-2efc-a5ae-356461d790b8@gmx.de>
On 14.10.20 19:31, Heinrich Schuchardt wrote:
> Dear all,
>
> the fwts fails on U-Boot due to testing for a non-existent
> RuntimeServicesSupported variable.
>
> If you look at the UEFI specification 2.8 (Errata B) [1] you will
> discover in the change log:
>
> 2.8 A2049
> RuntimeServicesSupported EFI variable should be a config table
> February 2020
>
> Please, read the configuration table to determine if a runtime service
> is available on UEFI 2.8 systems.
>
> On lower UEFI firmware version neither the variable nor the table exists.
>
> Best regards
>
> Heinrich
>
> [1] UEFI Specification Version 2.8 (Errata B) (released June 2020),
> https://uefi.org/sites/default/files/resources/UEFI%20Spec%202.8B%20May%202020.pdf
>
Hello Ard,
what is your idea how the EFI_RT_PROPERTIES_TABLE shall be exposed to
the efi_test driver?
Will the EFI runtime wrapper simply return EFI_UNSUPPORTED if the
function is not marked as supported in the table? Or will the
configuration table itself be make available?
Best regards
Heinrich
next parent reply other threads:[~2020-10-14 17:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4898db16-7f9b-2efc-a5ae-356461d790b8@gmx.de>
2020-10-14 17:45 ` Heinrich Schuchardt [this message]
2020-10-14 17:58 ` fwts: RuntimeServicesSupported variable Ard Biesheuvel
2020-10-14 18:41 ` Heinrich Schuchardt
2020-10-19 9:31 ` Ard Biesheuvel
2020-10-19 10:00 ` Heinrich Schuchardt
2020-10-19 10:03 ` Ard Biesheuvel
2020-10-19 11:00 ` Heinrich Schuchardt
2020-10-19 11:01 ` Ard Biesheuvel
2020-10-19 11:25 ` Heinrich Schuchardt
2020-10-20 6:20 ` ivanhu
2020-10-20 6:46 ` Ard Biesheuvel
2020-10-20 7:22 ` ivanhu
2020-11-24 13:05 ` Heinrich Schuchardt
2020-11-24 13:10 ` Ard Biesheuvel
2020-11-24 14:08 ` Heinrich Schuchardt
2020-11-24 14:13 ` Ard Biesheuvel
2020-10-19 11:22 ` Heinrich Schuchardt
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-all 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=4b74c0b7-7126-2829-29d3-ef5131c52b73@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=alex.hung@canonical.com \
--cc=ardb@kernel.org \
--cc=colin.king@canonical.com \
--cc=ivan.hu@canonical.com \
--cc=linux-efi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).