Dear Felix,
Thank you for bringing that up on the list.
Am 07.06.23 um 01:23 schrieb Felix Singer:
Another idea...
We could switch the default value of FSP_USE_REPO for ChromeOS builds so that it's disabled by default. It seems the header files are still taken from the repo then.
How does that sound?
On Tue, 2023-06-06 at 23:12 +0000, Felix Singer wrote:
Hello,
Moving forward the submodule pointers of the microcode [1] or Intel FSP [2][3] repository will make the Google boards (ChromeOS builds?) failing because the FSP does not fit into their flash region anymore.
How do we deal with that issue? I think there are two options:
* Make the flash regions bigger * Disable ChromeOS builds for upstream
Excuse my ignorance. How can all Google boards fail? Aren’t there Intel hardware generations where FSP should not be updated anymore?
Also, how much space is missing? Why did FSP grow that much?
Could a third option be to ask the FSP folks to provide smaller blobs?
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/75631 [2] https://review.coreboot.org/c/coreboot/+/74242 [3] https://review.coreboot.org/c/coreboot/+/74442