Mike, That is what I ended up doing, but it required overriding every PEIM and PEI Core. Seemed kind of excessive. I think people cheat and use IA32 vs X64 to mean PEI vs. DXE on X64 platforms. Thanks

I’m trying to have a different platform policy for PcdDebugPropertyMask in PEI and DXE. I can’t figure out how to do without overriding every PEIM that I build? My PEI and DXE has the same arch so I c

So I’m messing about in a DefaultExceptionHandler() (like [1]) that is called from CommonCExceptionHandler() [2]. What I notice is the faulting address is special cased. So the stack walking code has

Ray, ProcessSystemContext may not be needed… My thinking was if you pass ProcessSystemContext == TRUE there is some implied processing of the SystemContext by the PanicLib. If you pass FALSE then ther

Mike Kinney mentioned at the TianoCore Stewards Meeting that it might be a good idea to add a panic API to the edk2. I agree. Some background…. While ASSERT is a powerful tool I think we have a tenden

Mike, That sounds like the right fox to me. Disable the warning.

In general is it bad to assume what the disk node is going to look like. You have know idea what the transport is going to look like and how that transport enumerates disks. As I mentioned the BlockIO

I see the text in table 10-49 but I don’t know of any code that makes a node for the entire disk partition. If you look at the BlockIO protocol the partitions that are created due to the partitions on

Very cool idea but ….. 1) We don’t always use the systems native compiler and sometimes we use a cross compiler so making assumptions about system libs is not always valid. On a Mac with Xcode clang I

https://www.suse.com/c/revolutionizing-arm-technology-x86_64-option-rom-aarch64/ https://www.workofard.com/2020/12/aarch64-option-roms-for-amd-gpus/

Given it is undefined behavior and the compiler is behaving correctly I think it is better to write correct C code and use volatile if you mean to use a NULL pointer. Not to mention I worked hard to g

I was playing around with getting Xcode to compile AArch64 code and I hit an interesting compatibility issue. The assembler line continuation token for GCC (;) is a comment for the Xcode clang assembl

Jacek, Since you are not subscribed to the mailing list this mail got sent to moderation…. Sometimes syntax errors in your build config files can crash the tools. This looks like a PCD value in a DSC

Michael, I’m still researching how to install the dependent tools so I can follow the instructions. Do the stuart_* commands come from the EDKII Tools PIP? I think I can get NuGet from brew, but the 1

OK thanks. I can test on Linux and macOS. Maybe I’ll try using VS Code as my editor now…. Thanks, Andrew Fish

Mike, How is this documented outside of this patch set? Is there a Tianocore Wiki page on configuring uncrustify? Does that Readme.rst link to that? Thanks, Andrew Fish

Bibo, You are finding implementation bugs. Please file Bugzillas when you see these bugs. For X64 (x86-64) the reset vector is 0xFFFFFFF0 (just below 4 GiB) so the ROM (usually a NOR FLASH) is always

Me too.

I’d be OK if to start it just listed the various options, if making the button smart is too much work. Thanks, Andrew Fish

Yes sounds good. Thanks, Andrew Fish