AMD Bald Eagle: Add binary PI vendorcode files

Hardware / Coreboot - Bruce Griffith [se-eng.com] - 27 January 2015 08:02 UTC

Add all of the PI source that will remain part of coreboot to build with a binary AGESA PI BLOB. This includes the gcc makefiles, some Kconfig, and the AGESA standard library functions.

Change vendorcode Makefile and Kconfig so that they can compile AMD library files and use headers from outside the coreboot/src tree.

This fix changes the makefile so that the AGESA dispatcher is built using its own rules rather than generic library generation rules in coreboot/Makefile and coreboot/Makefile.inc. The AGESA source files are initially copied from whereever they live into coreboot/build/agesa. They are compiled from there. The binary PI directory now has a mandatory structure that places the AGESA BLOB into the same directory as the support headers. These will nominally be placed in the amd directory in SageBIOS or the 3rdparty directory in coreboot.org.

Change-Id: I56788cd197159939b64c7d16c1d32418f8cc2197

98e8253 AMD Bald Eagle: Add binary PI vendorcode files
src/vendorcode/amd/pi/00630F01/Kconfig | 55 ++
src/vendorcode/amd/pi/00630F01/Lib/amdlib.c | 1417 +++++++++++++++++++++++++++
src/vendorcode/amd/pi/00630F01/Lib/amdlib.h | 393 ++++++++
src/vendorcode/amd/pi/00630F01/Makefile.inc | 122 +++
src/vendorcode/amd/pi/Kconfig | 1 +
src/vendorcode/amd/pi/Makefile.inc | 1 +
6 files changed, 1989 insertions(+)

Upstream: review.coreboot.org


  • Share