Patch Set 1:

All the mainboard that use PI Hudson also use binaryPI release builds from 3rdparty blobs. Is there a known and open method to rebase the AGESA binary? Otherwise, I do not see any sense of moving the AGESA binary location to 0xFFF00000

I was never aware of a method for rebasing an AGESA image (i.e. similar to Intel's BCT) or a way to relocate it during the coreboot build process.

View Change

To view, visit change 31076. To unsubscribe, or for help writing mail filters, visit settings.