[...] I thought it could be a register on the new CPU hotplug controller that we're going to need anyway (if I understand correctly, at least). But: Yes, that should work. In fact, I had

A special case of your question is covered, at the moment, as follows ("give users an indication of the image validation failure"): - When a UEFI boot option is rejected due to secure boot

Hello, I have a question about user error reporting during SecureBoot image validation. From my testing with OVMF/Secureboot, when an image to be loaded fails validation (i.e. due to missing or

I've posted this to the largest forum of blind visually impaired people I know of to date and have gotten some excellent feedback from them. I also provided in that post a link to this discussion.

Hi Ethin and all As Leif mentioned, my mastering thesys was the implementation of a reference code so a driver for audio at pre-OS would be possible, eliminating the first barrier for the creation of

Woops, I just realized while reading my message after I'd sent it that I had linked to the wrong document. The priority system is outlined over here (https://freebsoft.org/doc/speechd/ssip.html#Top).

While conquering refreshable braille displays would be nice, I think we should take it in stages. (Some blind people would want this in along with the accessibility subsystems, however I do not

Hi Ethin, Apologies for the delay in responding - I personally don't tend to read the RFC list (and I know that applies to some other developers who have now subscribed). So, first of all, I need to

Laszlo Ersek <lersek@...> wrote: It looks like fwcfg smi feature negotiation isn't reusable in this case. I'd prefer not to add another device just for another SMI

Sorry, there's a typo above: I pasted "smbase-blackhole" twice. The second instance was meant to be "smbase-window". I checked all instances of both regions in the info mtree output, I just fumbled

Hi Igor, Tying the [0x30000+128K) lockdown to the broadcast SMI negotiation is a simplification for QEMU, but it is a complication for OVMF. (This QEMU patch ties those things together in effect

Another specific question: What's the meaning of "F1 and F2 don't work in UEFI Shell"? That sounds like a bug in Terminal driver.

Zhichao, Can you please summarize what terminal types are supported by EDKII Terminal driver today and what you are going to add through this RFC? For the newly added terminal types, where is the

Liming, All the three types will be introduced. By the way, fix one typo 'F4' for VT400 map key should be 'ESC [ 1 4 ~'. Thanks, Zhichao Sent: Friday, September 6, 2019 3:51 PM To: Gao, Zhichao

Zhichao: One clarification. What terminal type will be introduced? Xterm, VT400 and Linux? Thanks Liming Sent: Friday, September 06, 2019 12:56 PM To: rfc@edk2.groups.io Cc: devel@edk2.groups.io;

Hi everyone, Putty is a popular terminal console software in windows and it support various types of terminal keyboard type. I would like to add most of the type support. Here is the key map info.

lpc already has SMI negotiation feature, extend it by adding optin ICH9_LPC_SMI_F_LOCKED_SMBASE_BIT to supported features. Writing this bit into "etc/smi/requested-features" fw_cfg file, tells QEMU

Laszlo Ersek <lersek@...> wrote: I guess we at point where patch is better then words, I'll send one as reply here shortly. I've just implemented subset of above (opened, closed+locked). I