Date
1 - 3 of 3
[PATCH] Update Graphics Info Hob FrameBufferSize Based on UEFI Spec 2.0
|
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3793
Basede on UEFI Spec 2.0 section 17.7.1 structure EFI_GRAPHICS_OUTPUT_PROTOCOL_MODE say FrameBufferSize should be size of UINTN, in MdePkg\Include\Guid\GraphicsInfoHob.h EFI_PEI_GRAPHICS_INFO_HOB FrameBufferSize is UINT32, UefiPayloadPkg\GraphicsOutputDxe\GraphicsOutput.c MdeModulePkg\Universal\Console\GraphicsOutputDxe\GraphicsOutput.c Private->GraphicsOutputMode.FrameBufferSize = \ GraphicsInfo->FrameBufferSize; UINT32 value is getting assigned to UINTN, in X64 build compiler will throw possible loss of data error. so update the EFI_PEI_GRAPHICS_INFO_HOB based on UEFI Spec 2.0 Signed-off-by: Ashraf Ali S <ashraf.ali.s@...> Cc: Rangasai V Chaganty <rangasai.v.chaganty@...> Cc: Digant H Solanki <digant.h.solanki@...> Cc: Sangeetha V <sangeetha.v@...> Cc: Ray Ni <ray.ni@...> Cc: Michael D Kinney <michael.d.kinney@...> Cc: Liming Gao <gaoliming@...> Cc: Zhiguang Liu <zhiguang.liu@...> --- MdePkg/Include/Guid/GraphicsInfoHob.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MdePkg/Include/Guid/GraphicsInfoHob.h b/MdePkg/Include/Guid/GraphicsInfoHob.h index 237911e63a..92bd907f20 100644 --- a/MdePkg/Include/Guid/GraphicsInfoHob.h +++ b/MdePkg/Include/Guid/GraphicsInfoHob.h @@ -26,7 +26,7 @@ typedef struct { EFI_PHYSICAL_ADDRESS FrameBufferBase; - UINT32 FrameBufferSize; + UINTN FrameBufferSize; EFI_GRAPHICS_OUTPUT_MODE_INFORMATION GraphicsMode; } EFI_PEI_GRAPHICS_INFO_HOB; -- 2.30.2.windows.1 |
|
|
|
Michael D Kinney
Hi Ashraf,
toggle quoted message
Show quoted text
HOBs must never use UINTN or pointer fields. HOBs must always be the same size no matter what CPU or CPU mode the structure is compiler for. This is also a non-backwards compatible change to a HOB structure. For the case where the GraphicsOutputProtocol is build for X64 and uses this HOB as input, the UINT32 value from the HOB can be cast to UINTN for the protocol. Given that the cast is from UINT32 -> UINT32 for IA32 builds and UINT32->UINT64 for X64 builds, I do not see any case where there would be possible loss of data. The cast would always be to a type that is the same size or larger. Can you please verify the compiler error you observed? Thanks, Mike -----Original Message----- |
|
|
|
Hi., Michael
toggle quoted message
Show quoted text
The issue was coming due to assign UINTN to UINT32 (warning C4244: '=': conversion from 'UINTN' to 'UINT32', possible loss of data) I will fix this in my code instead of changing in the EDK2. Closing this bug, Thanks Happy New Year 😊 Regards, Ashraf Ali S Intel Technology India Pvt. Ltd. -----Original Message-----
From: Kinney, Michael D <michael.d.kinney@...> Sent: Monday, January 3, 2022 1:55 AM To: S, Ashraf Ali <ashraf.ali.s@...>; devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@...> Cc: Chaganty, Rangasai V <rangasai.v.chaganty@...>; Solanki, Digant H <digant.h.solanki@...>; V, Sangeetha <sangeetha.v@...>; Ni, Ray <ray.ni@...>; Gao, Liming <gaoliming@...>; Liu, Zhiguang <zhiguang.liu@...> Subject: RE: [PATCH] Update Graphics Info Hob FrameBufferSize Based on UEFI Spec 2.0 Hi Ashraf, HOBs must never use UINTN or pointer fields. HOBs must always be the same size no matter what CPU or CPU mode the structure is compiler for. This is also a non-backwards compatible change to a HOB structure. For the case where the GraphicsOutputProtocol is build for X64 and uses this HOB as input, the UINT32 value from the HOB can be cast to UINTN for the protocol. Given that the cast is from UINT32 -> UINT32 for IA32 builds and UINT32->UINT64 for X64 builds, I do not see any case where there would be possible loss of data. The cast would always be to a type that is the same size or larger. Can you please verify the compiler error you observed? Thanks, Mike -----Original Message----- |
|
|