Hi Paul,
On Wed, 2023-06-07 at 08:09 +0200, Paul Menzel wrote:
Excuse my ignorance. How can all Google boards fail? Aren’t there Intel hardware generations where FSP should not be updated anymore?
I was unclear, sorry. Only the Alderlake boards are affected as it seems.
Also, how much space is missing? Why did FSP grow that much?
I didn't check. As Subrata explained in his comments[1], Google seems to use some sort of customized FSP binary, which is built from an internal repository and also stripped. So I was thinking that might be the reason for that issue, because related ChromeOS flashmaps are optimized for their FSP binary and not for the one from the public Intel repo.
Could a third option be to ask the FSP folks to provide smaller blobs?
I don't know how feasible that is. From recent discussions about releasing FSP binaries, it's even a thing to get *any* FSP binary uploaded on the FSP repo.
However, I think the best compromise is the one I wrote in my second mail, which is to use only the FSP headers from the repo but not the binaries for ChromeOS builds. Customized binaries can still be added by the build system or manually.
For the coreboot CI it shouldn't make much difference (probably not anything?) because it does only build-tests and there are still enough other boards to build-test that part.
Best
Felix