#13 TODO: add automation in the build system, for extracting CONFIG_MMCONF_BASE_ADDRESS from the generated coreboot configs, and inserted into tianocore build script, for PCIE_BASE variable

# some notes about PCIE_BASE
# which is CONFIG_MMCONF_BASE_ADDRESS in .config created by coreboot
# build system. I still need to figure out how it's calculated, or if boards
# hardcode this variable

# 0xf0000000 seems to be the magic number for CONFIG_MMCONF_BASE_ADDRESS
# at least when building ROMs for X230. probably the same for other ROMs
# in coreboot build system, PCIE_BASE below is set to CONFIG_MMCONF_BASE_ADDRESS
# It's that way in the libreboot build system aswell, for all of the boards
# on libreboot d16/d8 it's 0xc0000000

# TODO: when adding more boards to retroboot, check this variable generated
# by coreboot "make menuconfig" in the menu. actually include this variable
# in resources/tianocore/boardname/pcie_base
# I need to figure out how coreboot generates this. Probably something hardcoded

<pre> # some notes about PCIE_BASE # which is CONFIG_MMCONF_BASE_ADDRESS in .config created by coreboot # build system. I still need to figure out how it's calculated, or if boards # hardcode this variable # 0xf0000000 seems to be the magic number for CONFIG_MMCONF_BASE_ADDRESS # at least when building ROMs for X230. probably the same for other ROMs # in coreboot build system, PCIE_BASE below is set to CONFIG_MMCONF_BASE_ADDRESS # It's that way in the libreboot build system aswell, for all of the boards # on libreboot d16/d8 it's 0xc0000000 # TODO: when adding more boards to retroboot, check this variable generated # by coreboot "make menuconfig" in the menu. actually include this variable # in resources/tianocore/boardname/pcie_base # I need to figure out how coreboot generates this. Probably something hardcoded </pre>