On Wed, Aug 21, 2019 at 7:52 PM Raul Rangel email@example.com wrote:
You can grep for commits containing b:65442212 or b:111610455 to see the work required to remove AGESA from bootblock.
Some of that seems very SoC or hardware specific. I think we will go ahead with a bootblock that does nothing else but sets up CAR and finds a romstage.elf to jump into. At this time verstage is not a requirement so we'll just ignore any LPC or SPI PAD configurations TPM might need.
In general, changes from amd/stoneyridge do not apply to previous binaryPI builds. A different set of modifications to StoneyPI were made in comparison to the changes that SAGE had previously made to MullinsPI, KaveriPI and CarrizoPI. Also AMD rolled out a custom PSP firmware build for Chromebooks? So it is possible the implementation of AGESAv5 API we have for amd/stoneyridge is only compatible with the modified StoneyPI source tree and the modified PSP firmware. And the PSP mailbox APIs are not exactly the same across different SoCs either.
Regards, Kyösti Mälkki