@retval EFI_SUCCESS The requested number of bytes was allocated.\r
@retval EFI_OUT_OF_RESOURCES The pool requested could not be allocated.\r
@retval EFI_UNSUPPORTED In runtime.\r
- @Note: Inconsistent with specification here:\r
+ @note: Inconsistent with specification here:\r
In Framework Spec, This definition is naming EFI_SMM_ALLOCATE_POOL. However, \r
To avoid the naming conflict, the definition is renamed.\r
**/\r
@retval EFI_SUCCESS The memory was returned to the system.\r
@retval EFI_INVALID_PARAMETER Buffer was invalid.\r
@retval EFI_UNSUPPORTED In runtime.\r
- @Note: Inconsistent with specification here:\r
+ @note: Inconsistent with specification here:\r
In Framework Spec, This definition is naming EFI_SMM_FREE_POOL However, \r
To avoid the naming conflict, the definition is renamed.\r
**/\r
@retval EFI_NOT_FOUND The requested pages could not be found.\r
@retval EFI_INVALID_PARAMETER Type is not AllocateAnyPages or AllocateMaxAddress\r
or AllocateAddress. Or MemoryType is in the range EfiMaxMemoryType..0x7FFFFFFF.\r
- @Note: Inconsistent with specification here:\r
+ @note: Inconsistent with specification here:\r
In Framework Spec, This definition is naming EFI_SMM_ALLOCATE_PAGES However, \r
To avoid the naming conflict, the definition is renamed.\r
**/\r
@retval EFI_INVALID_PARAMETER Memory is not a page-aligned address or NumberOfPages is invalid.\r
@retval EFI_NOT_FOUND The requested memory pages were not allocated with SmmAllocatePages().\r
\r
- @Note: Inconsistent with specification here:\r
+ @note: Inconsistent with specification here:\r
In Framework Spec, This definition is naming EFI_SMM_FREE_PAGES However, \r
To avoid the naming conflict, the definition is renamed.\r
**/\r
@retval EFI_INVALID_PARAMETER The CPU requested is not available on this SMI invocation.\r
@retval EFI_INVALID_PARAMETER The CPU cannot support an additional service invocation.\r
\r
- @Note: Inconsistent with specification here:\r
+ @note: Inconsistent with specification here:\r
In Framework Spec, No this definition. This method is introduced in PI1.0 spec for \r
implementation needed.\r
\r
// is defined in MdePkg/Protocol/GraphicsOutput.h\r
//\r
#include <Protocol/GraphicsOutput.h>\r
-\r
+//\r
+// In UEFI2.1 spec, there is a same data type named EFI_GRAPHICS_OUTPUT_BLT_PIXEL.\r
+// To define this data type only for backward compatibility. \r
+//\r
+typedef struct {\r
+ UINT8 Blue;\r
+ UINT8 Green;\r
+ UINT8 Red;\r
+ UINT8 Reserved;\r
+} EFI_UGA_PIXEL\r
//\r
// In both EDK and EDK II, incompatbile change is done to Framework HII protocol. \r
// This change should cause a change of GUID in both of code and HII spec. But we \r
0x5542cce1, 0xdf5c, 0x4d1b, { 0xab, 0xca, 0x36, 0x4f, 0x77, 0xd3, 0x99, 0xfb } \\r
}\r
\r
-// BugBug:\r
-//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r
-// If UGA goes away we need to put this some place. I'm not sure where?\r
-//\r
-//typedef struct {\r
-// UINT8 Blue;\r
-// UINT8 Green;\r
-// UINT8 Red;\r
-// UINT8 Reserved;\r
-//} EFI_UGA_PIXEL;\r
-\r
-//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r
-//\r
\r
typedef UINT16 STRING_REF;\r
typedef UINT32 RELOFST;\r
\r
@retval EFI_SUCCESS It worked.\r
@retval EFI_NOT_FOUND A glyph for a character was not found.\r
-\r
+ @note: Inconsistent with specification here:\r
+ In Framework Spec,HII spec 0.92. The type of 3rd, 4th and 8th parameter is EFI_UGA_PIXEL.\r
+ Here the definition use the EFI_GRAPHICS_OUTPUT_BLT_PIXEL which defined in UEFI2.1 spec\r
**/\r
typedef\r
EFI_STATUS\r