On 08/16/13 06:41, Hamel, Lee M wrote:
> I have a DEBUG macro call DEBUG((DEBUG_INFO,
>
> In a DEBUG build, the string appears in the serial console, while in
> RELEASE build it does not.
>
> Does anyone know why this is the case?
Well at least in case of OVMF, the OvmfPkg/OvmfPkgX64.dsc
I have a DEBUG macro call DEBUG((DEBUG_INFO,
In a DEBUG build, the string appears in the serial console, while in RELEASE
build it does not.
Does anyone know why this is the case?
PcdDebugPropertyMask and PcdDebugPrintErrorLevel
are set correctly, otherwise I shouldn't see the string
Have you committed it into BaseTools trunk? If yes, I will sync it together. If
no, I want to know what impact for this patch. Does it impact all GCC build or
only ARM GCC build?
From: Olivier Martin [mailto:olivier.mar...@arm.com]
Sent: Thursday, August 15, 2013 5:14 PM
To: edk2-devel@lists.so
Hi All,
I'd like to drive keyboard/mouse devices and add the
WaitForInput of EFI_SIMPLE_POINTER_PROTOCOL into gBS->WaitForEvent(). So I
wrote a sample code below.
I found if I keep the "*Print(L"\n");*" in my code, both RelativeMovementX
and RelativeMovementY could be printed.
But once removing "*
I sent a patch on June 11th that fixes the calculation of the PE/COFF header
attribute 'BaseOfCode'. And a second version on July 16th taking in account
the comments after the review.
Do you think my fix could be integrated to this BaseTools sync?
Thanks,
Olivier
From: Gao, Liming [mai
