On Wed, Nov 01, 2017 at 03:28:45PM +0000, Scheithauer, Mario wrote:
When you say "a hack in coreboot.rom", are you referring to the CONFIG_CBFS_LOCATION=0xfff9f000 seabios setting or was some additional change necessary?
-Kevin
Hi Kevin,
Yes, we had to make another adjustment. I think SeaBios is expecting a pointer at this position to the beginning of the CBFS. But coreboot doesn't enter anything there, because everything works over the FMAP. But it may also be that we are still doing something wrong.
-> CONFIG_CBFS_LOCATION = top of memory (0xFFFFFFFF) - SPI Flash size + CBFS end position (FMAP) + DEVICE_EXTENSION size (FMAP) + UNUSED_HOLE size (FMAP) -> At this position there is only 0xffffffff and SeaBios has a problem with that. -> 0xff401838 = top of memory (0xFFFFFFFF) - SPI Flash size + DEVICE_EXTENSION size (FMAP) + UNUSED_HOLE size (FMAP) + CBFS master header size (0x38) -> It all depends on the FMAP -> If we put into the pointer there, SeaBios will also find the CBFS and everything is fine
Regards, Mario