On Fri, Apr 24, 2020 at 4:59 AM Wolfgang Kamp - datakamp <[email protected]> wrote:
> Hello Matt, > > > > Thank you for your response. I see that SeaBIOS still can’t handle the > FMAP structure. > > The pointer depends on the FMAP layout and this is different to chromium > devices. > > For the UP squared board I did not find any other solution than to set > CONFIG_CBFS_LOCATION=0xFFFC0000 and > this is for the upsquared board? looking at the fmap, I'm not sure how you calculated that CBFS location > to patch the 16M coreboot.rom image at address 0x00EBEFFE with 0x44. > > Then SeaBIOS will find the CBFS to load the APL VGA BIOS ROM. > what does patching 0x00EBEFFE with 0x44 do exactly? > > > > > Kind regards, > > Wolfgang > > *Von:* Matt DeVillier [mailto:[email protected]] > *Gesendet:* Donnerstag, 23. April 2020 17:35 > *An:* Wolfgang Kamp - datakamp <[email protected]> > *Cc:* [email protected] > *Betreff:* [coreboot] Re: CBFS pointer problem with SeaBios and Apollo > Lake platform > > > > Apollolake should work with: > > CONFIG_CBFS_LOCATION=0xfffb1000 > > # CONFIG_HARDWARE_IRQ is not set > > > > That's what I use for SeaBIOS as a legacy boot payload on ChromeOS > devices, but the CBFS address will be the same if using upstream coreboot > > > > regards, > Matt > > > > On Thu, Apr 23, 2020 at 3:24 AM Wolfgang Kamp - datakamp < > [email protected]> wrote: > > Hello, > > > > Am I correct that the problem still exists that SeaBios can’t find the > CBFS in apl platform? > > > > Kind regards, > > Wolfgang Kamp > > _______________________________________________ > coreboot mailing list -- [email protected] > To unsubscribe send an email to [email protected] > >
_______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
