From: Ard Biesheuvel <ard.biesheuvel@...> The ChaosKey driver implements the UEFI driver model, and so it is not guaranteed that any controllers will be attached to this driver unless it is connec

This is not the right fix. The translation offset should be taken into account for these checks

Can you elaborate on this issue? What does /GL do, and why is it throwing this error?

Ah never mind this last point - you did create a cover letter, you just didn't cc me on it :-)

<samer@...> wrote: Hi Samer, Please use my @arm.com email address from now on. Also, for future contributions, could you please include a cover letter? It doesn't have to be elaborate if

Thanks Pushed as b93aa851aab6..4a73a96931a5

Thank you Dandan. Jian, Hao, do you have any comments on this series? If you are too busy to have a closer look immediately, could you please indicate so instead of not responding at all? Thanks.

Jian, Hao, Liming, Michael, It is not always clear to me how you at Intel divide up the maintainer duties between yourselves. Liming and Jiewen have acked this entire series, but they are not the MdeM

There's an additional problem in EDK2 that we never fixed, which is the fact that constructor dependencies are not transitive across library implementations that don't have a constructor themselves. F

<michael.d.kinney@...> wrote: In my opinion, having these intrinsics libraries added via NULL library class resolution was a mistake to begin with. Every component that we build incorporates som

Thanks all Given the fact that the mailmap is only used when explicitly asked for it, adding the entry is not going to make it more likely that unsuspecting contributors will end up using my @arm.com

Reviewed-by: Ard Biesheuvel <ard.biesheuvel@...>

Doesn't the build error go away as well if you simply add FloatUsed.c to all BaseCryptLib flavours if Visual Studio is being used? Something like diff --git a/CryptoPkg/Library/BaseCryptLib/BaseCryptL

<sean.brogan@...> wrote: Even better. Not sure I follow. Which command line are we talking about? Thanks again for the effort. This is going to help tremendously.

<sean.brogan@...> wrote: OK, in that case, please switch to a single -pflash argument from -bios, but pad the QEMU_EFI.fd file to exactly 64 MiB first. I also noticed that you are

<macarl@...> wrote: Yes, so this either belongs in one of the IntrinsicsLibs we have, or in the various Entrypoint libraries we have for PEIMs, DXEs, etc. However, given that we ar

truncate should work on Linux, but I have no idea how to pad an image to a certain size on Windows, and I think the idea was to enable both? In any case, I don't feel as strongly about this as Laszlo

<sean.brogan@...> wrote: You need either -nographic or -serial stdio to get the serial output to go to QEMU's stdout. The latter is probably better, since the former gives you the

(adding Jian and Hao) Thanks for the acks, and apologies for failing to cc the MdeModulePkg maintainers. Jian, Hao, do you have any opinion on this series?

<sean.brogan@...> wrote: OK, so the typical invocation would be qemu-system-aarch64 -M virt -cpu cortex-a57 -m 1024 -net none -nographic -bios .../path/to/QEMU_EFI.fd -hda fat:rw:.