Hi.
I'm working on implementing UEFI graphics output protocol.
I read the GOP structure to get framebuffer size. It works on VMware, but when I change the resolution, the framebuffer size remains the same (3145728 = 3MiB).
Also, the framebuffer size reported by virtualbox is strangely big.
What is the problem?
Thanks in advance.
UEFI GOP strange behavior
UEFI GOP strange behavior
Last edited by psdgijdfi on Sun Dec 15, 2013 7:58 am, edited 1 time in total.
- Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: UEFI GOP strange behavior
1024x768x4 = 3MB so that's not surprising.
Your base and size printed in the screenshot look like garbage, which means you're probably not getting that information out correctly.
Your base and size printed in the screenshot look like garbage, which means you're probably not getting that information out correctly.
Re: UEFI GOP strange behavior
Actually, the base address is correct (it is hexadecimal). I checked the address by filling the screen.
It is strange because the base address and the framebuffer size information is in the same structure, but only one of them is correct.
And, I meant this strange situation. Even though I changed the resolution to 1920x1080x32, the buffer size remains the same.
It is strange because the base address and the framebuffer size information is in the same structure, but only one of them is correct.
And, I meant this strange situation. Even though I changed the resolution to 1920x1080x32, the buffer size remains the same.
- Attachments
-
- Cap 2013-12-15 22-56-20-181.png (1.53 KiB) Viewed 1968 times
Re: UEFI GOP strange behavior
Maybe it is related to VMware emulator - only its UEFI firmware.
How does it behave on real hardware?
How does it behave on real hardware?
hypervisor-based solutions developer (Intel, AMD)