Hi Nico!
but it is. It's part of 0xd0000000-0xffffffff.
Beside little SMM and some ACPI, coreboot is no resident firmware like a BIOS that leaves some code to call into. Hence, if you run the VBIOS inside coreboot, it will also leave nothing for the OS to query the framebuffer info.
You have to make use of the framebuffer info coreboot leaves in it's own tables. With the current payload loading (I assume the kernel is wrapped into a SELF binary), this information is not handed over to the kernel (it could, though). So you need a driver that can fetch it.
Have a look into drivers/firmware/google/ in the kernel. GOOGLE_ FRAMEBUFFER_COREBOOT=y should do the trick.
Yes! That's makes sense! I didn't understand how the info was received by the kernel. Now I've patched my kernel with the https://lore.kernel.org/patchwork/cover/875704/ patches and I have framebuffer.
Thanks a lot! Jorge
-
Jorge Fernandez Monteagudo