Nickle: So, your proposal is to let HII driver call new API to disable or enable Hotkey on its page. There are still some issues here. 1. UEFI option rom driver is the independent driver. It refers

Sure, I'm not pushing for that; just if it were possible with VFR out of the box, it would be a good choice. Thanks Laszlo

UEFI driver write guide 12.6.1 Minimize callbacks section defines the guide line. https://github.com/tianocore/tianocore.github.io/wiki/UEFI-Driver-Writer%27s-Guide But, some HII drivers still like

Thanks for your feedback, Laszlo. I like the idea to support hotkey from VFR level. However, I checked the UEFI driver writer guide and I do not see anything about HII hotkey. In terms of hotkey

I agree with the problem statement. I've noticed this too, and found it confusing. I wonder if there are HII guidelines or best known practices to deal with it -- I assume that one desirable solution

Hi All, I am having trouble to disable hotkey support in HII browser with existing interface. I am wondering if we could have new interface to disable hotkey support in form browser extension2

I'm honestly surprised that the iSCSI RFC has not been updated to drop CHAP-MD5 at this point. I realize that is probably a bigger effort but it seems like something the industry should do. I agree

When the RPi UEFI FW dropped iSCSI (because it was removed from NetworkDefines.dsc.inc), we got multiple users complaining since they had existing use cases that depended on that. See for instance the

Lazlo, This sounds like the right direction to me. My 2C, Simo. -- Simo Sorce RHEL Crypto Team Red Hat, Inc

Hi, RFC 7143 requires CHAP-MD5 as a mandatory option offered by an iscsi client (initiator). At the same time, edk2 has deprecated MD5 in general, as a cryptographically weak hash

[...] [...] One more thought, regarding fw_cfg-controlled DebugLib instances: - fw_cfg access is unavailable in ArmVirtQemu before the DXE phase, - on both Ovmf and ArmVirtQemu, the QemuFwCfgLib

This is generally not a bad idea; we implemented a very simple version of it (for setting dynamic boolean PCDs from fw_cfg) in QemuFwCfgSimpleParserLib. See commit range

Thanks Laszlo! This is very helpful. From a user perspective, I was thinking perhaps OVMF/AAVMF could support a generic config file (on the host). Linux users are all too familiar with config files.

two other examples (not an exhaustive list by far), for fw_cfg-based configuration: - The cipher suites, and the CA certificates, that are to be trusted by the firmware for UEFI HTTPS Boot (TLS), are

Sorry, can't give you anything. The general approach is: - UEFI variables are used for configuring firmware aspects, usually the same as on physical platforms (meaning volatile/non-volatile, boot

Hello. What methods currently exist to configure OVMF/AAVMF dynamically at runtime? For example, modify the preferred Language, set boot menu timeout or enable SecureBoot. To my knowledge, the

Yeah, I have the same problem with cscope. Too many matches for one symbol. wrote: -- Best, Daniel

Ah, ctags! Haven't used that for years. I'll give it a shot. Thanks for sharing. -- Best, Daniel

I use cscope, and the "rscope" extension to emacs. I use a script to collect source files and include directories from the source tree to generate the cscope.files file. That works, but isn't smart