Hi Nico, On 22.06.2020 23:40, Nico Huber wrote: > Hi Michal, > > On 22.06.20 10:29, Michal Zygowski wrote: >> 3. Used VGA option rom to initialize graphics and display the bootsplash >> in coreboot and SeaBIOS as well. What surprised me is that coreboot >> displayed the bootsplash incorrectly (the same color issues as with >> libgfxinit) while SeaBIOS displayed it with the expected colors. > are you 100% sure that it's the same mode? AIUI, SeaBIOS would automati- > cally pick one at runtime, should be visible in the log which. I have set VESA mode 1024x768 16.8M-color (8:8:8) in coreboot when using option ROM (the same resolution and colors as my bootsplash). It seems that SeaBIOS picks different mode then... I will check with the debug output as you suggest. > >> Now the only thing that comes to my mind are the VGA interrupts, because >> SeaBIOS has more complete interrupt services than coreboot. Any comments >> or suggestions on that? I think my next step would be to trace all INT >> 10h and compare the differences and fix it possibly in SeaVGABIOS. > Not sure what you are up to. Libgfxinit sets a specific mode. After that > is set, SeaVGABIOS can't change it, only report the mode info. And if > SeaBIOS' JPEG parser ignores the info, it doesn't matter what SeaVGABIOS > reports. Okay, I see. How do I know which mode is set by libgfxinit? > > Nico > _______________________________________________ > coreboot mailing list -- [email protected] > To unsubscribe send an email to [email protected] Best regards,
-- Michał Żygowski Firmware Engineer https://3mdeb.com | @3mdeb_com _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
