From: "Tim Lewis via groups.io" <tim.lewis=insyde.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] Bitfield var stores and compatibility
Date: Mon, 5 May 2025 17:33:18 +0000 [thread overview]
Message-ID: <TYSPR02MB8447A8172CF62FEACDDB46ED838E2@TYSPR02MB8447.apcprd02.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]
Can we discuss the EDK2 extension to allow bitfield varstores that is not a compatible changes and, in fact, inhibits the UEFI spec from going in certain directions.
Back in 2017, the EDK2 version of the browser added the EDKII_IFR_BIT_VARSTORE_GUID, which, if present, tells the EDK2 form browser to change the meaning of almost all fields related to storage, including VarOffset, size and uses the bottom 6 bits of the Flags field in the question header.
However, these changes are not found in the UEFI specifications. As a result, any "compliant" browser cannot correctly deal with questions that require these extensions. It is not problem if the form is built at the same time as the rest of the firmware, but 3rd party drivers, UEFI applications and option ROMs cannot assume that this support is present.
We have run into this when thinking about creating a proposal for the UEFI specification and found that adding bits in the Flags field doesn't work for checkbox, one-of and numeric questions because those bits are already co-opted by this EDK2 extension and this EDK2 extension is being used by some 3rd party drivers.
How did this ever get approved by the maintainers?
Thanks,
Tim
[cid:image002.png@01DBBDA9.1F3EE5A0]
Tim Lewis
CTO
Insyde Software
Phone: +1-916-813-6838
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121305): https://edk2.groups.io/g/devel/message/121305
Mute This Topic: https://groups.io/mt/112634275/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #1.2: Type: text/html, Size: 8738 bytes --]
[-- Attachment #2: image001.gif --]
[-- Type: image/gif, Size: 3386 bytes --]
[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 5805 bytes --]
reply other threads:[~2025-05-05 17:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=TYSPR02MB8447A8172CF62FEACDDB46ED838E2@TYSPR02MB8447.apcprd02.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