config SOC_INTEL_BAYTRAIL bool help Bay Trail M/D part support. if SOC_INTEL_BAYTRAIL config CPU_SPECIFIC_OPTIONS def_bool y select ARCH_BOOTBLOCK_X86_32 select ARCH_ROMSTAGE_X86_32 select ARCH_RAMSTAGE_X86_32 select CACHE_MRC_SETTINGS select CAR_MIGRATION select COLLECT_TIMESTAMPS select CPU_INTEL_TURBO_NOT_PACKAGE_SCOPED select CPU_MICROCODE_IN_CBFS select DYNAMIC_CBMEM select HAVE_MONOTONIC_TIMER select HAVE_SMI_HANDLER select HAVE_HARD_RESET select MMCONF_SUPPORT select MMCONF_SUPPORT_DEFAULT select RELOCATABLE_MODULES select PARALLEL_MP select PCIEXP_ASPM select PCIEXP_COMMON_CLOCK select SMM_MODULES select SMM_TSEG select SMP select SPI_FLASH select SSE2 select SUPPORT_CPU_UCODE_IN_CBFS select TSC_CONSTANT_RATE select TSC_MONOTONIC_TIMER select TSC_SYNC_MFENCE select UDELAY_TSC config BOOTBLOCK_CPU_INIT string default "soc/intel/baytrail/bootblock/bootblock.c" config MMCONF_BASE_ADDRESS hex default 0xe0000000 config MAX_CPUS int default 4 config CPU_ADDR_BITS int default 36 config SMM_TSEG_SIZE hex default 0x800000 config SMM_RESERVED_SIZE hex default 0x100000 config HAVE_MRC bool "Add a Memory Reference Code binary" default y help Select this option to add a blob containing memory reference code. Note: Without this binary coreboot will not work if HAVE_MRC config MRC_FILE string "Intel memory refeference code path and filename" default "3rdparty/northbridge/intel/sandybridge/systemagent-r6.bin" help The path and filename of the file to use as System Agent binary. Note that this points to the sandybridge binary file which is will not work, but it serves its purpose to do builds. config MRC_BIN_ADDRESS hex default 0xfffa0000 config MRC_RMT bool "Enable MRC RMT training + debug prints" default n config CACHE_MRC_SETTINGS bool "Save cached MRC settings" default n if CACHE_MRC_SETTINGS config MRC_SETTINGS_CACHE_BASE hex default 0xffb00000 config MRC_SETTINGS_CACHE_SIZE hex default 0x10000 endif # CACHE_MRC_SETTINGS endif # HAVE_MRC # Cache As RAM region layout: # # +-------------+ DCACHE_RAM_BASE + DCACHE_RAM_SIZE + DCACHE_RAM_MRC_VAR_SIZE # | MRC usage | # | | # +-------------+ DCACHE_RAM_BASE + DCACHE_RAM_SIZE # | Stack |\ # | | | * DCACHE_RAM_ROMSTAGE_STACK_SIZE # | v |/ # +-------------+ # | ^ | # | | | # | CAR Globals | # +-------------+ DCACHE_RAM_BASE # # Note that the MRC binary is linked to assume the region marked as "MRC usage" # starts at DCACHE_RAM_BASE + DCACHE_RAM_SIZE. If those values change then # a new MRC binary needs to be produced with the updated start and size # information. config DCACHE_RAM_BASE hex default 0xff800000 config DCACHE_RAM_SIZE hex default 0x8000 help The size of the cache-as-ram region required during bootblock and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE must add up to a power of 2. config DCACHE_RAM_MRC_VAR_SIZE hex default 0x8000 help The amount of cache-as-ram region required by the reference code. config DCACHE_RAM_ROMSTAGE_STACK_SIZE hex default 0x800 help The amount of anticipated stack usage from the data cache during pre-RAM ROM stage execution. config RESET_ON_INVALID_RAMSTAGE_CACHE bool "Reset the system on S3 wake when ramstage cache invalid." default n depends on RELOCATABLE_RAMSTAGE help The baytrail romstage code caches the loaded ramstage program in SMM space. On S3 wake the romstage will copy over a fresh ramstage that was cached in the SMM space. This option determines the action to take when the ramstage cache is invalid. If selected the system will reset otherwise the ramstage will be reloaded from cbfs. config CBFS_SIZE hex "Size of CBFS filesystem in ROM" default 0x100000 help On Bay Trail systems the firmware image has to store a lot more than just coreboot, including: - a firmware descriptor - Intel Management Engine firmware - MRC cache information This option allows to limit the size of the CBFS portion in the firmware image. config ENABLE_BUILTIN_COM1 bool "Enable builtin COM1 Serial Port" default n help The PMC has a legacy COM1 serial port. Choose this option to configure the pads and enable it. This serial port can be used for the debug console. config HAVE_ME_BIN bool "Add Intel Management Engine firmware" default y help The Intel processor in the selected system requires a special firmware for an integrated controller called Management Engine (ME). The ME firmware might be provided in coreboot's 3rdparty repository. If not and if you don't have the firmware elsewhere, you can still build coreboot without it. In this case however, you'll have to make sure that you don't overwrite your ME firmware on your flash ROM. config ME_BIN_PATH string "Path to management engine firmware" depends on HAVE_ME_BIN default "3rdparty/mainboard/$(MAINBOARDDIR)/me.bin" config HAVE_IFD_BIN bool default y config BUILD_WITH_FAKE_IFD bool "Build with a fake IFD" default y if !HAVE_IFD_BIN help If you don't have an Intel Firmware Descriptor (ifd.bin) for your board, you can select this option and coreboot will build without it. Though, the resulting coreboot.rom will not contain all parts required to get coreboot running on your board. You can however write only the BIOS section to your board's flash ROM and keep the other sections untouched. Unfortunately the current version of flashrom doesn't support this yet. But there is a patch pending [1]. WARNING: Never write a complete coreboot.rom to your flash ROM if it was built with a fake IFD. It just won't work. [1] http://www.flashrom.org/pipermail/flashrom/2013-June/011083.html config IFD_BIOS_SECTION depends on BUILD_WITH_FAKE_IFD string default "" config IFD_ME_SECTION depends on BUILD_WITH_FAKE_IFD string default "" config IFD_PLATFORM_SECTION depends on BUILD_WITH_FAKE_IFD string default "" config IFD_BIN_PATH string "Path to intel firmware descriptor" depends on !BUILD_WITH_FAKE_IFD default "3rdparty/mainboard/$(MAINBOARDDIR)/descriptor.bin" endif