Hi all, I'm trying to write generic EFI code that wires up `printf` to both SIMPLE_TEXT_OUTPUT_PROTOCOL and SERIAL_IO_PROTOCOL when present. However, at least on headless QEMU, doing this in the

Hi all, I'm noticing the following (unspec'd?) behaviour in a shell-run application with the handling of the EFI_SHELL_PARAMETERS_PROTOCOL: * It gets opened with (Handle, AgentHandle,

*at least on headless QEMU

Hi all, I'm trying to write generic EFI code that wires up `printf` to both SIMPLE_TEXT_OUTPUT_PROTOCOL and SERIAL_IO_PROTOCOL when present. However, at least on QEMU, doing this in the naive way

Hi all, I'm noticing the following (unspec'd?) behaviour in a shell-run application with the handling of the EFI_SHELL_PARAMETERS_PROTOCOL: * It gets opened with (Handle, AgentHandle,

Hi y'all, I'm Dionna. I work at Google on Confidential VMs. I've been following the lazy accept patch series for TDVF. Min Xu has seen me fork it in an RFC to AMD's OVMF. What I'm wondering about is

Hi Pranay Kadam, I hope you are fine. I think there is no problem in the implemented code. This status is returned because probably the system you use to validate the implementation does not have the

I don't get this one ... The error message says that there is a file name case mismatch, but I don't see any mismatch. The only thing I see is that there is the "2/" which seems to be to much in the

Hi all, I compiled Vlv2TbltDevicePkg in Windows 10 and operated according to the following URL: https://github.com/tianocore/edk2-platforms/tree/master/Platform/Intel/Vlv2TbltDevicePkg The compiled

When you source edksetup.sh It should put the path to the build command in your $PATH. Here is an example from my Mac: /Volumes/Case/edk2/BaseTools/BinWrappers/PosixLike We can see that is how it

Hi all, I currently work on integrate the edk2 build within a buildsystem. I startet with the docu, made manual builds and wrote me a bash script to automate the steps. Worked all very well. The

Hi Rebecca, thank you that was a very good hint. I now set the PYTHON_COMMAND manually to python3 and the tests working. But the build behaves really odd in that environment, but that's another

Hi all, We are planning to develop UEFI capsule F/W update, and we have seen \FmpDevicePkg\FmpDxe and MdeModulePkg\Application\CapsuleApp in https://github.com/tianocore/edk2. The examples are both

My initial guess would be that for some reason it's trying to use Python 2.x instead of 3.x. -- Rebecca Cran

Hi Team, I'm new to Edk2 platform. I am trying to write simple program to display available Wifi network in Uefi Shell. I'm trying to load gEfiWiFi2ProtocolGuid Protocol using *LocateProtocol*

Hi all, I currently work on integrate the edk2 build within a buildsystem. I startet with the docu, made manual builds and wrote me a bash script to automate the steps. Worked very well till

Hi All, We are working on a hypervisor for x86_64 and we brought up OVMF on our hypervisor. Our hypervisor pass through whole hardware i.e. whole PCI devices starting from root ports to all

Hi Nate, I've submitted my proposal. I ran into some accessibility problems with the "project technologies" part, so there might be random junk there that was added that I couldn't figure out how to

GSoC tip: Try to spread your proposals out. If we don't have enough project slots for you, all your 3 proposals get rejected and your GSoC participation goes out the window. Take a look at our project

Hi Marvin, Ada, Some comments: I don't think the purpose of the dynamic linker is to treat EFI as a complete operating system, but to try to eliminate the static linking that may be needlessly