Difference between revisions of "Coreboot Options"

From coreboot
Jump to navigation Jump to search
Line 1: Line 1:
This is an automatically generated list of '''coreboot compile-time options'''.
This is an automatically generated list of '''coreboot compile-time options'''.


Last update: 2015/05/05 16:17:26. (r4.0-9599-g40c26df-dirty)
Last update: 2016/02/19 11:53:53. (r4.3-262-g38cd375)
{| border="0" style="font-size: smaller"
{| border="0" style="font-size: smaller"
|- bgcolor="#6699dd"
|- bgcolor="#6699dd"
Line 11: Line 11:
|- bgcolor="#6699dd"
|- bgcolor="#6699dd"
! align="left" | Menu: General setup || || || ||
! align="left" | Menu: General setup || || || ||
|- bgcolor="#eeeeee"
| EXPERT || toplevel || bool || Expert mode ||
This allows you to select certain advanced configuration options.
Warning: Only enable this option if you really know what you are
doing! You have been warned!
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCALVERSION || toplevel || string || Local version string ||  
| LOCALVERSION || toplevel || string || Local version string ||  
Line 52: Line 44:
This option allows you to select the compiler used for building
This option allows you to select the compiler used for building
coreboot.
coreboot.
You must build the coreboot crosscompiler for the board that you
have selected.
To build all the GCC crosscompilers (takes a LONG time), run:
make crossgcc
For help on individual architectures, run the command:
make help_toolchain


||
||
Line 62: Line 62:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COMPILER_LLVM_CLANG || toplevel || bool || LLVM/clang ||  
| COMPILER_LLVM_CLANG || toplevel || bool || LLVM/clang (TESTING ONLY - Not currently working) ||  
Use LLVM/clang to build coreboot.
Use LLVM/clang to build coreboot.  To use this, you must build the
coreboot version of the clang compiler.  Run the command
make clang
Note that this option is not currently working correctly and should
really only be selected if you're trying to work on getting clang
operational.


For details see http://clang.llvm.org.
For details see http://clang.llvm.org.
Line 83: Line 88:


For details see https://ccache.samba.org.
For details see https://ccache.samba.org.
||
|- bgcolor="#eeeeee"
| FMD_GENPARSER || toplevel || bool || Generate flashmap descriptor parser using flex and bison ||
Enable this option if you are working on the flashmap descriptor
parser and made changes to fmd_scanner.l or fmd_parser.y.
Otherwise, say N to use the provided pregenerated scanner/parser.


||
||
Line 88: Line 101:
| SCONFIG_GENPARSER || toplevel || bool || Generate SCONFIG parser using flex and bison ||  
| SCONFIG_GENPARSER || toplevel || bool || Generate SCONFIG parser using flex and bison ||  
Enable this option if you are working on the sconfig device tree
Enable this option if you are working on the sconfig device tree
parser and made changes to sconfig.l and sconfig.y.
parser and made changes to sconfig.l or sconfig.y.


Otherwise, say N.
Otherwise, say N to use the provided pregenerated scanner/parser.


||
||
Line 165: Line 178:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RELOCATABLE_MODULES || toplevel || bool || Relocatable Modules ||  
| RELOCATABLE_MODULES || toplevel || bool || ||  
If RELOCATABLE_MODULES is selected then support is enabled for
If RELOCATABLE_MODULES is selected then support is enabled for
building relocatable modules in the RAM stage. Those modules can be
building relocatable modules in the RAM stage. Those modules can be
Line 184: Line 197:
The relocated ramstage is saved in an area specified by the
The relocated ramstage is saved in an area specified by the
by the board and/or chipset.
by the board and/or chipset.
||
|- bgcolor="#eeeeee"
| FLASHMAP_OFFSET || toplevel || hex || Flash Map Offset ||
Offset of flash map in firmware image


||
||
Line 190: Line 208:
Do not clear the reboot count immediately after successful boot.
Do not clear the reboot count immediately after successful boot.
Set to allow the payload to control normal/fallback image recovery.
Set to allow the payload to control normal/fallback image recovery.
Note that it is the responsibility of the payload to reset the
normal boot bit to 1 after each successsful boot.


||
||
Line 198: Line 218:
is a suitable file for further processing.
is a suitable file for further processing.
The bootblock will not be modified.
The bootblock will not be modified.
If unsure, select 'N'


||
||
Line 214: Line 236:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ID_MANUAL || toplevel || bool || Add board ID file to CBFS ||  
| BOARD_ID_MANUAL || toplevel || bool || ||  
If you want to maintain a board ID, but the hardware does not
If you want to maintain a board ID, but the hardware does not
have straps to automatically determine the ID, you can say Y
have straps to automatically determine the ID, you can say Y
Line 228: Line 250:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RAM_CODE_SUPPORT || toplevel || bool || Discover RAM configuration code and store it in coreboot table ||  
| RAM_CODE_SUPPORT || toplevel || bool || ||  
If enabled, coreboot discovers RAM configuration (value obtained by
If enabled, coreboot discovers RAM configuration (value obtained by
reading board straps) and stores it in coreboot table.
reading board straps) and stores it in coreboot table.


||
||
|- bgcolor="#eeeeee"
| BOOTSPLASH_IMAGE || toplevel || bool || Add a bootsplash image ||
Select this option if you have a bootsplash image that you would
like to add to your ROM.
This will only add the image to the ROM. To actually run it check
options under 'Display' section.


|- bgcolor="#6699dd"
! align="left" | Menu: Mainboard || || || ||
|- bgcolor="#eeeeee"
| || || (comment) || || see under vendor LiPPERT ||
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_DDR3_VOLT_135 || mainboard/asus/f2a85-m || bool || 1.35V ||
Set DRR3 memory voltage to 1.35V
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_DDR3_VOLT_150 || mainboard/asus/f2a85-m || bool || 1.50V ||  
| BOOTSPLASH_FILE || toplevel || string || Bootsplash path and filename ||  
Set DRR3 memory voltage to 1.50V
The path and filename of the file to use as graphical bootsplash
screen. The file format has to be jpg.
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_DDR3_VOLT_165 || mainboard/asus/f2a85-m || bool || 1.65V ||  
| ACPI_SATA_GENERATOR || acpi || bool || ||  
Set DRR3 memory voltage to 1.65V
Use acpi sata port generator.
 
||
||
|- bgcolor="#eeeeee"
 
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_135 || mainboard/asus/f2a85-m_le || bool || 1.35V ||
Set DRR3 memory voltage to 1.35V
||
||
|- bgcolor="#6699dd"
! align="left" | Menu: Mainboard || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_150 || mainboard/asus/f2a85-m_le || bool || 1.50V ||  
| UART_FOR_CONSOLE || mainboard/intel/mohonpeak || int || ||  
Set DRR3 memory voltage to 1.50V
The Mohon Peak board uses COM2 (2f8) for the serial console.
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_165 || mainboard/asus/f2a85-m_le || bool || 1.65V ||  
| PAYLOAD_CONFIGFILE || mainboard/intel/mohonpeak || string || ||  
Set DRR3 memory voltage to 1.65V
The Avoton/Rangeley chip does not allow devices to write into the 0xe000
segment. This means that USB/SATA devices will not work in SeaBIOS unless
we put the SeaBIOS buffer area down in the 0x9000 segment.
 
||
||
|- bgcolor="#6699dd"
|- bgcolor="#eeeeee"
! align="left" | Menu: On-Chip Device Power Down Control || || || ||
| UART_FOR_CONSOLE || mainboard/intel/littleplains || int || ||  
The Little Plains board uses COM2 (2f8) for the serial console.


|- bgcolor="#6699dd"
||
! align="left" | Menu: Watchdog Timer setting || || || ||
|- bgcolor="#eeeeee"
| PAYLOAD_CONFIGFILE || mainboard/intel/littleplains || string || ||  
The Avoton/Rangeley chip does not allow devices to write into the 0xe000
segment.  This means that USB/SATA devices will not work in SeaBIOS unless
we put the SeaBIOS buffer area down in the 0x9000 segment.


|- bgcolor="#6699dd"
||
! align="left" | Menu: IDE controller setting || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| IDE_STANDARD_COMPATIBLE || mainboard/dmp/vortex86ex || bool || Standard IDE Compatible ||  
| VGA_BIOS_FILE || mainboard/intel/strago || string || ||  
Built-in IDE controller PCI vendor/device ID is 17F3:1012, which
The C0 version of the video bios gets computed from this name
is not recognized by some OSes.
so that they can both be added.  Only the correct one for the
system will be run.


This option can change IDE controller PCI vendor/device ID to
||
other value for software compatibility.
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || mainboard/intel/strago || string ||  ||
The VGA_BIOS_ID for the C0 version of the video bios is hardcoded
in soc/intel/braswell/Makefile.inc as 8086,22b1


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| IDE_COMPATIBLE_SELECTION || mainboard/dmp/vortex86ex || hex || IDE Compatible Selection ||  
| ENABLE_DP3_DAUGHTER_CARD_IN_J120 || mainboard/amd/lamar || bool || Use J120 as an additional graphics port ||  
IDE controller PCI vendor/device ID value setting.
The PCI Express slot at J120 can be configured as an additional
DisplayPort connector using an adapter card from AMD or as a normal
PCI Express (x4) slot.


Higher 16-bit is vendor ID, lower 16-bit is device ID.
By default, the connector is configured as a PCI Express (x4) slot.


||
Select this option to enable the slot for use with one of AMD's
 
passive graphics port expander cards (only available from AMD).
|- bgcolor="#6699dd"
! align="left" | Menu: GPIO setting || || || ||
 
|- bgcolor="#6699dd"
! align="left" | Menu: UART setting || || || ||
 
|- bgcolor="#6699dd"
! align="left" | Menu: LPT setting || || || ||
 
|- bgcolor="#eeeeee"
| UART_FOR_CONSOLE || mainboard/intel/mohonpeak || int ||  ||
The Mohon Peak board uses COM2 (2f8) for the serial console.
 
||
|- bgcolor="#eeeeee"
| SEABIOS_MALLOC_UPPERMEMORY || mainboard/intel/mohonpeak || bool ||  ||
The Avoton/Rangeley chip does not allow devices to write into the 0xe000
segment.  This means that USB/SATA devices will not work in SeaBIOS unless
we put the SeaBIOS buffer area down in the 0x9000 segment.


||
||
Line 334: Line 355:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAINBOARD_PART_NUMBER || mainboard/google/nyan || string || BCT boot media ||  
| DISPLAY_SPD_DATA || mainboard/google/cyan || bool || Display Memory Serial Presence Detect Data ||  
Which boot media to configure the BCT for.
When enabled displays the memory configuration data.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| NYAN_BCT_CFG_SPI || mainboard/google/nyan || bool || SPI ||  
| VGA_BIOS_FILE || mainboard/google/cyan || string || ||  
Configure the BCT for booting from SPI.
The C0 version of the video bios gets computed from this name
 
so that they can both be added. Only the correct one for the
||
system will be run.
|- bgcolor="#eeeeee"
| NYAN_BCT_CFG_EMMC || mainboard/google/nyan || bool || eMMC ||
Configure the BCT for booting from eMMC.
 
||
|- bgcolor="#eeeeee"
| BOOT_MEDIA_SPI_BUS || mainboard/google/nyan || int || SPI bus with boot media ROM ||
Which SPI bus the boot media is connected to.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/nyan || int || Chip select for SPI boot media ||  
| VGA_BIOS_ID || mainboard/google/cyan || string || ||  
Which chip select to use for boot media.
The VGA_BIOS_ID for the C0 version of the video bios is hardcoded
in soc/intel/braswell/Makefile.inc as 8086,22b1


||
||
Line 384: Line 398:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAINBOARD_PART_NUMBER || mainboard/google/nyan_big || string || BCT boot media ||  
| DRAM_SIZE_MB || mainboard/google/smaug || int || BCT boot media ||  
Which boot media to configure the BCT for.
Which boot media to configure the BCT for.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| NYAN_BIG_BCT_CFG_SPI || mainboard/google/nyan_big || bool || SPI ||  
| SMAUG_BCT_CFG_SPI || mainboard/google/smaug || bool || SPI ||  
Configure the BCT for booting from SPI.
Configure the BCT for booting from SPI.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| NYAN_BIG_BCT_CFG_EMMC || mainboard/google/nyan_big || bool || eMMC ||  
| SMAUG_BCT_CFG_EMMC || mainboard/google/smaug || bool || eMMC ||  
Configure the BCT for booting from eMMC.
Configure the BCT for booting from eMMC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOT_MEDIA_SPI_BUS || mainboard/google/nyan_big || int || SPI bus with boot media ROM ||  
| BOOT_MEDIA_SPI_BUS || mainboard/google/smaug || int || SPI bus with boot media ROM ||  
Which SPI bus the boot media is connected to.
Which SPI bus the boot media is connected to.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/nyan_big || int || Chip select for SPI boot media ||  
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/smaug || int || Chip select for SPI boot media ||  
Which chip select to use for boot media.
Which chip select to use for boot media.


Line 434: Line 448:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_DP3_DAUGHTER_CARD_IN_J120 || mainboard/amd/lamar || bool || Use J120 as an additional graphics port ||  
| MAINBOARD_PART_NUMBER || mainboard/google/nyan_big || string || BCT boot media ||  
The PCI Express slot at J120 can be configured as an additional
Which boot media to configure the BCT for.
DisplayPort connector using an adapter card from AMD or as a normal
PCI Express (x4) slot.


By default, the connector is configured as a PCI Express (x4) slot.
||
 
|- bgcolor="#eeeeee"
Select this option to enable the slot for use with one of AMD's
| NYAN_BIG_BCT_CFG_SPI || mainboard/google/nyan_big || bool || SPI ||
passive graphics port expander cards (only available from AMD).
Configure the BCT for booting from SPI.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || was acquired by ADLINK ||
| NYAN_BIG_BCT_CFG_EMMC || mainboard/google/nyan_big || bool || eMMC ||  
|- bgcolor="#eeeeee"
Configure the BCT for booting from eMMC.
| ONBOARD_UARTS_RS485 || mainboard/lippert/literunner-lx || bool || Switch on-board serial ports 1 & 2 to RS485 ||  
If selected, the first two on-board serial ports will operate in RS485
mode instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ONBOARD_IDE_SLAVE || mainboard/lippert/literunner-lx || bool || Make on-board CF socket act as Slave ||  
| BOOT_MEDIA_SPI_BUS || mainboard/google/nyan_big || int || SPI bus with boot media ROM ||  
If selected, the on-board Compact Flash card socket will act as IDE
Which SPI bus the boot media is connected to.
Slave instead of Master.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_OLD_REVISION || mainboard/lippert/hurricane-lx || bool || Board is old pre-3.0 revision ||  
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/nyan_big || int || Chip select for SPI boot media ||  
Look on the bottom side for a number like 406-0001-30.  The last 2
Which chip select to use for boot media.
digits state the PCB revision (3.0 in this example).  For 2.0 or older
boards choose Y, for 3.0 and newer say N.
 
Old revision boards need a jumper shorting the power button to
power on automatically.  You may enable the button only after this
jumper has been removed.  New revision boards are not restricted
in this way, and always have the power button enabled.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ONBOARD_UARTS_RS485 || mainboard/lippert/hurricane-lx || bool || Switch on-board serial ports to RS485 ||  
| DRAM_SIZE_MB || mainboard/google/foster || int || BCT boot media ||  
If selected, both on-board serial ports will operate in RS485 mode
Which boot media to configure the BCT for.
instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ONBOARD_UARTS_RS485 || mainboard/lippert/spacerunner-lx || bool || Switch on-board serial ports to RS485 ||  
| FOSTER_BCT_CFG_SPI || mainboard/google/foster || bool || SPI ||  
If selected, both on-board serial ports will operate in RS485 mode
Configure the BCT for booting from SPI.
instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ONBOARD_IDE_SLAVE || mainboard/lippert/spacerunner-lx || bool || Make on-board SSD act as Slave ||  
| FOSTER_BCT_CFG_EMMC || mainboard/google/foster || bool || eMMC ||  
If selected, the on-board SSD will act as IDE Slave instead of Master.
Configure the BCT for booting from eMMC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ONBOARD_UARTS_RS485 || mainboard/lippert/roadrunner-lx || bool || Switch on-board serial ports to RS485 ||  
| BOOT_MEDIA_SPI_BUS || mainboard/google/foster || int || SPI bus with boot media ROM ||  
If selected, both on-board serial ports will operate in RS485 mode
Which SPI bus the boot media is connected to.
instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOARD_ROMSIZE_KB_16384 || mainboard || bool || ROM chip size ||  
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/foster || int || Chip select for SPI boot media ||  
Select the size of the ROM chip you intend to flash coreboot on.
Which chip select to use for boot media.
 
The build system will take care of creating a coreboot.rom file
of the matching size.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_64 || mainboard || bool || 64 KB ||  
| MAINBOARD_PART_NUMBER || mainboard/google/nyan || string || BCT boot media ||  
Choose this option if you have a 64 KB ROM chip.
Which boot media to configure the BCT for.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_128 || mainboard || bool || 128 KB ||  
| NYAN_BCT_CFG_SPI || mainboard/google/nyan || bool || SPI ||  
Choose this option if you have a 128 KB ROM chip.
Configure the BCT for booting from SPI.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_256 || mainboard || bool || 256 KB ||  
| NYAN_BCT_CFG_EMMC || mainboard/google/nyan || bool || eMMC ||  
Choose this option if you have a 256 KB ROM chip.
Configure the BCT for booting from eMMC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_512 || mainboard || bool || 512 KB ||  
| BOOT_MEDIA_SPI_BUS || mainboard/google/nyan || int || SPI bus with boot media ROM ||  
Choose this option if you have a 512 KB ROM chip.
Which SPI bus the boot media is connected to.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_1024 || mainboard || bool || 1024 KB (1 MB) ||  
| BOOT_MEDIA_SPI_CHIP_SELECT || mainboard/google/nyan || int || Chip select for SPI boot media ||  
Choose this option if you have a 1024 KB (1 MB) ROM chip.
Which chip select to use for boot media.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_2048 || mainboard || bool || 2048 KB (2 MB) ||  
| BOARD_ASUS_F2A85_M_DDR3_VOLT_135 || mainboard/asus/f2a85-m || bool || 1.35V ||  
Choose this option if you have a 2048 KB (2 MB) ROM chip.
Set DRR3 memory voltage to 1.35V
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_4096 || mainboard || bool || 4096 KB (4 MB) ||  
| BOARD_ASUS_F2A85_M_DDR3_VOLT_150 || mainboard/asus/f2a85-m || bool || 1.50V ||
Choose this option if you have a 4096 KB (4 MB) ROM chip.
Set DRR3 memory voltage to 1.50V
 
||
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_DDR3_VOLT_165 || mainboard/asus/f2a85-m || bool || 1.65V ||
Set DRR3 memory voltage to 1.65V
||
|- bgcolor="#eeeeee"
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_135 || mainboard/asus/f2a85-m_le || bool || 1.35V ||
Set DRR3 memory voltage to 1.35V
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_8192 || mainboard || bool || 8192 KB (8 MB) ||  
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_150 || mainboard/asus/f2a85-m_le || bool || 1.50V ||  
Choose this option if you have a 8192 KB (8 MB) ROM chip.
Set DRR3 memory voltage to 1.50V
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_12288 || mainboard || bool || 12288 KB (12 MB) ||  
| BOARD_ASUS_F2A85_M_LE_DDR3_VOLT_165 || mainboard/asus/f2a85-m_le || bool || 1.65V ||  
Choose this option if you have a 12288 KB (12 MB) ROM chip.
Set DRR3 memory voltage to 1.65V
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| COREBOOT_ROMSIZE_KB_16384 || mainboard || bool || 16384 KB (16 MB) ||  
| DRIVERS_PS2_KEYBOARD || mainboard/purism/librem13 || None || ||  
Choose this option if you have a 16384 KB (16 MB) ROM chip.
Default PS/2 Keyboard to enabled on this board.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_POWER_BUTTON || mainboard || bool || Enable the power button ||  
| DRIVERS_UART_8250IO || mainboard/purism/librem13 || None || ||  
The selected mainboard can optionally have the power button tied
This platform does not have any way to get standard
to ground with a jumper so that the button appears to be
serial output so disable it by default.
constantly depressed. If this option is enabled and the jumper is
installed then the board will turn on, but turn off again after a
short timeout, usually 4 seconds.
 
Select Y here if you have removed the jumper and want to use an
actual power button. Select N if you have the jumper installed.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LATE_CBMEM_INIT || arch/x86 || bool ||  ||  
| NO_POST || mainboard/purism/librem13 || int ||  ||  
Enable this in chipset's Kconfig if northbridge does not implement
This platform does not have any way to see POST codes
early get_top_of_ram() call for romstage. CBMEM tables will be
so disable them by default.
allocated late in ramstage, after PCI devices resources are known.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: ChromeOS || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CHROMEOS || vendorcode/google/chromeos || bool || Build for ChromeOS ||  
| || || (comment) || || was acquired by ADLINK ||
Enable ChromeOS specific features like the GPIO sub table in
|- bgcolor="#eeeeee"
the coreboot table. NOTE: Enabling this option on an unsupported
| ONBOARD_UARTS_RS485 || mainboard/lippert/spacerunner-lx || bool || Switch on-board serial ports to RS485 ||  
board will most likely break your build.
If selected, both on-board serial ports will operate in RS485 mode
instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBNV_OFFSET || vendorcode/google/chromeos || hex || ||  
| ONBOARD_IDE_SLAVE || mainboard/lippert/spacerunner-lx || bool || Make on-board SSD act as Slave ||  
CMOS offset for VbNv data. This value must match cmos.layout
If selected, the on-board SSD will act as IDE Slave instead of Master.
in the mainboard directory, minus 14 bytes for the RTC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBNV_SIZE || vendorcode/google/chromeos || hex || ||  
| BOARD_OLD_REVISION || mainboard/lippert/hurricane-lx || bool || Board is old pre-3.0 revision ||  
CMOS storage size for VbNv data. This value must match cmos.layout
Look on the bottom side for a number like 406-0001-30.  The last 2
in the mainboard directory.
digits state the PCB revision (3.0 in this example). For 2.0 or older
boards choose Y, for 3.0 and newer say N.


||
Old revision boards need a jumper shorting the power button to
|- bgcolor="#eeeeee"
power on automatically.  You may enable the button only after this
| CHROMEOS_VBNV_CMOS || vendorcode/google/chromeos || bool || Vboot non-volatile storage in CMOS. ||
jumper has been removed. New revision boards are not restricted
VBNV is stored in CMOS
in this way, and always have the power button enabled.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CHROMEOS_VBNV_EC || vendorcode/google/chromeos || bool || Vboot non-volatile storage in EC. ||  
| ONBOARD_UARTS_RS485 || mainboard/lippert/hurricane-lx || bool || Switch on-board serial ports to RS485 ||  
VBNV is stored in EC
If selected, both on-board serial ports will operate in RS485 mode
instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CHROMEOS_VBNV_FLASH || vendorcode/google/chromeos || bool || ||  
| ONBOARD_UARTS_RS485 || mainboard/lippert/literunner-lx || bool || Switch on-board serial ports 1 & 2 to RS485 ||  
VBNV is stored in flash storage
If selected, the first two on-board serial ports will operate in RS485
mode instead of RS232.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FLASHMAP_OFFSET || vendorcode/google/chromeos || hex || Flash Map Offset ||  
| ONBOARD_IDE_SLAVE || mainboard/lippert/literunner-lx || bool || Make on-board CF socket act as Slave ||  
Offset of flash map in firmware image
If selected, the on-board Compact Flash card socket will act as IDE
Slave instead of Master.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_SOFTWARE_SYNC || vendorcode/google/chromeos || bool || Enable EC software sync ||  
| ONBOARD_UARTS_RS485 || mainboard/lippert/roadrunner-lx || bool || Switch on-board serial ports to RS485 ||  
EC software sync is a mechanism where the AP helps the EC verify its
If selected, both on-board serial ports will operate in RS485 mode
firmware similar to how vboot verifies the main system firmware. This
instead of RS232.
option selects whether depthcharge should support EC software sync.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: On-Chip Device Power Down Control || || || ||
|- bgcolor="#6699dd"
! align="left" | Menu: Watchdog Timer setting || || || ||
|- bgcolor="#6699dd"
! align="left" | Menu: IDE controller setting || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_EC_SLOW_UPDATE || vendorcode/google/chromeos || bool || EC is slow to update ||  
| IDE_STANDARD_COMPATIBLE || mainboard/dmp/vortex86ex || bool || Standard IDE Compatible ||  
Whether the EC (or PD) is slow to update and needs to display a
Built-in IDE controller PCI vendor/device ID is 17F3:1012, which
screen that informs the user the update is happening.
is not recognized by some OSes.


||
This option can change IDE controller PCI vendor/device ID to
|- bgcolor="#eeeeee"
other value for software compatibility.
| VBOOT_OPROM_MATTERS || vendorcode/google/chromeos || bool || Video option ROM matters ||
Whether the video option ROM has run matters on this platform.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VIRTUAL_DEV_SWITCH || vendorcode/google/chromeos || bool || Virtual developer switch support ||  
| IDE_COMPATIBLE_SELECTION || mainboard/dmp/vortex86ex || hex || IDE Compatible Selection ||  
Whether this platform has a virtual developer switch.
IDE controller PCI vendor/device ID value setting.


||
Higher 16-bit is vendor ID, lower 16-bit is device ID.
|- bgcolor="#eeeeee"
| VBOOT_VERIFY_FIRMWARE || vendorcode/google/chromeos || bool || Verify firmware with vboot. ||
Enabling VBOOT_VERIFY_FIRMWARE will use vboot to verify the components
of the firmware (stages, payload, etc).


||
||
|- bgcolor="#eeeeee"
| NO_TPM_RESUME || vendorcode/google/chromeos || bool ||  ||
On some boards the TPM stays powered up in S3. On those
boards, booting Windows will break if the TPM resume command
is sent during an S3 resume.


||
|- bgcolor="#6699dd"
! align="left" | Menu: GPIO setting || || || ||
 
|- bgcolor="#6699dd"
! align="left" | Menu: UART setting || || || ||
 
|- bgcolor="#6699dd"
! align="left" | Menu: LPT setting || || || ||
 
|- bgcolor="#eeeeee"
| || || (comment) || || see under vendor LiPPERT ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PHYSICAL_REC_SWITCH || vendorcode/google/chromeos || bool || Physical recovery switch is present ||  
| BOARD_ROMSIZE_KB_16384 || mainboard || bool || ROM chip size ||  
Whether this platform has a physical recovery switch
Select the size of the ROM chip you intend to flash coreboot on.
 
The build system will take care of creating a coreboot.rom file
of the matching size.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| WIPEOUT_SUPPORTED || vendorcode/google/chromeos || bool || User is able to request factory reset ||  
| COREBOOT_ROMSIZE_KB_64 || mainboard || bool || 64 KB ||  
When this option is enabled, the firmware provides the ability to
Choose this option if you have a 64 KB ROM chip.
signal the application the need for factory reset (a.k.a. wipe
out) of the device


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_STARTS_IN_BOOTBLOCK || vendorcode/google/chromeos/vboot2 || bool || ||  
| COREBOOT_ROMSIZE_KB_128 || mainboard || bool || 128 KB ||  
Firmware verification happens during or at the end of bootblock.
Choose this option if you have a 128 KB ROM chip.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_STARTS_IN_ROMSTAGE || vendorcode/google/chromeos/vboot2 || bool || ||  
| COREBOOT_ROMSIZE_KB_256 || mainboard || bool || 256 KB ||  
Firmware verification happens during or at the end of romstage.
Choose this option if you have a 256 KB ROM chip.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT2_MOCK_SECDATA || vendorcode/google/chromeos/vboot2 || bool || Mock secdata for firmware verification ||  
| COREBOOT_ROMSIZE_KB_512 || mainboard || bool || 512 KB ||  
Enabling VBOOT2_MOCK_SECDATA will mock secdata for the firmware
Choose this option if you have a 512 KB ROM chip.
verification to avoid access to a secdata storage (typically TPM).
All operations for a secdata storage will be successful. This option
can be used during development when a TPM is not present or broken.
THIS SHOULD NOT BE LEFT ON FOR PRODUCTION DEVICES.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_DISABLE_DEV_ON_RECOVERY || vendorcode/google/chromeos/vboot2 || bool || Disable dev mode on recovery requests ||  
| COREBOOT_ROMSIZE_KB_1024 || mainboard || bool || 1024 KB (1 MB) ||  
When this option is enabled, the Chrome OS device leaves the
Choose this option if you have a 1024 KB (1 MB) ROM chip.
developer mode as soon as recovery request is detected. This is
handy on embedded devices with limited input capabilities.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RETURN_FROM_VERSTAGE || vendorcode/google/chromeos/vboot2 || bool || ||  
| COREBOOT_ROMSIZE_KB_2048 || mainboard || bool || 2048 KB (2 MB) ||  
If this is set, the verstage returns back to the calling stage instead
Choose this option if you have a 2048 KB (2 MB) ROM chip.
of exiting to the succeeding stage so that the verstage space can be
reused by the succeeding stage. This is useful if a ram space is too
small to fit both the verstage and the succeeding stage.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_ROMSTAGE_INDEX || vendorcode/google/chromeos/vboot2 || hex || Romstage component index ||  
| COREBOOT_ROMSIZE_KB_4096 || mainboard || bool || 4096 KB (4 MB) ||  
This is the index of the romstage component in the verified
Choose this option if you have a 4096 KB (4 MB) ROM chip.
firmware block.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_RAMSTAGE_INDEX || vendorcode/google/chromeos/vboot2 || hex || Ramstage component index ||  
| COREBOOT_ROMSIZE_KB_8192 || mainboard || bool || 8192 KB (8 MB) ||  
This is the index of the ramstage component in the verified
Choose this option if you have a 8192 KB (8 MB) ROM chip.
firmware block.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_REFCODE_INDEX || vendorcode/google/chromeos/vboot2 || hex || Reference code firmware index ||  
| COREBOOT_ROMSIZE_KB_12288 || mainboard || bool || 12288 KB (12 MB) ||  
This is the index of the reference code component in the verified
Choose this option if you have a 12288 KB (12 MB) ROM chip.
firmware block.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VBOOT_BOOT_LOADER_INDEX || vendorcode/google/chromeos/vboot2 || hex || Bootloader component index ||  
| COREBOOT_ROMSIZE_KB_16384 || mainboard || bool || 16384 KB (16 MB) ||  
This is the index of the bootloader component in the verified
Choose this option if you have a 16384 KB (16 MB) ROM chip.
firmware block.
 
||


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VIRTUAL_DEV_SWITCH || vendorcode/google/chromeos || bool || ||  
| ENABLE_POWER_BUTTON || mainboard || bool || Enable the power button ||  
Whether this platform has a virtual developer switch.
The selected mainboard can optionally have the power button tied
||
to ground with a jumper so that the button appears to be
constantly depressed. If this option is enabled and the jumper is
installed then the board will turn on, but turn off again after a
short timeout, usually 4 seconds.


|- bgcolor="#6699dd"
Select Y here if you have removed the jumper and want to use an
! align="left" | Menu: AMD Platform Initialization || || || ||
actual power button. Select N if you have the jumper installed.
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_PATH_DEFAULT || vendorcode/amd/pi/00630F01 || string ||  ||
The default binary file name to use for AMD platform initialization.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_FILE_DEFAULT || vendorcode/amd/pi/00630F01 || string || ||  
| CBFS_SIZE || toplevel || hex || Size of CBFS filesystem in ROM ||  
The default binary file name to use for AMD platform initialization.
This is the part of the ROM actually managed by CBFS, located at the
end of the ROM (passed through cbfstool -o) on x86 and at at the start
of the ROM (passed through cbfstool -s) everywhere else. It defaults
to span the whole ROM on all but Intel systems that use an Intel Firmware
Descriptor.  It can be overridden to make coreboot live alongside other
components like ChromeOS's vboot/FMAP or Intel's IFD / ME / TXE
binaries.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_LOCATION_DEFAULT || vendorcode/amd/pi/00630F01 || hex || ||  
| FMDFILE || toplevel || string || fmap description file in fmd format ||  
The default ROM address at which to store the binary Platform
The build system creates a default FMAP from ROM_SIZE and CBFS_SIZE,
Initialization code.
but in some cases more complex setups are required.
When an fmd is specified, it overrides the default format.


||
||
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_PATH_DEFAULT || vendorcode/amd/pi/00730F01 || string ||  ||
The default binary file name to use for AMD platform initialization.


||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_FILE_DEFAULT || vendorcode/amd/pi/00730F01 || string ||  ||  
| CBFS_AUTOGEN_ATTRIBUTES || toplevel || bool ||  ||  
The default binary file name to use for AMD platform initialization.
If this option is selected, every file in cbfs which has a constraint
regarding position or alignment will get an additional file attribute
which describes this constraint.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: Chipset || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_LOCATION_DEFAULT || vendorcode/amd/pi/00730F01 || hex || ||  
| || || (comment) || || SoC ||
The default ROM address at which to store the binary Platform
|- bgcolor="#eeeeee"
Initialization code.
| MAINBOARD_DO_DSI_INIT || soc/nvidia/tegra210 || bool || Use dsi graphics interface ||  
Initialize dsi display


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| None || vendorcode/amd || None || AGESA source ||  
| MAINBOARD_DO_SOR_INIT || soc/nvidia/tegra210 || bool || Use dp graphics interface ||  
Select the method for including the AMD Platform Initialization
Initialize dp display
code into coreboot.  Platform Initialization code is required for
all AMD processors.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_AMD_AGESA_BINARY_PI || vendorcode/amd || bool || binary PI ||  
| CONSOLE_SERIAL_TEGRA210_UARTA || soc/nvidia/tegra210 || bool || UARTA ||  
Use a binary PI package.  Generally, these will be stored in the
Serial console on UART A.
"3rdparty" directory.  For some processors, these must be obtained
directly from AMD Embedded Processors Group
(http://www.amdcom/embedded).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_AMD_AGESA_OPENSOURCE || vendorcode/amd || bool || open-source AGESA ||  
| CONSOLE_SERIAL_TEGRA210_UARTB || soc/nvidia/tegra210 || bool || UARTB ||  
Build the PI package ("AGESA") from source code in the "vendorcode"
Serial console on UART B.
directory.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_PATH || vendorcode/amd || string || AGESA PI directory path ||  
| CONSOLE_SERIAL_TEGRA210_UARTC || soc/nvidia/tegra210 || bool || UARTC ||  
Specify where to find the AGESA headers and binary file
Serial console on UART C.
for AMD platform initialization.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_FILE || vendorcode/amd || string || AGESA PI binary file name ||  
| CONSOLE_SERIAL_TEGRA210_UARTD || soc/nvidia/tegra210 || bool || UARTD ||  
Specify the binary file to use for AMD platform initialization.
Serial console on UART D.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AGESA_BINARY_PI_LOCATION || vendorcode/amd || string || AGESA PI binary address in ROM ||  
| CONSOLE_SERIAL_TEGRA210_UARTE || soc/nvidia/tegra210 || bool || UARTE ||  
Specify the ROM address at which to store the binary Platform
Serial console on UART E.
Initialization code.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: Chipset || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || CPU ||
| CONSOLE_SERIAL_TEGRA210_UART_ADDRESS || soc/nvidia/tegra210 || hex ||  ||  
|- bgcolor="#eeeeee"
Map the UART names to the respective MMIO addres.
| LAPIC_MONOTONIC_TIMER || cpu/x86 || bool ||  ||  
Expose monotonic time using the local apic.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| TSC_CONSTANT_RATE || cpu/x86 || bool || ||  
| BOOTROM_SDRAM_INIT || soc/nvidia/tegra210 || bool || SoC BootROM does SDRAM init with full BCT ||  
This option asserts that the TSC ticks at a known constant rate.
Use during Foster LPDDR4 bringup.
Therefore, no TSC calibration is required.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| TSC_MONOTONIC_TIMER || cpu/x86 || bool || ||  
| TRUSTZONE_CARVEOUT_SIZE_MB || soc/nvidia/tegra210 || hex || Size of Trust Zone region ||  
Expose monotonic time using the TSC.
Size of Trust Zone area in MiB to reserve in memory map.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| TSC_SYNC_LFENCE || cpu/x86 || bool || ||  
| TTB_SIZE_MB || soc/nvidia/tegra210 || hex || Size of TTB ||  
The CPU driver should select this if the CPU needs
Maximum size of Translation Table Buffer in MiB.
to execute an lfence instruction in order to synchronize
rdtsc. This is true for all modern AMD CPUs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| TSC_SYNC_MFENCE || cpu/x86 || bool || ||  
| SEC_COMPONENT_SIZE_MB || soc/nvidia/tegra210 || hex || Size of resident EL3 components ||  
The CPU driver should select this if the CPU needs
Maximum size of resident EL3 components in MiB including BL31 and
to execute an mfence instruction in order to synchronize
Secure OS.
rdtsc. This is true for all modern Intel CPUs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SMM_MODULES || cpu/x86 || bool || ||  
| HAVE_MTC || soc/nvidia/tegra210 || bool || Add external Memory controller Training Code binary ||  
If SMM_MODULES is selected then SMM handlers are built as modules.
Select this option to add emc training firmware
A SMM stub along with a SMM loader/relocator. All the handlers are
written in C with stub being the only assembly.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SMM_MODULE_HEAP_SIZE || cpu/x86 || hex || ||  
| MTC_FILE || soc/nvidia/tegra210 || string || tegra mtc firmware filename ||  
This option determines the size of the heap within the SMM handler
The filename of the mtc firmware
modules.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| X86_AMD_FIXED_MTRRS || cpu/x86 || bool || ||  
| MTC_DIRECTORY || soc/nvidia/tegra210 || string || Directory where MTC firmware file is located ||  
This option informs the MTRR code to use the RdMem and WrMem fields
Path to directory where MTC firmware file is located.
in the fixed MTRR MSRs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PLATFORM_USES_FSP1_0 || cpu/x86 || bool ||  ||  
| MTC_ADDRESS || soc/nvidia/tegra210 || hex ||  ||  
Selected for Intel processors/platform combinations that use the
The DRAM location where MTC firmware to be loaded in. This location
Intel Firmware Support Package (FSP) 1.0 for initialization.
needs to be consistent with the location defined in tegra_mtc.ld


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PARALLEL_MP || cpu/x86 || bool || ||  
| MAINBOARD_DO_DSI_INIT || soc/nvidia/tegra132 || bool || Use dsi graphics interface ||  
This option uses common MP infrastructure for bringing up APs
Initialize dsi display
in parallel. It additionally provides a more flexible mechanism
for sequencing the steps of bringing up the APs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BACKUP_DEFAULT_SMM_REGION || cpu/x86 || bool || ||  
| MAINBOARD_DO_SOR_INIT || soc/nvidia/tegra132 || bool || Use dp graphics interface ||  
The CPU support will select this option if the default SMM region
Initialize dp display
needs to be backed up for suspend/resume purposes.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MIRROR_PAYLOAD_TO_RAM_BEFORE_LOADING || cpu/x86 || bool || ||  
| MTS_DIRECTORY || soc/nvidia/tegra132 || string || Directory where MTS microcode files are located ||  
On certain platforms a boot speed gain can be realized if mirroring
Path to directory where MTS microcode files are located.
the payload data stored in non-volatile storage. On x86 systems the
payload would typically live in a memory-mapped SPI part. Copying
the SPI contents to RAM before performing the load can speed up
the boot process.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOT_MEDIA_SPI_BUS || cpu/x86 || int || ||  
| TRUSTZONE_CARVEOUT_SIZE_MB || soc/nvidia/tegra132 || hex || Size of Trust Zone region ||  
Most x86 systems which boot from SPI flash boot using bus 0.
Size of Trust Zone area in MiB to reserve in memory map.


||
||
|- bgcolor="#eeeeee"
| BOOTROM_SDRAM_INIT || soc/nvidia/tegra132 || bool || SoC BootROM does SDRAM init with full BCT ||
Use during Ryu LPDDR3 bringup
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RESET_ON_INVALID_RAMSTAGE_CACHE || cpu/intel/haswell || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
| SOC_INTEL_FSP_BAYTRAIL || soc/intel/fsp_baytrail || bool || ||
The haswell romstage code caches the loaded ramstage program
Bay Trail I part support using the Intel FSP.
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
|- bgcolor="#eeeeee"
the system will reset otherwise the ramstage will be reloaded from
| SMM_TSEG_SIZE || soc/intel/fsp_baytrail || hex ||  ||  
cbfs.
This is set by the FSP
 
||
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || soc/intel/fsp_baytrail || string ||  ||
This is the default PCI ID for the Bay Trail graphics
devices. This string names the vbios ROM in cbfs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MONOTONIC_TIMER_MSR || cpu/intel/haswell || bool || ||  
| ENABLE_BUILTIN_COM1 || soc/intel/fsp_baytrail || bool || Enable built-in legacy Serial Port ||  
Provide a monotonic timer using the 24MHz MSR counter.
The Baytrail SOC has one legacy serial port. Choose this option to
configure the pads and enable it. This serial port can be used for
the debug console.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_INTEL_FIRMWARE_INTERFACE_TABLE || cpu/intel/fit || None ||  ||  
| FSP_FILE || soc/intel/fsp_baytrail/fsp || string ||  ||  
This option selects building a Firmware Interface Table (FIT).
The path and filename of the Intel FSP binary for this platform.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_INTEL_NUM_FIT_ENTRIES || cpu/intel/fit || int ||  ||  
| FSP_LOC || soc/intel/fsp_baytrail/fsp || hex ||  ||  
This option selects the number of empty entries in the FIT table.
The location in CBFS that the FSP is located. This must match the
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with Intel's BCT (tool).


The Bay Trail FSP is built with a preferred base address of
0xFFFC0000.


||
||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_INTEL_TURBO_NOT_PACKAGE_SCOPED || cpu/intel/turbo || None ||  ||  
| SOC_INTEL_BRASWELL || soc/intel/braswell || bool ||  ||  
This option indicates that the turbo mode setting is not package
Braswell M/D part support.
scoped. i.e. enable_turbo() needs to be called on not just the bsp


||
||
|- bgcolor="#eeeeee"
| DCACHE_RAM_SIZE || soc/intel/braswell || hex || Temporary RAM Size ||
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.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| GEODE_VSA_FILE || cpu/amd/geode_gx2 || bool || Add a VSA image ||  
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || soc/intel/braswell || hex || ||  
Select this option if you have an AMD Geode GX2 vsa that you would
The amount of anticipated stack usage from the data cache
like to add to your ROM.
during pre-ram rom stage execution.
 
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VSA_FILENAME || cpu/amd/geode_gx2 || string || AMD Geode GX2 VSA path and filename ||  
| RESET_ON_INVALID_RAMSTAGE_CACHE || soc/intel/braswell || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
The path and filename of the file to use as VSA.
The haswell 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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| GEODE_VSA_FILE || cpu/amd/geode_lx || bool || Add a VSA image ||  
| ENABLE_BUILTIN_COM1 || soc/intel/braswell || bool || Enable builtin COM1 Serial Port ||  
Select this option if you have an AMD Geode LX vsa that you would
The PMC has a legacy COM1 serial port. Choose this option to
like to add to your ROM.
configure the pads and enable it. This serial port can be used for
 
the debug console.
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VSA_FILENAME || cpu/amd/geode_lx || string || AMD Geode LX VSA path and filename ||  
| SOC_INTEL_APOLLOLAKE || soc/intel/apollolake || bool || ||  
The path and filename of the file to use as VSA.
Intel Apollolake support


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| XIP_ROM_SIZE || cpu/amd/agesa || hex || ||  
| DCACHE_RAM_SIZE || soc/intel/apollolake || hex || Length in bytes of cache-as-RAM ||  
Overwride the default write through caching size as 1M Bytes.
The size of the cache-as-ram region required during bootblock
On some AMD platforms, one socket supports 2 or more kinds of
and/or romstage.
processor family, compiling several CPU families agesa code
will increase the romstage size.
In order to execute romstage in place on the flash ROM,
more space is required to be set as write through caching.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| REDIRECT_IDS_HDT_CONSOLE_TO_SERIAL || cpu/amd/agesa/family10 || bool || Redirect AGESA IDS_HDT_CONSOLE to serial console ||  
| DCACHE_BSP_STACK_SIZE || soc/intel/apollolake || hex || ||  
This Option allows you to redirect the AMD AGESA IDS_HDT_CONSOLE debug information to the serial console.
The amount of anticipated stack usage in CAR by bootblock and
 
other stages.
Warning: Only enable this option when debuging or tracing AMD AGESA code.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_AMD_SOCKET_G34 || cpu/amd/agesa/family15 || bool ||  ||  
| SOC_INTEL_BAYTRAIL || soc/intel/baytrail || bool ||  ||  
AMD G34 Socket
Bay Trail M/D part support.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_AMD_SOCKET_C32 || cpu/amd/agesa/family15 || bool || ||  
| HAVE_MRC || soc/intel/baytrail || bool || Add a Memory Reference Code binary ||  
AMD C32 Socket
Select this option to add a blob containing
memory reference code.
Note: Without this binary coreboot will not work


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_AMD_SOCKET_AM3R2 || cpu/amd/agesa/family15 || bool || ||  
| MRC_FILE || soc/intel/baytrail || string || Intel memory refeference code path and filename ||  
AMD AM3r2 Socket
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| REDIRECT_IDS_HDT_CONSOLE_TO_SERIAL || cpu/amd/agesa/family15 || bool || Redirect AGESA IDS_HDT_CONSOLE to serial console ||  
| DCACHE_RAM_SIZE || soc/intel/baytrail || hex || ||  
This Option allows you to redirect the AMD AGESA IDS_HDT_CONSOLE debug information to the serial console.
The size of the cache-as-ram region required during bootblock
 
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
Warning: Only enable this option when debuging or tracing AMD AGESA code.
must add up to a power of 2.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FORCE_AM1_SOCKET_SUPPORT || cpu/amd/agesa/family16kb || bool ||  ||  
| DCACHE_RAM_MRC_VAR_SIZE || soc/intel/baytrail || hex ||  ||  
Force AGESA to ignore package type mismatch between CPU and northbridge
The amount of cache-as-ram region required by the reference code.
in memory code. This enables Socket AM1 support with current AGESA
version for Kabini platform.
Enable this option only if you have Socket AM1 board.
Note that the AGESA release shipped with coreboot does not officially
support the AM1 socket. Selecting this option might damage your hardware.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| XIP_ROM_SIZE || cpu/amd/pi || hex ||  ||  
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || soc/intel/baytrail || hex ||  ||  
Overwride the default write through caching size as 1M Bytes.
The amount of anticipated stack usage from the data cache
On some AMD platforms, one socket supports 2 or more kinds of
during pre-RAM ROM stage execution.
processor family, compiling several CPU families agesa code
will increase the romstage size.
In order to execute romstage in place on the flash ROM,
more space is required to be set as write through caching.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SMP || cpu || bool || ||  
| RESET_ON_INVALID_RAMSTAGE_CACHE || soc/intel/baytrail || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
This option is used to enable certain functions to make coreboot
The baytrail romstage code caches the loaded ramstage program
work correctly on symmetric multi processor (SMP) systems.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AP_SIPI_VECTOR || cpu || hex || ||  
| ENABLE_BUILTIN_COM1 || soc/intel/baytrail || bool || Enable builtin COM1 Serial Port ||  
This must equal address of ap_sipi_vector from bootblock build.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MMX || cpu || bool || ||  
| HAVE_REFCODE_BLOB || soc/intel/baytrail || bool || An external reference code blob should be put into cbfs. ||  
Select MMX in your socket or model Kconfig if your CPU has MMX
The reference code blob will be placed into cbfs.
streaming SIMD instructions. ROMCC can build more efficient
code if it can spill to MMX registers.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SSE || cpu || bool || ||  
| REFCODE_BLOB_FILE || soc/intel/baytrail || string || Path and filename to reference code blob. ||  
Select SSE in your socket or model Kconfig if your CPU has SSE
The path and filename to the file to be added to cbfs.
streaming SIMD instructions. ROMCC can build more efficient
code if it can spill to SSE (aka XMM) registers.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SSE2 || cpu || bool ||  ||  
| SOC_INTEL_QUARK || soc/intel/quark || bool ||  ||  
Select SSE2 in your socket or model Kconfig if your CPU has SSE2
Intel Quark support
streaming SIMD instructions. Some parts of coreboot can be built
with more efficient code if SSE2 instructions are available.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_MICROCODE_CBFS_GENERATE || cpu || bool || Generate from tree ||  
| ENABLE_BUILTIN_HSUART1 || soc/intel/quark || bool || Enable built-in HSUART1 ||  
Select this option if you want microcode updates to be assembled when
The Quark SoC has two HSUART. Choose this option to configure the pads
building coreboot and included in the final image as a separate CBFS
and enable HSUART1, which can be used for the debug console.
file. Microcode will not be hard-coded into ramstage.
 
The microcode file may be removed from the ROM image at a later
time with cbfstool, if desired.
 
If unsure, select this option.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_MICROCODE_CBFS_EXTERNAL || cpu || bool || Include external microcode file ||  
| TTYS0_BASE || soc/intel/quark || hex || HSUART1 Base Address ||  
Select this option if you want to include an external file containing
Memory mapped MMIO of HSUART1.
the CPU microcode. This will be included as a separate file in CBFS.
A word of caution: only select this option if you are sure the
microcode that you have is newer than the microcode shipping with
coreboot.


The microcode file may be removed from the ROM image at a later
||
time with cbfstool, if desired.
|- bgcolor="#eeeeee"
| ENABLE_DEBUG_LED || soc/intel/quark || bool ||  ||
Enable the use of the SD LED for early debugging before serial output
is available.  Setting this LED indicates that control has reached the
desired check point.


If unsure, select "Generate from tree"
||
|- bgcolor="#eeeeee"
| ENABLE_DEBUG_LED_ESRAM || soc/intel/quark || bool || SD LED indicates ESRAM initialized ||
Indicate that ESRAM has been successfully initialized.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_MICROCODE_CBFS_NONE || cpu || bool || Do not include microcode updates ||  
| ENABLE_DEBUG_LED_FINDFSP || soc/intel/quark || bool || SD LED indicates fsp.bin file was found ||  
Select this option if you do not want CPU microcode included in CBFS.
Indicate that fsp.bin was found.
Note that for some CPUs, the microcode is hard-coded into the source
tree and is not loaded from CBFS. In this case, microcode will still
be updated. There is a push to move all microcode to CBFS, but this
change is not implemented for all CPUs.


This option currently applies to:
||
- Intel SandyBridge/IvyBridge
|- bgcolor="#eeeeee"
- VIA Nano
| ENABLE_DEBUG_LED_TEMPRAMINIT || soc/intel/quark || bool || SD LED indicates TempRamInit was successful ||
Indicate that TempRamInit was successful.


Microcode may be added to the ROM image at a later time with cbfstool,
||
if desired.
|- bgcolor="#eeeeee"
| CBFS_SIZE || soc/intel/quark || hex ||  ||
Specify the size of the coreboot file system in the read-only (recovery)
portion of the flash part.  On Quark systems the firmware image stores
more than just coreboot, including:
- The chipset microcode (RMU) binary file located at 0xFFF00000
- Intel Trusted Execution Engine firmware


If unsure, select "Generate from tree"
||
|- bgcolor="#eeeeee"
| ADD_FSP_RAW_BIN || soc/intel/quark || bool || Add the Intel FSP binary to the flash image without relocation ||
Select this option to add an Intel FSP binary to
the resulting coreboot image.


The GOOD:
Note: Without this binary, coreboot builds relying on the FSP
Microcode updates intend to solve issues that have been discovered
will not boot
after CPU production. The expected effect is that systems work as
intended with the updated microcode, but we have also seen cases where
issues were solved by not applying microcode updates.


The BAD:
||
Note that some operating system include these same microcode patches,
|- bgcolor="#eeeeee"
so you may need to also disable microcode updates in your operating
| FSP_FILE || soc/intel/quark || string || Intel FSP binary path and filename ||
system for this option to have an effect.
The path and filename of the Intel FSP binary for this platform.


The UGLY:
||
A word of CAUTION: some CPUs depend on microcode updates to function
|- bgcolor="#eeeeee"
correctly. Not updating the microcode may leave the CPU operating at
| FSP_IMAGE_ID_STRING || soc/intel/quark || string || 8 byte platform string identifying the FSP platform ||
less than optimal performance, or may cause outright hangups.
8 ASCII character byte signature string that will help match the FSP
There are CPUs where coreboot cannot properly initialize the CPU
binary to a supported hardware configuration.
without microcode updates
For example, if running with the factory microcode, some Intel
SandyBridge CPUs may hang when enabling CAR, or some VIA Nano CPUs
will hang when changing the frequency.


Make sure you have a way of flashing the ROM externally before
||
selecting this option.
|- bgcolor="#eeeeee"
| FSP_LOC || soc/intel/quark || hex ||  ||
The location in CBFS that the FSP is located. This must match the
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with Intel's BCT (tool).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CPU_MICROCODE_FILE || cpu || string || Path and filename of CPU microcode ||  
| FSP_ESRAM_LOC || soc/intel/quark || hex || ||  
The path and filename of the file containing the CPU microcode.
The location in ESRAM where a copy of the FSP binary is placed.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || Northbridge ||
| RELOCATE_FSP_INTO_DRAM || soc/intel/quark || bool || Relocate FSP into DRAM ||  
|- bgcolor="#eeeeee"
Relocate the FSP binary into DRAM before the call to SiliconInit.
| VGA_BIOS_ID || northbridge/intel/fsp_sandybridge || string || ||  
This is the default PCI ID for the sandybridge/ivybridge graphics
devices. This string names the vbios ROM in cbfs.  The following
PCI IDs will be remapped to load this ROM:
0x80860102, 0x8086010a, 0x80860112, 0x80860116
0x80860122, 0x80860126, 0x80860166


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || northbridge/intel/fsp_sandybridge || hex || Size of CBFS filesystem in ROM ||  
| ADD_FSP_PDAT_FILE || soc/intel/quark || bool || Should the PDAT binary be added to the flash image? ||  
On Sandybridge and Ivybridge systems the firmware image may
The PDAT file is required for the FSP 1.1 binary
have to store a lot more than just coreboot, including:
- a firmware descriptor
- Intel Management Engine firmware
This option specifies the maximum size of the CBFS portion in the
firmware image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_FILE || northbridge/intel/fsp_sandybridge/fsp || string ||  ||  
| FSP_PDAT_FILE || soc/intel/quark || string ||  ||  
The path and filename of the Intel FSP binary for this platform.
The path and filename of the Intel Galileo platform-data-patch (PDAT)
binary. This binary file is generated by the platform-data-patch.py
script released with the Quark BSP and contains the Ethernet address.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_LOC || northbridge/intel/fsp_sandybridge/fsp || hex || Intel FSP Binary location in CBFS ||  
| FSP_PDAT_LOC || soc/intel/quark || hex || ||  
The location in CBFS that the FSP is located. This must match the
The location in CBFS that the PDAT is located. It must match the
value that is set in the FSP binary.  If the FSP needs to be moved,
PCD PcdPlatformDataBaseAddress of Quark SoC FSP.
rebase the FSP with the Intel's BCT (tool).
 
The Ivy Bridge Processor/Panther Point FSP is built with a preferred
base address of 0xFFF80000


||
||
|- bgcolor="#eeeeee"
| ADD_RMU_FILE || soc/intel/quark || bool || Should the RMU binary be added to the flash image? ||
The RMU file is required to get the chip out of reset.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || northbridge/intel/nehalem || hex || Size of CBFS filesystem in ROM ||  
| RMU_FILE || soc/intel/quark || string || ||  
On Nehalem systems the firmware image has to
The path and filename of the Intel Quark RMU binary.
store a lot more than just coreboot, including:
- a firmware descriptor
- Intel Management Engine firmware
This option allows to limit the size of the CBFS portion in the
firmware image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || northbridge/intel/gm45 || hex || Size of CBFS filesystem in ROM ||  
| RMU_LOC || soc/intel/quark || hex || ||  
On GM45 systems the firmware image may
The location in CBFS that the RMU is located. It must match the
store a lot more than just coreboot, including:
strap-determined base address.
- a firmware descriptor
- Intel Management Engine firmware
This option allows to limit the size of the CBFS portion in the
firmware image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SDRAMPWR_4DIMM || northbridge/intel/i440bx || bool ||  ||  
| SOC_INTEL_COMMON || soc/intel/common || bool ||  ||  
This option affects how the SDRAMC register is programmed.
common code for Intel SOCs
Memory clock signals will not be routed properly if this option
is set wrong.


If your board has 4 DIMM slots, you must use select this option, in
||
your Kconfig file of the board. On boards with 3 DIMM slots,
|- bgcolor="#eeeeee"
do _not_ select this option.
| SOC_SETS_MTRRS || soc/intel/common || bool ||  ||
The SoC needs uses different access methods for reading and writing
the MTRRs. Use SoC specific routines to handle the MTRR access.


||
|- bgcolor="#eeeeee"
| MMA || soc/intel/common || bool || enable MMA (Memory Margin Analysis) support ||
Set this option to y to enable MMA (Memory Margin Analysis) support


||
||
|- bgcolor="#eeeeee"
| SOC_INTEL_BROADWELL || soc/intel/broadwell || bool ||  ||
Intel Broadwell and Haswell ULT support.
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_SIZE || northbridge/intel/haswell || hex ||  ||  
| DCACHE_RAM_SIZE || soc/intel/broadwell || hex ||  ||  
The size of the cache-as-ram region required during bootblock
The size of the cache-as-ram region required during bootblock
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
Line 1,194: Line 1,158:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_MRC_VAR_SIZE || northbridge/intel/haswell || hex ||  ||  
| DCACHE_RAM_MRC_VAR_SIZE || soc/intel/broadwell || hex ||  ||  
The amount of cache-as-ram region required by the reference code.
The amount of cache-as-ram region required by the reference code.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || northbridge/intel/haswell || hex ||  ||  
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || soc/intel/broadwell || hex ||  ||  
The amount of anticipated stack usage from the data cache
The amount of anticipated stack usage from the data cache
during pre-ram rom stage execution.
during pre-ram rom stage execution.
Line 1,205: Line 1,169:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_MRC || northbridge/intel/haswell || bool || Add a System Agent binary ||  
| HAVE_MRC || soc/intel/broadwell || bool || Add a Memory Reference Code binary ||  
Select this option to add a System Agent binary to
Select this option to add a Memory Reference Code binary to
the resulting coreboot image.
the resulting coreboot image.


Line 1,213: Line 1,177:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_FILE || northbridge/intel/haswell || string || Intel System Agent path and filename ||  
| MRC_FILE || soc/intel/broadwell || string || Intel Memory Reference Code path and filename ||  
The path and filename of the file to use as System Agent
The filename of the file to use as Memory Reference Code binary.
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || northbridge/intel/haswell || hex || Size of CBFS filesystem in ROM ||
| PRE_GRAPHICS_DELAY || soc/intel/broadwell || int || Graphics initialization delay in ms ||  
On Haswell 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.
 
||
|- bgcolor="#eeeeee"
| PRE_GRAPHICS_DELAY || northbridge/intel/haswell || int || Graphics initialization delay in ms ||  
On some systems, coreboot boots so fast that connected monitors
On some systems, coreboot boots so fast that connected monitors
(mostly TVs) won't be able to wake up fast enough to talk to the
(mostly TVs) won't be able to wake up fast enough to talk to the
Line 1,238: Line 1,190:
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_MRC || northbridge/intel/sandybridge || bool || Add a System Agent binary ||  
| RESET_ON_INVALID_RAMSTAGE_CACHE || soc/intel/broadwell || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
Select this option to add a System Agent binary to
The romstage code caches the loaded ramstage program in SMM space.
the resulting coreboot image.
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.


Note: Without this binary coreboot will not work
||
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || soc/intel/broadwell || bool ||  ||
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_FILE || northbridge/intel/sandybridge || string || Intel System Agent path and filename ||  
| HAVE_REFCODE_BLOB || soc/intel/broadwell || bool || An external reference code blob should be put into cbfs. ||  
The path and filename of the file to use as System Agent
The reference code blob will be placed into cbfs.
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || northbridge/intel/sandybridge || hex || Size of CBFS filesystem in ROM ||  
| REFCODE_BLOB_FILE || soc/intel/broadwell || string || Path and filename to reference code blob. ||  
On Sandybridge and Ivybridge systems the firmware image has to
The path and filename to the file to be added to cbfs.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| OVERRIDE_CLOCK_DISABLE || northbridge/intel/i945 || bool ||  ||  
| SOC_INTEL_SKYLAKE || soc/intel/skylake || bool ||  ||  
Usually system firmware turns off system memory clock
Intel Skylake support
signals to unused SO-DIMM slots to reduce EMI and power
consumption.
However, some boards do not like unused clock signals to
be disabled.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAXIMUM_SUPPORTED_FREQUENCY || northbridge/intel/i945 || int || ||  
| DCACHE_RAM_SIZE || soc/intel/skylake || hex || Length in bytes of cache-as-RAM ||  
If non-zero, this designates the maximum DDR frequency
The size of the cache-as-ram region required during bootblock
the board supports, despite what the chipset should be
and/or romstage.
capable of.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CHECK_SLFRCS_ON_RESUME || northbridge/intel/i945 || int ||  ||  
| EXCLUDE_NATIVE_SD_INTERFACE || soc/intel/skylake || bool ||  ||  
On some boards it may be neccessary to hard reset early
If you set this option to n, will not use native SD controller.
during resume from S3 if the SLFRCS register indicates that
a memory channel is not guaranteed to be in self-refresh.
On other boards the check always creates a false positive,
effectively making it impossible to resume.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SET_TSEG_1MB || northbridge/intel/fsp_rangeley || bool || 1 MB ||  
| MONOTONIC_TIMER_MSR || soc/intel/skylake || hex || ||  
Set the TSEG area to 1 MB.
Provide a monotonic timer using the 24MHz MSR counter.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SET_TSEG_2MB || northbridge/intel/fsp_rangeley || bool || 2 MB ||  
| PRE_GRAPHICS_DELAY || soc/intel/skylake || int || Graphics initialization delay in ms ||  
Set the TSEG area to 2 MB.
On some systems, coreboot boots so fast that connected monitors
(mostly TVs) won't be able to wake up fast enough to talk to the
VBIOS. On those systems we need to wait for a bit before executing
the VBIOS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SET_TSEG_4MB || northbridge/intel/fsp_rangeley || bool || 4 MB ||  
| SERIRQ_CONTINUOUS_MODE || soc/intel/skylake || bool || ||  
Set the TSEG area to 4 MB.
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SET_TSEG_8MB || northbridge/intel/fsp_rangeley || bool || 8 MB ||  
| NHLT_DMIC_2CH || soc/intel/skylake || bool || ||  
Set the TSEG area to 8 MB.
Include DSP firmware settings for 2 channel DMIC array.
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_FILE || northbridge/intel/fsp_rangeley/fsp || string ||  ||  
| NHLT_DMIC_4CH || soc/intel/skylake || bool ||  ||  
The path and filename of the Intel FSP binary for this platform.
Include DSP firmware settings for 4 channel DMIC array.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_LOC || northbridge/intel/fsp_rangeley/fsp || hex ||  ||  
| NHLT_NAU88L25 || soc/intel/skylake || bool ||  ||  
The location in CBFS that the FSP is located. This must match the
Include DSP firmware settings for nau88l25 headset codec.
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with Intel's BCT (tool).


The Rangeley FSP is built with a preferred base address of 0xFFF80000
||
|- bgcolor="#eeeeee"
| NHLT_MAX98357 || soc/intel/skylake || bool ||  ||
Include DSP firmware settings for max98357 amplifier.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| REDIRECT_NBCIMX_TRACE_TO_SERIAL || northbridge/amd/cimx/rd890 || bool || Redirect AMD Northbridge CIMX Trace to serial console ||  
| NHLT_SSM4567 || soc/intel/skylake || bool || ||  
This Option allows you to redirect the AMD Northbridge CIMX
Include DSP firmware settings for ssm4567 smart amplifier.
Trace debug information to the serial console.


Warning: Only enable this option when debuging or tracing AMD CIMX code.
||
|- bgcolor="#eeeeee"
| SKIP_FSP_CAR || soc/intel/skylake || bool || Skip cache as RAM setup in FSP ||
Skip Cache as RAM setup in FSP.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || northbridge/amd/pi/00630F01 || string || ||  
| CYGNUS_DDR_AUTO_SELF_REFRESH_ENABLE || soc/broadcom/cygnus || bool || Enable DDR auto self-refresh ||  
The default VGA BIOS PCI vendor/device ID should be set to the
Warning: M0 expects that auto self-refresh is enabled. Modify
result of the map_oprom_vendev() function in northbridge.c.
with caution.
 


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || northbridge/amd/pi/00730F01 || string || ||  
| DEBUG_DRAM || soc/mediatek/mt8173 || bool || Output verbose DRAM related debug message ||  
The default VGA BIOS PCI vendor/device ID should be set to the
This option enables additional DRAM related debug messages.
result of the map_oprom_vendev() function in northbridge.c.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || northbridge/amd/agesa/family16kb || string || ||  
| DEBUG_I2C || soc/mediatek/mt8173 || bool || Output verbose I2C related debug message ||  
The default VGA BIOS PCI vendor/device ID should be set to the
This option enables I2C related debug message.
result of the map_oprom_vendev() function in northbridge.c.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SVI_HIGH_FREQ || northbridge/amd/amdfam10 || bool || ||  
| DEBUG_PMIC || soc/mediatek/mt8173 || bool || Output verbose PMIC related debug message ||  
Select this for boards with a Voltage Regulator able to operate
This option enables PMIC related debug message.
at 3.4 MHz in SVI mode. Ignored unless the AMD CPU is rev C3.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: HyperTransport setup || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SVI_HIGH_FREQ || northbridge/amd/amdfam10 || bool || HyperTransport downlink width ||  
| DEBUG_PMIC_WRAP || soc/mediatek/mt8173 || bool || Output verbose PMIC WRAP related debug message ||  
This option sets the maximum permissible HyperTransport
This option enables PMIC WRAP related debug message.
downlink width.
||
 
|- bgcolor="#eeeeee"
Use of this option will only limit the autodetected HT width.
| BOOTBLOCK_CPU_INIT || soc/marvell/armada38x || string ||  ||
It will not (and cannot) increase the width beyond the autodetected
CPU/SoC-specific bootblock code. This is useful if the
limits.
bootblock must load microcode or copy data from ROM before
 
searching for the bootblock.
This is primarily used to work around poorly designed or laid out HT
traces on certain motherboards.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LIMIT_HT_DOWN_WIDTH_16 || northbridge/amd/amdfam10 || bool || HyperTransport uplink width ||  
| SBL_BLOB || soc/qualcomm/ipq806x || string || file name of the Qualcomm SBL blob ||  
This option sets the maximum permissible HyperTransport
The path and filename of the binary blob containing
uplink width.
ipq806x early initialization code, as supplied by the
 
vendor.
Use of this option will only limit the autodetected HT width.
It will not (and cannot) increase the width beyond the autodetected
limits.
 
This is primarily used to work around poorly designed or laid out HT
traces on certain motherboards.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || Southbridge ||
| || || (comment) || || CPU ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_CMC || southbridge/intel/sch || bool || Add a CMC state machine binary ||  
| RESET_ON_INVALID_RAMSTAGE_CACHE || cpu/intel/haswell || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
Select this option to add a CMC state machine binary to
The haswell romstage code caches the loaded ramstage program
the resulting coreboot image.
in SMM space. On S3 wake the romstage will copy over a fresh
 
ramstage that was cached in the SMM space. This option determines
Note: Without this binary coreboot will not work
the action to take when the ramstage cache is invalid. If selected
the system will reset otherwise the ramstage will be reloaded from
cbfs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CMC_FILE || southbridge/intel/sch || string || Intel CMC path and filename ||  
| CPU_INTEL_FIRMWARE_INTERFACE_TABLE || cpu/intel/fit || None || ||  
The path and filename of the file to use as CMC state machine
This option selects building a Firmware Interface Table (FIT).
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/bd82x6x || bool ||  ||  
| CPU_INTEL_NUM_FIT_ENTRIES || cpu/intel/fit || int ||  ||  
If you set this option to y, the serial IRQ machine will be
This option selects the number of empty entries in the FIT table.
operated in continuous mode.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || southbridge/intel/bd82x6x || bool || Build with a fake IFD ||  
| CPU_INTEL_TURBO_NOT_PACKAGE_SCOPED || cpu/intel/turbo || None || ||  
If you don't have an Intel Firmware Descriptor (ifd.bin) for your
This option indicates that the turbo mode setting is not package
board, you can select this option and coreboot will build without it.
scoped. i.e. enable_turbo() needs to be called on not just the bsp
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


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_GBE_BIN || southbridge/intel/bd82x6x || bool || Add gigabit ethernet firmware ||  
| GEODE_VSA_FILE || cpu/amd/geode_gx2 || bool || Add a VSA image ||  
The integrated gigabit ethernet controller needs a firmware file.
Select this option if you have an AMD Geode GX2 vsa that you would
Select this if you are going to use the PCH integrated controller
like to add to your ROM.
and have the firmware.
 
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_ME_BIN || southbridge/intel/bd82x6x || bool || Add Intel Management Engine firmware ||  
| VSA_FILENAME || cpu/amd/geode_gx2 || string || AMD Geode GX2 VSA path and filename ||  
The Intel processor in the selected system requires a special firmware
The path and filename of the file to use as VSA.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || southbridge/intel/bd82x6x || bool || Lock Management Engine section ||  
| GEODE_VSA_FILE || cpu/amd/geode_lx || bool || Add a VSA image ||  
The Intel Management Engine supports preventing write accesses
Select this option if you have an AMD Geode LX vsa that you would
from the host to the Management Engine section in the firmware
like to add to your ROM.
descriptor. If the ME section is locked, it can only be overwritten
with an external SPI flash programmer. You will want this if you
want to increase security of your ROM image once you are sure
that the ME firmware is no longer going to change.


If unsure, say N.
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_SPI_ON_RESUME || southbridge/intel/bd82x6x || bool || Lock all flash ROM sections on S3 resume ||  
| VSA_FILENAME || cpu/amd/geode_lx || string || AMD Geode LX VSA path and filename ||  
If the flash ROM shall be protected against write accesses from the
The path and filename of the file to use as VSA.
operating system (OS), the locking procedure has to be repeated after
each resume from S3. Select this if you never want to update the flash
ROM from within your OS. Notice: Even with this option, the write lock
has still to be enabled on the normal boot path (e.g. by the payload).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| INTEL_LYNXPOINT_LP || southbridge/intel/lynxpoint || bool ||  ||  
| XIP_ROM_SIZE || cpu/amd/agesa || hex ||  ||  
Set this option to y for Lynxpont LP (Haswell ULT).
Overwride the default write through caching size as 1M Bytes.
On some AMD platforms, one socket supports 2 or more kinds of
processor family, compiling several CPU families agesa code
will increase the romstage size.
In order to execute romstage in place on the flash ROM,
more space is required to be set as write through caching.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/lynxpoint || bool || ||  
| REDIRECT_IDS_HDT_CONSOLE_TO_SERIAL || cpu/amd/agesa/family10 || bool || Redirect AGESA IDS_HDT_CONSOLE to serial console ||  
If you set this option to y, the serial IRQ machine will be
This Option allows you to redirect the AMD AGESA IDS_HDT_CONSOLE debug information to the serial console.
operated in continuous mode.
 
Warning: Only enable this option when debuging or tracing AMD AGESA code.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || southbridge/intel/lynxpoint || bool || Build with a fake IFD ||  
| CPU_AMD_SOCKET_G34 || cpu/amd/agesa/family15 || bool || ||  
If you don't have an Intel Firmware Descriptor (ifd.bin) for your
AMD G34 Socket
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


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_ME_BIN || southbridge/intel/lynxpoint || bool || Add Intel Management Engine firmware ||  
| CPU_AMD_SOCKET_C32 || cpu/amd/agesa/family15 || bool || ||  
The Intel processor in the selected system requires a special firmware
AMD C32 Socket
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ME_MBP_CLEAR_LATE || southbridge/intel/lynxpoint || bool || Defer wait for ME MBP Cleared ||  
| CPU_AMD_SOCKET_AM3R2 || cpu/amd/agesa/family15 || bool || ||  
If you set this option to y, the Management Engine driver
AMD AM3r2 Socket
will defer waiting for the MBP Cleared indicator until the
finalize step.  This can speed up boot time if the ME takes
a long time to indicate this status.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FINALIZE_USB_ROUTE_XHCI || southbridge/intel/lynxpoint || bool || Route all ports to XHCI controller in finalize step ||  
| REDIRECT_IDS_HDT_CONSOLE_TO_SERIAL || cpu/amd/agesa/family15 || bool || Redirect AGESA IDS_HDT_CONSOLE to serial console ||  
If you set this option to y, the USB ports will be routed
This Option allows you to redirect the AMD AGESA IDS_HDT_CONSOLE debug information to the serial console.
to the XHCI controller during the finalize SMM callback.


||
Warning: Only enable this option when debuging or tracing AMD AGESA code.
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || southbridge/intel/lynxpoint || bool || Lock Management Engine section ||
The Intel Management Engine supports preventing write accesses
from the host to the Management Engine section in the firmware
descriptor. If the ME section is locked, it can only be overwritten
with an external SPI flash programmer. You will want this if you
want to increase security of your ROM image once you are sure
that the ME firmware is no longer going to change.
 
If unsure, say N.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/fsp_bd82x6x || bool ||  ||  
| FORCE_AM1_SOCKET_SUPPORT || cpu/amd/agesa/family16kb || bool ||  ||  
If you set this option to y, the serial IRQ machine will be
Force AGESA to ignore package type mismatch between CPU and northbridge
operated in continuous mode.
in memory code. This enables Socket AM1 support with current AGESA
version for Kabini platform.
Enable this option only if you have Socket AM1 board.
Note that the AGESA release shipped with coreboot does not officially
support the AM1 socket. Selecting this option might damage your hardware.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| INCLUDE_ME || southbridge/intel/fsp_bd82x6x || bool ||  ||  
| XIP_ROM_SIZE || cpu/amd/pi || hex ||  ||  
Include the me.bin and descriptor.bin for Intel PCH.
Overwride the default write through caching size as 1M Bytes.
This is usually required for the PCH.
On some AMD platforms, one socket supports 2 or more kinds of
processor family, compiling several CPU families agesa code
will increase the romstage size.
In order to execute romstage in place on the flash ROM,
more space is required to be set as write through caching.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ME_PATH || southbridge/intel/fsp_bd82x6x || string ||  ||  
| LAPIC_MONOTONIC_TIMER || cpu/x86 || bool ||  ||  
The path of the ME and Descriptor files.
Expose monotonic time using the local apic.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || southbridge/intel/fsp_bd82x6x || bool || Lock Management Engine section ||  
| TSC_CONSTANT_RATE || cpu/x86 || bool || ||  
The Intel Management Engine supports preventing write accesses
This option asserts that the TSC ticks at a known constant rate.
from the host to the Management Engine section in the firmware
Therefore, no TSC calibration is required.
descriptor. If the ME section is locked, it can only be overwritten
with an external SPI flash programmer. You will want this if you
want to increase security of your ROM image once you are sure
that the ME firmware is no longer going to change.


If unsure, say N.
||
|- bgcolor="#eeeeee"
| TSC_MONOTONIC_TIMER || cpu/x86 || bool ||  ||
Expose monotonic time using the TSC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/ibexpeak || bool ||  ||  
| TSC_SYNC_LFENCE || cpu/x86 || bool ||  ||  
If you set this option to y, the serial IRQ machine will be
The CPU driver should select this if the CPU needs
operated in continuous mode.
to execute an lfence instruction in order to synchronize
rdtsc. This is true for all modern AMD CPUs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || southbridge/intel/ibexpeak || bool || Build with a fake IFD ||  
| TSC_SYNC_MFENCE || cpu/x86 || bool || ||  
If you don't have an Intel Firmware Descriptor (ifd.bin) for your
The CPU driver should select this if the CPU needs
board, you can select this option and coreboot will build without it.
to execute an mfence instruction in order to synchronize
Though, the resulting coreboot.rom will not contain all parts required
rdtsc. This is true for all modern Intel CPUs.
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
 


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_ME_BIN || southbridge/intel/ibexpeak || bool || Add Intel Management Engine firmware ||  
| SMM_MODULE_HEAP_SIZE || cpu/x86 || hex || ||  
The Intel processor in the selected system requires a special firmware
This option determines the size of the heap within the SMM handler
for an integrated controller called Management Engine (ME). The ME
modules.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || southbridge/intel/ibexpeak || bool || Lock Management Engine section ||  
| SERIALIZED_SMM_INITIALIZATION || cpu/x86 || bool || ||  
The Intel Management Engine supports preventing write accesses
On some CPUs, there is a race condition in SMM.
from the host to the Management Engine section in the firmware
This can occur when both hyperthreads change SMM state
descriptor. If the ME section is locked, it can only be overwritten
variables in parallel without coordination.
with an external SPI flash programmer. You will want this if you
Setting this option serializes the SMM initialization
want to increase security of your ROM image once you are sure
to avoid an ugly hang in the boot process at the cost
that the ME firmware is no longer going to change.
of a slightly longer boot time.
 
If unsure, say N.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/fsp_rangeley || bool ||  ||  
| X86_AMD_FIXED_MTRRS || cpu/x86 || bool ||  ||  
If you set this option to y, the serial IRQ machine will be
This option informs the MTRR code to use the RdMem and WrMem fields
operated in continuous mode.
in the fixed MTRR MSRs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| INCLUDE_ME || southbridge/intel/fsp_rangeley || bool || Add Intel descriptor.bin file ||  
| PLATFORM_USES_FSP1_0 || cpu/x86 || bool || ||  
Include the descriptor.bin for rangeley.
Selected for Intel processors/platform combinations that use the
Intel Firmware Support Package (FSP) 1.0 for initialization.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ME_PATH || southbridge/intel/fsp_rangeley || string || Path to descriptor.bin file ||  
| PARALLEL_MP || cpu/x86 || bool || ||  
The path of the descriptor.bin file.
This option uses common MP infrastructure for bringing up APs
in parallel. It additionally provides a more flexible mechanism
for sequencing the steps of bringing up the APs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SATA_CONTROLLER_MODE || southbridge/amd/cimx/sb700 || hex ||  ||  
| BACKUP_DEFAULT_SMM_REGION || cpu/x86 || bool ||  ||  
0x0 = Native IDE mode.
The CPU support will select this option if the default SMM region
0x1 = RAID mode.
needs to be backed up for suspend/resume purposes.
0x2 = AHCI mode.
0x3 = Legacy IDE mode.
0x4 = IDE->AHCI mode.
0x5 = AHCI mode as 7804 ID (AMD driver).
0x6 = IDE->AHCI mode as 7804 ID (AMD driver).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIB_ENABLE || southbridge/amd/cimx/sb700 || bool ||  ||  
| MIRROR_PAYLOAD_TO_RAM_BEFORE_LOADING || cpu/x86 || bool ||  ||  
n = Disable PCI Bridge Device 14 Function 4.
On certain platforms a boot speed gain can be realized if mirroring
y = Enable PCI Bridge Device 14 Function 4.
the payload data stored in non-volatile storage. On x86 systems the
payload would typically live in a memory-mapped SPI part. Copying
the SPI contents to RAM before performing the load can speed up
the boot process.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ACPI_SCI_IRQ || southbridge/amd/cimx/sb700 || hex ||  ||  
| BOOT_MEDIA_SPI_BUS || cpu/x86 || int ||  ||  
Set SCI IRQ to 9.
Most x86 systems which boot from SPI flash boot using bus 0.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| REDIRECT_SBCIMX_TRACE_TO_SERIAL || southbridge/amd/cimx/sb700 || bool || Redirect AMD Southbridge CIMX Trace to serial console ||  
| SMP || cpu || bool || ||  
This Option allows you to redirect the AMD Southbridge CIMX Trace
This option is used to enable certain functions to make coreboot
debug information to the serial console.
work correctly on symmetric multi processor (SMP) systems.
 
Warning: Only enable this option when debuging or tracing AMD CIMX code.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_IDE_COMBINED_MODE || southbridge/amd/cimx/sb800 || bool || Enable SATA IDE combined mode ||  
| AP_SIPI_VECTOR || cpu || hex || ||  
If Combined Mode is enabled. IDE controller is exposed and
This must equal address of ap_sipi_vector from bootblock build.
SATA controller has control over Port0 through Port3,
IDE controller has control over Port4 and Port5.
 
If Combined Mode is disabled, IDE controller is hidden and
SATA controller has full control of all 6 Ports when operating in non-IDE mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| IDE_COMBINED_MODE || southbridge/amd/cimx/sb800 || hex || SATA Mode ||  
| MMX || cpu || bool || ||  
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
Select MMX in your socket or model Kconfig if your CPU has MMX
The default is AHCI.
streaming SIMD instructions. ROMCC can build more efficient
code if it can spill to MMX registers.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SB800_SATA_IDE || southbridge/amd/cimx/sb800 || bool || NATIVE ||  
| SSE || cpu || bool || ||  
NATIVE does not require a ROM.
Select SSE in your socket or model Kconfig if your CPU has SSE
streaming SIMD instructions. ROMCC can build more efficient
code if it can spill to SSE (aka XMM) registers.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SB800_SATA_AHCI || southbridge/amd/cimx/sb800 || bool || AHCI ||  
| SSE2 || cpu || bool || ||  
AHCI is the default and may work with or without AHCI ROM. It depends on the payload support.
Select SSE2 in your socket or model Kconfig if your CPU has SSE2
For example, seabios does not require the AHCI ROM.
streaming SIMD instructions. Some parts of coreboot can be built
with more efficient code if SSE2 instructions are available.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SB800_SATA_RAID || southbridge/amd/cimx/sb800 || bool || RAID ||  
| USES_MICROCODE_HEADER_FILES || cpu || bool || ||  
sb800 RAID mode must have the two required ROM files.
This is selected by a board or chipset to set the default for the
microcode source choice to a list of external microcode headers


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RAID_ROM_ID || southbridge/amd/cimx/sb800 || string || RAID device PCI IDs ||  
| CPU_MICROCODE_CBFS_GENERATE || cpu || bool || Generate from tree ||  
1002,4392 for SATA NON-RAID5 module, 1002,4393 for SATA RAID5 mode
Select this option if you want microcode updates to be assembled when
building coreboot and included in the final image as a separate CBFS
file. Microcode will not be hard-coded into ramstage.


||
The microcode file may be removed from the ROM image at a later
|- bgcolor="#eeeeee"
time with cbfstool, if desired.
| RAID_MISC_ROM_POSITION || southbridge/amd/cimx/sb800 || hex || RAID Misc ROM Position ||
The RAID ROM requires that the MISC ROM is located between the range
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
The CONFIG_ROM_SIZE must larger than 0x100000.


||
If unsure, select this option.
|- bgcolor="#eeeeee"
| SB800_IMC_FWM || southbridge/amd/cimx/sb800 || bool || Add IMC firmware ||
Add SB800 / Hudson 1 IMC Firmware to support the onboard fan control.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SB800_FWM_AT_FFFA0000 || southbridge/amd/cimx/sb800 || bool || 0xFFFA0000 ||  
| CPU_MICROCODE_CBFS_EXTERNAL_HEADER || cpu || bool || Include external microcode header files ||  
The IMC and GEC ROMs requires a 'signature' located at one of several
Select this option if you want to include external c header files
fixed locations in memory.  The location used shouldn't matter, just
containing the CPU microcode. This will be included as a separate
select an area that doesn't conflict with anything else.
file in CBFS.


||
A word of caution: only select this option if you are sure the
|- bgcolor="#eeeeee"
microcode that you have is newer than the microcode shipping with
| SB800_FWM_AT_FFF20000 || southbridge/amd/cimx/sb800 || bool || 0xFFF20000 ||
coreboot.
The IMC and GEC ROMs requires a 'signature' located at one of several
fixed locations in memory.  The location used shouldn't matter, just
select an area that doesn't conflict with anything else.


||
The microcode file may be removed from the ROM image at a later
|- bgcolor="#eeeeee"
time with cbfstool, if desired.
| SB800_FWM_AT_FFE20000 || southbridge/amd/cimx/sb800 || bool || 0xFFE20000 ||
The IMC and GEC ROMs requires a 'signature' located at one of several
fixed locations in memory.  The location used shouldn't matter, just
select an area that doesn't conflict with anything else.


||
If unsure, select "Generate from tree"
|- bgcolor="#eeeeee"
| SB800_FWM_AT_FFC20000 || southbridge/amd/cimx/sb800 || bool || 0xFFC20000 ||
The IMC and GEC ROMs requires a 'signature' located at one of several
fixed locations in memory.  The location used shouldn't matter, just
select an area that doesn't conflict with anything else.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SB800_FWM_AT_FF820000 || southbridge/amd/cimx/sb800 || bool || 0xFF820000 ||  
| CPU_MICROCODE_CBFS_NONE || cpu || bool || Do not include microcode updates ||  
The IMC and GEC ROMs requires a 'signature' located at one of several
Select this option if you do not want CPU microcode included in CBFS.
fixed locations in memory. The location used shouldn't matter, just
Note that for some CPUs, the microcode is hard-coded into the source
select an area that doesn't conflict with anything else.
tree and is not loaded from CBFS. In this case, microcode will still
be updated. There is a push to move all microcode to CBFS, but this
change is not implemented for all CPUs.


||
This option currently applies to:
|- bgcolor="#eeeeee"
- Intel SandyBridge/IvyBridge
| EHCI_BAR || southbridge/amd/cimx/sb800 || hex || Fan Control ||
- VIA Nano
Select the method of SB800 fan control to be used.  None would be
for either fixed maximum speed fans connected to the SB800 or for
an external chip controlling the fan speeds.  Manual control sets
up the SB800 fan control registers.  IMC fan control uses the SB800
IMC to actively control the fan speeds.


||
Microcode may be added to the ROM image at a later time with cbfstool,
|- bgcolor="#eeeeee"
if desired.
| SB800_NO_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || None ||
No SB800 Fan control - Do not set up the SB800 fan control registers.


||
If unsure, select "Generate from tree"
|- bgcolor="#eeeeee"
| SB800_MANUAL_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || Manual ||
Configure the SB800 fan control registers in devicetree.cb.


||
The GOOD:
|- bgcolor="#eeeeee"
Microcode updates intend to solve issues that have been discovered
| SB800_IMC_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || IMC Based ||
after CPU production. The expected effect is that systems work as
Set up the SB800 to use the IMC based Fan controller. This requires
intended with the updated microcode, but we have also seen cases where
the IMC rom from AMD. Configure the registers in devicetree.cb.
issues were solved by not applying microcode updates.
 
The BAD:
Note that some operating system include these same microcode patches,
so you may need to also disable microcode updates in your operating
system for this option to have an effect.
 
The UGLY:
A word of CAUTION: some CPUs depend on microcode updates to function
correctly. Not updating the microcode may leave the CPU operating at
less than optimal performance, or may cause outright hangups.
There are CPUs where coreboot cannot properly initialize the CPU
without microcode updates
For example, if running with the factory microcode, some Intel
SandyBridge CPUs may hang when enabling CAR, or some VIA Nano CPUs
will hang when changing the frequency.
 
Make sure you have a way of flashing the ROM externally before
selecting this option.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SATA_CONTROLLER_MODE || southbridge/amd/cimx/sb900 || hex ||  ||  
| CPU_MICROCODE_MULTIPLE_FILES || cpu || bool ||  ||  
0x0 = Native IDE mode.
Select this option to install separate microcode container files into
0x1 = RAID mode.
CBFS instead of using the traditional monolithic microcode file format.
0x2 = AHCI mode.
0x3 = Legacy IDE mode.
0x4 = IDE->AHCI mode.
0x5 = AHCI mode as 7804 ID (AMD driver).
0x6 = IDE->AHCI mode as 7804 ID (AMD driver).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIB_ENABLE || southbridge/amd/cimx/sb900 || bool || ||  
| CPU_MICROCODE_HEADER_FILES || cpu || string || List of space separated microcode header files with the path ||  
n = Disable PCI Bridge Device 14 Function 4.
A list of one or more microcode header files with path from the
y = Enable PCI Bridge Device 14 Function 4.
coreboot directory. These should be separated by spaces.


||
||
||
|- bgcolor="#eeeeee"
| || || (comment) || || Northbridge ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ACPI_SCI_IRQ || southbridge/amd/cimx/sb900 || hex ||  ||  
| OVERRIDE_CLOCK_DISABLE || northbridge/intel/i945 || bool ||  ||  
Set SCI IRQ to 9.
Usually system firmware turns off system memory clock
signals to unused SO-DIMM slots to reduce EMI and power
consumption.
However, some boards do not like unused clock signals to
be disabled.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_XHCI_ENABLE || southbridge/amd/pi/hudson || bool || Enable Hudson XHCI Controller ||  
| MAXIMUM_SUPPORTED_FREQUENCY || northbridge/intel/i945 || int || ||  
The XHCI controller must be enabled and the XHCI firmware
If non-zero, this designates the maximum DDR frequency
must be added in order to have USB 3.0 support configured
the board supports, despite what the chipset should be
by coreboot. The OS will be responsible for enabling the XHCI
capable of.
controller if the the XHCI firmware is available but the
XHCI controller is not enabled by coreboot.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_XHCI_FWM || southbridge/amd/pi/hudson || bool || Add xhci firmware ||  
| CHECK_SLFRCS_ON_RESUME || northbridge/intel/i945 || int || ||  
Add Hudson 2/3/4 XHCI Firmware to support the onboard USB 3.0
On some boards it may be neccessary to hard reset early
during resume from S3 if the SLFRCS register indicates that
a memory channel is not guaranteed to be in self-refresh.
On other boards the check always creates a false positive,
effectively making it impossible to resume.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_IMC_FWM || southbridge/amd/pi/hudson || bool || Add IMC firmware ||  
| USE_NATIVE_RAMINIT || northbridge/intel/sandybridge || bool || Use native raminit ||  
Add Hudson 2/3/4 IMC Firmware to support the onboard fan control
Select if you want to use coreboot implementation of raminit rather than
System Agent/MRC.bin. You should answer Y.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_GEC_FWM || southbridge/amd/pi/hudson || bool || ||  
| MRC_FILE || northbridge/intel/sandybridge || string || Intel System Agent path and filename ||  
Add Hudson 2/3/4 GEC Firmware to support the onboard gigabit Ethernet MAC.
The path and filename of the file to use as System Agent
Must be connected to a Broadcom B50610 or B50610M PHY on the motherboard.
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_FWM_POSITION || southbridge/amd/pi/hudson || hex || Hudson Firmware ROM Position ||  
| DCACHE_RAM_SIZE || northbridge/intel/haswell || hex || ||  
Hudson requires the firmware MUST be located at
The size of the cache-as-ram region required during bootblock
a specific address (ROM start address + 0x20000), otherwise
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
xhci host Controller can not find or load the xhci firmware.
must add up to a power of 2.


The firmware start address is dependent on the ROM chip size.
The default offset is 0x20000 from the ROM start address, namely
0xFFF20000 if flash chip size is 1M
0xFFE20000 if flash chip size is 2M
0xFFC20000 if flash chip size is 4M
0xFF820000 if flash chip size is 8M
0xFF020000 if flash chip size is 16M
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_SATA_MODE || southbridge/amd/pi/hudson || int || SATA Mode ||  
| DCACHE_RAM_MRC_VAR_SIZE || northbridge/intel/haswell || hex || ||  
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
The amount of cache-as-ram region required by the reference code.
The default is NATIVE.
0: NATIVE mode does not require a ROM.
1: RAID mode must have the two ROM files.
2: AHCI may work with or without AHCI ROM. It depends on the payload support.
For example, seabios does not require the AHCI ROM.
3: LEGACY IDE
4: IDE to AHCI
5: AHCI7804: ROM Required, and AMD driver required in the OS.
6: IDE to AHCI7804: ROM Required, and AMD driver required in the OS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || NATIVE ||
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || northbridge/intel/haswell || hex || ||  
|- bgcolor="#eeeeee"
The amount of anticipated stack usage from the data cache
| || || (comment) || || RAID ||
during pre-ram rom stage execution.
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI ||
|- bgcolor="#eeeeee"
| || || (comment) || || LEGACY IDE ||
|- bgcolor="#eeeeee"
| || || (comment) || || IDE to AHCI ||
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI7804 ||
|- bgcolor="#eeeeee"
| || || (comment) || || IDE to AHCI7804 ||
|- bgcolor="#eeeeee"
| RAID_ROM_ID || southbridge/amd/pi/hudson || string || RAID device PCI IDs ||  
1022,7802 for SATA NON-RAID5 module, 1022,7803 for SATA RAID5 mode


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RAID_MISC_ROM_POSITION || southbridge/amd/pi/hudson || hex || RAID Misc ROM Position ||  
| HAVE_MRC || northbridge/intel/haswell || bool || Add a System Agent binary ||  
The RAID ROM requires that the MISC ROM is located between the range
Select this option to add a System Agent binary to
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
the resulting coreboot image.
The CONFIG_ROM_SIZE must be larger than 0x100000.
 
Note: Without this binary coreboot will not work


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_LEGACY_FREE || southbridge/amd/pi/hudson || bool || System is legacy free ||  
| MRC_FILE || northbridge/intel/haswell || string || Intel System Agent path and filename ||  
Select y if there is no keyboard controller in the system.
The path and filename of the file to use as System Agent
This sets variables in AGESA and ACPI.
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AZ_PIN || southbridge/amd/pi/hudson || hex || ||  
| PRE_GRAPHICS_DELAY || northbridge/intel/haswell || int || Graphics initialization delay in ms ||  
bit 1,0 - pin 0
On some systems, coreboot boots so fast that connected monitors
bit 3,2 - pin 1
(mostly TVs) won't be able to wake up fast enough to talk to the
bit 5,4 - pin 2
VBIOS. On those systems we need to wait for a bit before executing
bit 7,6 - pin 3
the VBIOS.
||
|- bgcolor="#eeeeee"
| EXT_CONF_SUPPORT || southbridge/amd/rs690 || bool ||  ||
Select if RS690 should be setup to support MMCONF.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_XHCI_ENABLE || southbridge/amd/agesa/hudson || bool || Enable Hudson XHCI Controller ||  
| VGA_BIOS_ID || northbridge/intel/fsp_sandybridge || string || ||  
The XHCI controller must be enabled and the XHCI firmware
This is the default PCI ID for the sandybridge/ivybridge graphics
must be added in order to have USB 3.0 support configured
devices.  This string names the vbios ROM in cbfs. The following
by coreboot. The OS will be responsible for enabling the XHCI
PCI IDs will be remapped to load this ROM:
controller if the the XHCI firmware is available but the
0x80860102, 0x8086010a, 0x80860112, 0x80860116
XHCI controller is not enabled by coreboot.
0x80860122, 0x80860126, 0x80860166


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_XHCI_FWM || southbridge/amd/agesa/hudson || bool || Add xhci firmware ||  
| FSP_FILE || northbridge/intel/fsp_sandybridge/fsp || string || ||  
Add Hudson 2/3/4 XHCI Firmware to support the onboard USB 3.0
The path and filename of the Intel FSP binary for this platform.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_IMC_FWM || southbridge/amd/agesa/hudson || bool || Add imc firmware ||  
| FSP_LOC || northbridge/intel/fsp_sandybridge/fsp || hex || Intel FSP Binary location in CBFS ||  
Add Hudson 2/3/4 IMC Firmware to support the onboard fan control
The location in CBFS that the FSP is located. This must match the
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with the Intel's BCT (tool).
 
The Ivy Bridge Processor/Panther Point FSP is built with a preferred
base address of 0xFFF80000


||
||
|- bgcolor="#eeeeee"
| HUDSON_GEC_FWM || southbridge/amd/agesa/hudson || bool ||  ||
Add Hudson 2/3/4 GEC Firmware to support the onboard gigabit Ethernet MAC.
Must be connected to a Broadcom B50610 or B50610M PHY on the motherboard.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_FWM_POSITION || southbridge/amd/agesa/hudson || hex || Hudson Firmware ROM Position ||  
| SDRAMPWR_4DIMM || northbridge/intel/i440bx || bool || ||  
Hudson requires the firmware MUST be located at
This option affects how the SDRAMC register is programmed.
a specific address (ROM start address + 0x20000), otherwise
Memory clock signals will not be routed properly if this option
xhci host Controller can not find or load the xhci firmware.
is set wrong.
 
If your board has 4 DIMM slots, you must use select this option, in
your Kconfig file of the board. On boards with 3 DIMM slots,
do _not_ select this option.


The firmware start address is dependent on the ROM chip size.
||
The default offset is 0x20000 from the ROM start address, namely
0xFFF20000 if flash chip size is 1M
0xFFE20000 if flash chip size is 2M
0xFFC20000 if flash chip size is 4M
0xFF820000 if flash chip size is 8M
0xFF020000 if flash chip size is 16M
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HUDSON_SATA_MODE || southbridge/amd/agesa/hudson || int || SATA Mode ||  
| SET_TSEG_1MB || northbridge/intel/fsp_rangeley || bool || 1 MB ||  
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
Set the TSEG area to 1 MB.
The default is NATIVE.
0: NATIVE mode does not require a ROM.
1: RAID mode must have the two ROM files.
2: AHCI may work with or without AHCI ROM. It depends on the payload support.
For example, seabios does not require the AHCI ROM.
3: LEGACY IDE
4: IDE to AHCI
5: AHCI7804: ROM Required, and AMD driver required in the OS.
6: IDE to AHCI7804: ROM Required, and AMD driver required in the OS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || NATIVE ||
| SET_TSEG_2MB || northbridge/intel/fsp_rangeley || bool || 2 MB ||  
Set the TSEG area to 2 MB.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || RAID ||
| SET_TSEG_4MB || northbridge/intel/fsp_rangeley || bool || 4 MB ||  
Set the TSEG area to 4 MB.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI ||
| SET_TSEG_8MB || northbridge/intel/fsp_rangeley || bool || 8 MB ||  
Set the TSEG area to 8 MB.
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || LEGACY IDE ||
| FSP_FILE || northbridge/intel/fsp_rangeley/fsp || string || ||  
|- bgcolor="#eeeeee"
The path and filename of the Intel FSP binary for this platform.
| || || (comment) || || IDE to AHCI ||
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI7804 ||
|- bgcolor="#eeeeee"
| || || (comment) || || IDE to AHCI7804 ||
|- bgcolor="#eeeeee"
| RAID_ROM_ID || southbridge/amd/agesa/hudson || string || RAID device PCI IDs ||  
1022,7802 for SATA NON-RAID5 module, 1022,7803 for SATA RAID5 mode


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RAID_MISC_ROM_POSITION || southbridge/amd/agesa/hudson || hex || RAID Misc ROM Position ||  
| FSP_LOC || northbridge/intel/fsp_rangeley/fsp || hex || ||  
The RAID ROM requires that the MISC ROM is located between the range
The location in CBFS that the FSP is located. This must match the
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
value that is set in the FSP binary.  If the FSP needs to be moved,
The CONFIG_ROM_SIZE must be larger than 0x100000.
rebase the FSP with Intel's BCT (tool).


||
The Rangeley FSP is built with a preferred base address of 0xFFF80000
|- bgcolor="#eeeeee"
| HUDSON_LEGACY_FREE || southbridge/amd/agesa/hudson || bool || System is legacy free ||
Select y if there is no keyboard controller in the system.
This sets variables in AGESA and ACPI.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| AZ_PIN || southbridge/amd/agesa/hudson || hex ||  ||  
| VGA_BIOS_ID || northbridge/amd/pi/00630F01 || string ||  ||  
bit 1,0 - pin 0
The default VGA BIOS PCI vendor/device ID should be set to the
bit 3,2 - pin 1
result of the map_oprom_vendev() function in northbridge.c.
bit 5,4 - pin 2
 
bit 7,6 - pin 3
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EHCI_BAR || southbridge/amd/sb600 || hex || SATA Mode ||  
| VGA_BIOS_ID || northbridge/amd/pi/00730F01 || string || ||  
Select the mode in which SATA should be driven. IDE or AHCI.
The default VGA BIOS PCI vendor/device ID should be set to the
The default is IDE.
result of the map_oprom_vendev() function in northbridge.c.
 
config SATA_MODE_IDE
bool "IDE"


config SATA_MODE_AHCI
bool "AHCI"
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || Super I/O ||
| VGA_BIOS_ID || northbridge/amd/pi/00660F01 || string || ||  
|- bgcolor="#eeeeee"
The default VGA BIOS PCI vendor/device ID should be set to the
| || || (comment) || || Embedded Controllers ||
result of the map_oprom_vendev() function in northbridge.c.
|- bgcolor="#eeeeee"
| EC_ACPI || ec/acpi || bool ||  ||
ACPI Embedded Controller interface. Mostly found in laptops.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_QUANTA_IT8518 || ec/quanta/it8518 || bool || ||  
| REDIRECT_NBCIMX_TRACE_TO_SERIAL || northbridge/amd/cimx/rd890 || bool || Redirect AMD Northbridge CIMX Trace to serial console ||  
Interface to QUANTA IT8518 Embedded Controller.
This Option allows you to redirect the AMD Northbridge CIMX
Trace debug information to the serial console.
 
Warning: Only enable this option when debuging or tracing AMD CIMX code.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_QUANTA_ENE_KB3940Q || ec/quanta/ene_kb3940q || bool ||  ||  
| VGA_BIOS_ID || northbridge/amd/agesa/family16kb || string ||  ||  
Interface to QUANTA ENE KB3940Q Embedded Controller.
The default VGA BIOS PCI vendor/device ID should be set to the
result of the map_oprom_vendev() function in northbridge.c.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_SMSC_MEC1308 || ec/smsc/mec1308 || bool ||  ||  
| SVI_HIGH_FREQ || northbridge/amd/amdfam10 || bool ||  ||  
Shared memory mailbox interface to SMSC MEC1308 Embedded Controller.
Select this for boards with a Voltage Regulator able to operate
at 3.4 MHz in SVI mode. Ignored unless the AMD CPU is rev C3.


||
||
||
|- bgcolor="#6699dd"
! align="left" | Menu: HyperTransport setup || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC || ec/google/chromeec || bool || ||  
| SVI_HIGH_FREQ || northbridge/amd/amdfam10 || bool || HyperTransport downlink width ||  
Google's Chrome EC
This option sets the maximum permissible HyperTransport
downlink width.
 
Use of this option will only limit the autodetected HT width.
It will not (and cannot) increase the width beyond the autodetected
limits.
 
This is primarily used to work around poorly designed or laid out HT
traces on certain motherboards.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_ACPI_MEMMAP || ec/google/chromeec || bool || ||  
| LIMIT_HT_DOWN_WIDTH_16 || northbridge/amd/amdfam10 || bool || HyperTransport uplink width ||  
When defined, ACPI accesses EC memmap data on ports 66h/62h. When
This option sets the maximum permissible HyperTransport
not defined, the memmap data is instead accessed on 900h-9ffh via
uplink width.
the LPC bus.
 
Use of this option will only limit the autodetected HT width.
It will not (and cannot) increase the width beyond the autodetected
limits.
 
This is primarily used to work around poorly designed or laid out HT
traces on certain motherboards.


||
||
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_I2C || ec/google/chromeec || bool ||  ||
Google's Chrome EC via I2C bus.


||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_I2C_PROTO3 || ec/google/chromeec || bool || ||  
| || || (comment) || || Southbridge ||
Use only proto3 for i2c EC communication.
|- bgcolor="#eeeeee"
| HAVE_CMC || southbridge/intel/sch || bool || Add a CMC state machine binary ||  
Select this option to add a CMC state machine binary to
the resulting coreboot image.
 
Note: Without this binary coreboot will not work


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_LPC || ec/google/chromeec || bool || ||  
| CMC_FILE || southbridge/intel/sch || string || Intel CMC path and filename ||  
Google Chrome EC via LPC bus.
The path and filename of the file to use as CMC state machine
binary.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_MEC || ec/google/chromeec || bool ||  ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/ibexpeak || bool ||  ||  
Microchip EC variant for LPC register access.
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_SPI || ec/google/chromeec || bool ||  ||  
| INTEL_LYNXPOINT_LP || southbridge/intel/lynxpoint || bool ||  ||  
Google's Chrome EC via SPI bus.
Set this option to y for Lynxpont LP (Haswell ULT).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_SPI_WAKEUP_DELAY_US || ec/google/chromeec || int ||  ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/lynxpoint || bool ||  ||  
Force delay after asserting /CS to allow EC to wakeup.
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_COMPAL_ENE932 || ec/compal/ene932 || bool || ||  
| ME_MBP_CLEAR_LATE || southbridge/intel/lynxpoint || bool || Defer wait for ME MBP Cleared ||  
Interface to COMPAL ENE932 Embedded Controller.
If you set this option to y, the Management Engine driver
will defer waiting for the MBP Cleared indicator until the
finalize step.  This can speed up boot time if the ME takes
a long time to indicate this status.


||
||
|- bgcolor="#eeeeee"
| FINALIZE_USB_ROUTE_XHCI || southbridge/intel/lynxpoint || bool || Route all ports to XHCI controller in finalize step ||
If you set this option to y, the USB ports will be routed
to the XHCI controller during the finalize SMM callback.
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EC_KONTRON_IT8516E || ec/kontron/it8516e || bool ||  ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/bd82x6x || bool ||  ||  
Kontron uses an ITE IT8516E on the KTQM77. Its firmware might
If you set this option to y, the serial IRQ machine will be
come from Fintek (mentioned as Finte*c* somewhere in their Linux
operated in continuous mode.
driver).
The KTQM77 is an embedded board and the IT8516E seems to be
only used for fan control and GPIO.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || SoC ||
| LOCK_SPI_ON_RESUME_RO || southbridge/intel/bd82x6x || bool || Lock all flash ROM sections on S3 resume ||  
|- bgcolor="#eeeeee"
If the flash ROM shall be protected against write accesses from the
| BOOTBLOCK_CPU_INIT || soc/nvidia/tegra124 || string ||  ||
operating system (OS), the locking procedure has to be repeated after
CPU/SoC-specific bootblock code. This is useful if the
each resume from S3. Select this if you never want to update the flash
bootblock must load microcode or copy data from ROM before
ROM from within your OS. Notice: Even with this option, the write lock
searching for the bootblock.
has still to be enabled on the normal boot path (e.g. by the payload).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAINBOARD_DO_DSI_INIT || soc/nvidia/tegra132 || bool || Use dsi graphics interface ||  
| LOCK_SPI_ON_RESUME_NO_ACCESS || southbridge/intel/bd82x6x || bool || Lock and disable reads all flash ROM sections on S3 resume ||  
Initialize dsi display
If the flash ROM shall be protected against all accesses from the
operating system (OS), the locking procedure has to be repeated after
each resume from S3. Select this if you never want to update the flash
ROM from within your OS. Notice: Even with this option, the lock
has still to be enabled on the normal boot path (e.g. by the payload).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAINBOARD_DO_SOR_INIT || soc/nvidia/tegra132 || bool || Use dp graphics interface ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/fsp_bd82x6x || bool || ||  
Initialize dp display
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOTBLOCK_CPU_INIT || soc/nvidia/tegra132 || string ||  ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/fsp_rangeley || bool ||  ||  
CPU/SoC-specific bootblock code. This is useful if the
If you set this option to y, the serial IRQ machine will be
bootblock must load microcode or copy data from ROM before
operated in continuous mode.
searching for the bootblock.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MTS_DIRECTORY || soc/nvidia/tegra132 || string || Directory where MTS microcode files are located ||  
| IFD_BIN_PATH || southbridge/intel/fsp_rangeley || string || ||  
Path to directory where MTS microcode files are located.
The path and filename to the descriptor.bin file.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| TRUSTZONE_CARVEOUT_SIZE_MB || soc/nvidia/tegra132 || hex || Size of Trust Zone region ||  
| SERIRQ_CONTINUOUS_MODE || southbridge/intel/fsp_i89xx || bool || ||  
Size of Trust Zone area in MiB to reserve in memory map.
If you set this option to y, the serial IRQ machine will be
operated in continuous mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOTROM_SDRAM_INIT || soc/nvidia/tegra132 || bool || SoC BootROM does SDRAM init with full BCT ||  
| HUDSON_XHCI_ENABLE || southbridge/amd/pi/hudson || bool || Enable Hudson XHCI Controller ||  
Use during Ryu LPDDR3 bringup
The XHCI controller must be enabled and the XHCI firmware
must be added in order to have USB 3.0 support configured
by coreboot. The OS will be responsible for enabling the XHCI
controller if the the XHCI firmware is available but the
XHCI controller is not enabled by coreboot.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CYGNUS_DDR_AUTO_SELF_REFRESH_ENABLE || soc/broadcom/cygnus || bool || Enable DDR auto self-refresh ||  
| HUDSON_XHCI_FWM || southbridge/amd/pi/hudson || bool || Add xhci firmware ||  
Warning: M0 expects that auto self-refresh is enabled. Modify
Add Hudson 2/3/4 XHCI Firmware to support the onboard USB 3.0
with caution.
 


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SOC_INTEL_BAYTRAIL || soc/intel/baytrail || bool || ||  
| HUDSON_IMC_FWM || southbridge/amd/pi/hudson || bool || Add IMC firmware ||  
Bay Trail M/D part support.
Add Hudson 2/3/4 IMC Firmware to support the onboard fan control


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_MRC || soc/intel/baytrail || bool || Add a Memory Reference Code binary ||  
| HUDSON_GEC_FWM || southbridge/amd/pi/hudson || bool || ||  
Select this option to add a blob containing
Add Hudson 2/3/4 GEC Firmware to support the onboard gigabit Ethernet MAC.
memory reference code.
Must be connected to a Broadcom B50610 or B50610M PHY on the motherboard.
Note: Without this binary coreboot will not work


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_FILE || soc/intel/baytrail || string || Intel memory refeference code path and filename ||  
| HUDSON_FWM_POSITION || southbridge/amd/pi/hudson || hex || Hudson Firmware ROM Position ||  
The path and filename of the file to use as System Agent
Hudson requires the firmware MUST be located at
binary. Note that this points to the sandybridge binary file
a specific address (ROM start address + 0x20000), otherwise
which is will not work, but it serves its purpose to do builds.
xhci host Controller can not find or load the xhci firmware.


The firmware start address is dependent on the ROM chip size.
The default offset is 0x20000 from the ROM start address, namely
0xFFF20000 if flash chip size is 1M
0xFFE20000 if flash chip size is 2M
0xFFC20000 if flash chip size is 4M
0xFF820000 if flash chip size is 8M
0xFF020000 if flash chip size is 16M
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_SIZE || soc/intel/baytrail || hex || ||  
| HUDSON_SATA_MODE || southbridge/amd/pi/hudson || int || SATA Mode ||  
The size of the cache-as-ram region required during bootblock
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
The default is NATIVE.
must add up to a power of 2.
0: NATIVE mode does not require a ROM.
1: RAID mode must have the two ROM files.
2: AHCI may work with or without AHCI ROM. It depends on the payload support.
For example, seabios does not require the AHCI ROM.
3: LEGACY IDE
4: IDE to AHCI
5: AHCI7804: ROM Required, and AMD driver required in the OS.
6: IDE to AHCI7804: ROM Required, and AMD driver required in the OS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_MRC_VAR_SIZE || soc/intel/baytrail || hex || ||  
| || || (comment) || || NATIVE ||
The amount of cache-as-ram region required by the reference code.
|- bgcolor="#eeeeee"
| || || (comment) || || RAID ||
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI ||
|- bgcolor="#eeeeee"
| || || (comment) || || LEGACY IDE ||
|- bgcolor="#eeeeee"
| || || (comment) || || IDE to AHCI ||
|- bgcolor="#eeeeee"
| || || (comment) || || AHCI7804 ||
|- bgcolor="#eeeeee"
| || || (comment) || || IDE to AHCI7804 ||
|- bgcolor="#eeeeee"
| RAID_ROM_ID || southbridge/amd/pi/hudson || string || RAID device PCI IDs ||  
1022,7802 for SATA NON-RAID5 module, 1022,7803 for SATA RAID5 mode


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || soc/intel/baytrail || hex || ||  
| RAID_MISC_ROM_POSITION || southbridge/amd/pi/hudson || hex || RAID Misc ROM Position ||  
The amount of anticipated stack usage from the data cache
The RAID ROM requires that the MISC ROM is located between the range
during pre-RAM ROM stage execution.
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
The CONFIG_ROM_SIZE must be larger than 0x100000.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RESET_ON_INVALID_RAMSTAGE_CACHE || soc/intel/baytrail || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
| HUDSON_LEGACY_FREE || southbridge/amd/pi/hudson || bool || System is legacy free ||  
The baytrail romstage code caches the loaded ramstage program
Select y if there is no keyboard controller in the system.
in SMM space. On S3 wake the romstage will copy over a fresh
This sets variables in AGESA and ACPI.
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || soc/intel/baytrail || hex || Size of CBFS filesystem in ROM ||  
| AZ_PIN || southbridge/amd/pi/hudson || hex || ||  
On Bay Trail systems the firmware image has to store a lot more
bit 1,0 - pin 0
than just coreboot, including:
bit 3,2 - pin 1
- a firmware descriptor
bit 5,4 - pin 2
- Intel Management Engine firmware
bit 7,6 - pin 3
- MRC cache information
This option allows to limit the size of the CBFS portion in the
firmware image.
 
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_BUILTIN_COM1 || soc/intel/baytrail || bool || Enable builtin COM1 Serial Port ||  
| HUDSON_UART || southbridge/amd/pi/hudson || bool || UART controller on Kern ||  
The PMC has a legacy COM1 serial port. Choose this option to
There are two UART controllers in Kern.
configure the pads and enable it. This serial port can be used for
The UART registers are memory-mapped. UART
the debug console.
controller 0 registers range from FEDC_6000h
to FEDC_6FFFh. UART controller 1 registers
range from FEDC_8000h to FEDC_8FFFh.
 
 


||
||
|- bgcolor="#eeeeee"
| HAVE_ME_BIN || soc/intel/baytrail || bool || Add Intel Management Engine firmware ||
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.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || soc/intel/baytrail || bool || Build with a fake IFD ||  
| SATA_CONTROLLER_MODE || southbridge/amd/cimx/sb700 || hex || ||  
If you don't have an Intel Firmware Descriptor (ifd.bin) for your
0x0 = Native IDE mode.
board, you can select this option and coreboot will build without it.
0x1 = RAID mode.
Though, the resulting coreboot.rom will not contain all parts required
0x2 = AHCI mode.
to get coreboot running on your board. You can however write only the
0x3 = Legacy IDE mode.
BIOS section to your board's flash ROM and keep the other sections
0x4 = IDE->AHCI mode.
untouched. Unfortunately the current version of flashrom doesn't
0x5 = AHCI mode as 7804 ID (AMD driver).
support this yet. But there is a patch pending [1].
0x6 = IDE->AHCI mode as 7804 ID (AMD driver).
 
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


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_REFCODE_BLOB || soc/intel/baytrail || bool || An external reference code blob should be put into cbfs. ||  
| PCIB_ENABLE || southbridge/amd/cimx/sb700 || bool || ||  
The reference code blob will be placed into cbfs.
n = Disable PCI Bridge Device 14 Function 4.
y = Enable PCI Bridge Device 14 Function 4.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| REFCODE_BLOB_FILE || soc/intel/baytrail || string || Path and filename to reference code blob. ||  
| ACPI_SCI_IRQ || southbridge/amd/cimx/sb700 || hex || ||  
The path and filename to the file to be added to cbfs.
Set SCI IRQ to 9.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SOC_INTEL_COMMON || soc/intel/common || bool || ||  
| REDIRECT_SBCIMX_TRACE_TO_SERIAL || southbridge/amd/cimx/sb700 || bool || Redirect AMD Southbridge CIMX Trace to serial console ||  
common code for Intel SOCs
This Option allows you to redirect the AMD Southbridge CIMX Trace
debug information to the serial console.
 
Warning: Only enable this option when debuging or tracing AMD CIMX code.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SOC_INTEL_BROADWELL || soc/intel/broadwell || bool || ||  
| ENABLE_IDE_COMBINED_MODE || southbridge/amd/cimx/sb800 || bool || Enable SATA IDE combined mode ||  
Intel Broadwell and Haswell ULT support.
If Combined Mode is enabled. IDE controller is exposed and
SATA controller has control over Port0 through Port3,
IDE controller has control over Port4 and Port5.
 
If Combined Mode is disabled, IDE controller is hidden and
SATA controller has full control of all 6 Ports when operating in non-IDE mode.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_SIZE || soc/intel/broadwell || hex || ||  
| IDE_COMBINED_MODE || southbridge/amd/cimx/sb800 || hex || SATA Mode ||  
The size of the cache-as-ram region required during bootblock
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
and/or romstage. Note DCACHE_RAM_SIZE and DCACHE_RAM_MRC_VAR_SIZE
The default is AHCI.
must add up to a power of 2.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_MRC_VAR_SIZE || soc/intel/broadwell || hex || ||  
| SB800_SATA_IDE || southbridge/amd/cimx/sb800 || bool || NATIVE ||  
The amount of cache-as-ram region required by the reference code.
NATIVE does not require a ROM.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| DCACHE_RAM_ROMSTAGE_STACK_SIZE || soc/intel/broadwell || hex || ||  
| SB800_SATA_AHCI || southbridge/amd/cimx/sb800 || bool || AHCI ||  
The amount of anticipated stack usage from the data cache
AHCI is the default and may work with or without AHCI ROM. It depends on the payload support.
during pre-ram rom stage execution.
For example, seabios does not require the AHCI ROM.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| HAVE_MRC || soc/intel/broadwell || bool || Add a Memory Reference Code binary ||  
| SB800_SATA_RAID || southbridge/amd/cimx/sb800 || bool || RAID ||  
Select this option to add a Memory Reference Code binary to
sb800 RAID mode must have the two required ROM files.
the resulting coreboot image.
 
Note: Without this binary coreboot will not work


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_FILE || soc/intel/broadwell || string || Intel Memory Reference Code path and filename ||  
| RAID_ROM_ID || southbridge/amd/cimx/sb800 || string || RAID device PCI IDs ||  
The filename of the file to use as Memory Reference Code binary.
1002,4392 for SATA NON-RAID5 module, 1002,4393 for SATA RAID5 mode


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || soc/intel/broadwell || hex || Size of CBFS filesystem in ROM ||  
| RAID_MISC_ROM_POSITION || southbridge/amd/cimx/sb800 || hex || RAID Misc ROM Position ||  
The firmware image has to store more than just coreboot, including:
The RAID ROM requires that the MISC ROM is located between the range
- a firmware descriptor
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
- Intel Management Engine firmware
The CONFIG_ROM_SIZE must larger than 0x100000.
- MRC cache information
This option allows to limit the size of the CBFS portion in the
firmware image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PRE_GRAPHICS_DELAY || soc/intel/broadwell || int || Graphics initialization delay in ms ||  
| SB800_IMC_FWM || southbridge/amd/cimx/sb800 || bool || Add IMC firmware ||  
On some systems, coreboot boots so fast that connected monitors
Add SB800 / Hudson 1 IMC Firmware to support the onboard fan control.
(mostly TVs) won't be able to wake up fast enough to talk to the
VBIOS. On those systems we need to wait for a bit before executing
the VBIOS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| RESET_ON_INVALID_RAMSTAGE_CACHE || soc/intel/broadwell || bool || Reset the system on S3 wake when ramstage cache invalid. ||  
| SB800_FWM_AT_FFFA0000 || southbridge/amd/cimx/sb800 || bool || 0xFFFA0000 ||  
The romstage code caches the loaded ramstage program in SMM space.
The IMC and GEC ROMs requires a 'signature' located at one of several
On S3 wake the romstage will copy over a fresh ramstage that was
fixed locations in memory. The location used shouldn't matter, just
cached in the SMM space. This option determines the action to take
select an area that doesn't conflict with anything else.
when the ramstage cache is invalid. If selected the system will
reset otherwise the ramstage will be reloaded from cbfs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SERIRQ_CONTINUOUS_MODE || soc/intel/broadwell || bool ||  ||
| SB800_FWM_AT_FFF20000 || southbridge/amd/cimx/sb800 || bool || 0xFFF20000 ||  
If you set this option to y, the serial IRQ machine will be
The IMC and GEC ROMs requires a 'signature' located at one of several
operated in continuous mode.
fixed locations in memory. The location used shouldn't matter, just
||
select an area that doesn't conflict with anything else.
|- bgcolor="#eeeeee"
| HAVE_ME_BIN || soc/intel/broadwell || bool || Add Intel Management Engine firmware ||  
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.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || soc/intel/broadwell || bool || Build with a fake IFD ||  
| SB800_FWM_AT_FFE20000 || southbridge/amd/cimx/sb800 || bool || 0xFFE20000 ||  
If you don't have an Intel Firmware Descriptor (ifd.bin) for your
The IMC and GEC ROMs requires a 'signature' located at one of several
board, you can select this option and coreboot will build without it.
fixed locations in memory. The location used shouldn't matter, just
Though, the resulting coreboot.rom will not contain all parts required
select an area that doesn't conflict with anything else.
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


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || soc/intel/broadwell || bool || Lock Management Engine section ||  
| SB800_FWM_AT_FFC20000 || southbridge/amd/cimx/sb800 || bool || 0xFFC20000 ||  
The Intel Management Engine supports preventing write accesses
The IMC and GEC ROMs requires a 'signature' located at one of several
from the host to the Management Engine section in the firmware
fixed locations in memory. The location used shouldn't matter, just
descriptor. If the ME section is locked, it can only be overwritten
select an area that doesn't conflict with anything else.
with an external SPI flash programmer. You will want this if you
want to increase security of your ROM image once you are sure
that the ME firmware is no longer going to change.
 
If unsure, say N.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SOC_INTEL_FSP_BAYTRAIL || soc/intel/fsp_baytrail || bool || ||  
| SB800_FWM_AT_FF820000 || southbridge/amd/cimx/sb800 || bool || 0xFF820000 ||  
Bay Trail I part support using the Intel FSP.
The IMC and GEC ROMs requires a 'signature' located at one of several
fixed locations in memory.  The location used shouldn't matter, just
select an area that doesn't conflict with anything else.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SMM_TSEG_SIZE || soc/intel/fsp_baytrail || hex || ||  
| EHCI_BAR || southbridge/amd/cimx/sb800 || hex || Fan Control ||  
This is set by the FSP
Select the method of SB800 fan control to be used.  None would be
for either fixed maximum speed fans connected to the SB800 or for
an external chip controlling the fan speeds.  Manual control sets
up the SB800 fan control registers.  IMC fan control uses the SB800
IMC to actively control the fan speeds.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || soc/intel/fsp_baytrail || string || ||  
| SB800_NO_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || None ||  
This is the default PCI ID for the Bay Trail graphics
No SB800 Fan control - Do not set up the SB800 fan control registers.
devices.  This string names the vbios ROM in cbfs.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || soc/intel/fsp_baytrail || hex || ||  
| SB800_MANUAL_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || Manual ||  
On Bay Trail systems the firmware image has to store a lot more
Configure the SB800 fan control registers in devicetree.cb.
than just coreboot, including:
- a firmware descriptor
- Intel Trusted Execution Engine firmware
This option specifies the maximum size of the CBFS portion in the
firmware image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| INCLUDE_ME || soc/intel/fsp_baytrail || bool || Include the TXE ||  
| SB800_IMC_FAN_CONTROL || southbridge/amd/cimx/sb800 || bool || IMC Based ||  
Build the TXE and descriptor.bin into the ROM imageIf you want to use a
Set up the SB800 to use the IMC based Fan controllerThis requires
descriptor.bin and TXE file from the previous ROM image, you may not want
the IMC rom from AMD. Configure the registers in devicetree.cb.
to build it in here.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ME_PATH || soc/intel/fsp_baytrail || string || Path to ME ||  
| SATA_CONTROLLER_MODE || southbridge/amd/cimx/sb900 || hex || ||  
The path of the TXE and Descriptor files.
0x0 = Native IDE mode.
0x1 = RAID mode.
0x2 = AHCI mode.
0x3 = Legacy IDE mode.
0x4 = IDE->AHCI mode.
0x5 = AHCI mode as 7804 ID (AMD driver).
0x6 = IDE->AHCI mode as 7804 ID (AMD driver).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| LOCK_MANAGEMENT_ENGINE || soc/intel/fsp_baytrail || bool || Lock TXE section ||  
| PCIB_ENABLE || southbridge/amd/cimx/sb900 || bool || ||  
The Intel Trusted Execution Engine supports preventing write accesses
n = Disable PCI Bridge Device 14 Function 4.
from the host to the Management Engine section in the firmware
y = Enable PCI Bridge Device 14 Function 4.
descriptor. If the ME section is locked, it can only be overwritten
with an external SPI flash programmer. You will want this if you
want to increase security of your ROM image once you are sure
that the ME firmware is no longer going to change.
 
If unsure, say N.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_BUILTIN_COM1 || soc/intel/fsp_baytrail || bool || Enable built-in legacy Serial Port ||  
| ACPI_SCI_IRQ || southbridge/amd/cimx/sb900 || hex || ||  
The Baytrail SOC has one legacy serial port. Choose this option to
Set SCI IRQ to 9.
configure the pads and enable it. This serial port can be used for
the debug console.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_FILE || soc/intel/fsp_baytrail/fsp || string || ||  
| EXT_CONF_SUPPORT || southbridge/amd/sr5650 || bool || Enable PCI-E MMCONFIG support ||  
The path and filename of the Intel FSP binary for this platform.
Select to enable PCI-E MMCONFIG support on the SR5650.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_LOC || soc/intel/fsp_baytrail/fsp || hex ||  ||  
| EXT_CONF_SUPPORT || southbridge/amd/rs690 || bool ||  ||  
The location in CBFS that the FSP is located. This must match the
Select if RS690 should be setup to support MMCONF.
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with Intel's BCT (tool).
 
The Bay Trail FSP is built with a preferred base address of
0xFFFC0000.
 
||


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CBFS_SIZE || soc/qualcomm/ipq806x || hex || Size of CBFS filesystem in ROM ||  
| HUDSON_XHCI_ENABLE || southbridge/amd/agesa/hudson || bool || Enable Hudson XHCI Controller ||  
CBFS size needs to match the size of memory allocated to the
The XHCI controller must be enabled and the XHCI firmware
coreboot blob elsewhere in the system. Make sure this config option
must be added in order to have USB 3.0 support configured
is fine tuned in the board config file.
by coreboot. The OS will be responsible for enabling the XHCI
controller if the the XHCI firmware is available but the
XHCI controller is not enabled by coreboot.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SBL_BLOB || soc/qualcomm/ipq806x || string || file name of the Qualcomm SBL blob ||  
| HUDSON_XHCI_FWM || southbridge/amd/agesa/hudson || bool || Add xhci firmware ||  
The path and filename of the binary blob containing
Add Hudson 2/3/4 XHCI Firmware to support the onboard USB 3.0
ipq806x early initialization code, as supplied by the
vendor.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| || || (comment) || || Intel FSP ||
| HUDSON_IMC_FWM || southbridge/amd/agesa/hudson || bool || Add imc firmware ||  
|- bgcolor="#eeeeee"
Add Hudson 2/3/4 IMC Firmware to support the onboard fan control
| HAVE_FSP_BIN || drivers/intel/fsp1_0 || bool || Use Intel Firmware Support Package ||
Select this option to add an Intel FSP binary to
the resulting coreboot image.
 
Note: Without this binary, coreboot builds relying on the FSP
will not boot


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_FILE || drivers/intel/fsp1_0 || string || Intel FSP binary path and filename ||  
| HUDSON_GEC_FWM || southbridge/amd/agesa/hudson || bool || ||  
The path and filename of the Intel FSP binary for this platform.
Add Hudson 2/3/4 GEC Firmware to support the onboard gigabit Ethernet MAC.
Must be connected to a Broadcom B50610 or B50610M PHY on the motherboard.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_LOC || drivers/intel/fsp1_0 || hex || Intel FSP Binary location in CBFS ||  
| HUDSON_FWM_POSITION || southbridge/amd/agesa/hudson || hex || Hudson Firmware ROM Position ||  
The location in CBFS that the FSP is located. This must match the
Hudson requires the firmware MUST be located at
value that is set in the FSP binary.  If the FSP needs to be moved,
a specific address (ROM start address + 0x20000), otherwise
rebase the FSP with Intel's BCT (tool).
xhci host Controller can not find or load the xhci firmware.


The firmware start address is dependent on the ROM chip size.
The default offset is 0x20000 from the ROM start address, namely
0xFFF20000 if flash chip size is 1M
0xFFE20000 if flash chip size is 2M
0xFFC20000 if flash chip size is 4M
0xFF820000 if flash chip size is 8M
0xFF020000 if flash chip size is 16M
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_FSP_FAST_BOOT || drivers/intel/fsp1_0 || bool || Enable Fast Boot ||  
| HUDSON_SATA_MODE || southbridge/amd/agesa/hudson || int || SATA Mode ||  
Enabling this feature will force the MRC data to be cached in NV
Select the mode in which SATA should be driven. NATIVE AHCI, or RAID.
storage to be used for speeding up boot time on future reboots
The default is NATIVE.
and/or power cycles.
0: NATIVE mode does not require a ROM.
1: RAID mode must have the two ROM files.
2: AHCI may work with or without AHCI ROM. It depends on the payload support.
For example, seabios does not require the AHCI ROM.
3: LEGACY IDE
4: IDE to AHCI
5: AHCI7804: ROM Required, and AMD driver required in the OS.
6: IDE to AHCI7804: ROM Required, and AMD driver required in the OS.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ENABLE_MRC_CACHE || drivers/intel/fsp1_0 || bool || ||  
| || || (comment) || || NATIVE ||
Enabling this feature will cause MRC data to be cached in NV storage.
|- bgcolor="#eeeeee"
This can either be used for fast boot, or just because the FSP wants
| || || (comment) || || RAID ||
it to be saved.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_CACHE_SIZE || drivers/intel/fsp1_0 || hex || Fast Boot Data Cache Size ||  
| || || (comment) || || AHCI ||
This is the amount of space in NV storage that is reserved for the
fast boot data cache storage.
 
WARNING: Because this area will be erased and re-written, the size
should be a full sector of the flash ROM chip and nothing else should
be included in CBFS in any sector that the fast boot cache data is in.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| OVERRIDE_CACHE_CACHE_LOC || drivers/intel/fsp1_0 || bool || ||  
| || || (comment) || || LEGACY IDE ||
Selected by the platform to set a new default location for the
MRC/fast boot cache.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_CACHE_LOC_OVERRIDE || drivers/intel/fsp1_0 || hex || ||  
| || || (comment) || || IDE to AHCI ||
Sets the override CBFS location of the MRC/fast boot cache.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MRC_CACHE_LOC || drivers/intel/fsp1_0 || hex || Fast Boot Data Cache location in CBFS ||  
| || || (comment) || || AHCI7804 ||
The location in CBFS for the MRC data to be cached.
|- bgcolor="#eeeeee"
 
| || || (comment) || || IDE to AHCI7804 ||
WARNING: This should be on a sector boundary of the BIOS ROM chip
and nothing else should be included in that sector, or IT WILL BE
ERASED.
 
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VIRTUAL_ROM_SIZE || drivers/intel/fsp1_0 || hex || Virtual ROM Size ||  
| RAID_ROM_ID || southbridge/amd/agesa/hudson || string || RAID device PCI IDs ||  
This is used to calculate the offset of the MRC data cache in NV
1022,7802 for SATA NON-RAID5 module, 1022,7803 for SATA RAID5 mode
Storage for fast boot.  If in doubt, leave this set to the default
which sets the virtual size equal to the ROM size.
 
Example: Cougar Canyon 2 has two 8 MB SPI ROMs.  When the SPI ROMs are
loaded with a 4 MB coreboot image, the virtual ROM size is 8 MB.  When
the SPI ROMs are loaded with an 8 MB coreboot image, the virtual ROM
size is 16 MB.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| CACHE_ROM_SIZE_OVERRIDE || drivers/intel/fsp1_0 || hex || Cache ROM Size ||  
| RAID_MISC_ROM_POSITION || southbridge/amd/agesa/hudson || hex || RAID Misc ROM Position ||  
This is the size of the cachable area that is passed into the FSP in
The RAID ROM requires that the MISC ROM is located between the range
the early initialization. Typically this should be the size of the CBFS
0xFFF0_0000 to 0xFFF0_FFFF. Also, it must 1K bytes aligned.
area, but the size must be a power of 2 whereas the CBFS size does not
The CONFIG_ROM_SIZE must be larger than 0x100000.
have this limitation.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| USE_GENERIC_FSP_CAR_INC || drivers/intel/fsp1_0 || bool || ||  
| HUDSON_LEGACY_FREE || southbridge/amd/agesa/hudson || bool || System is legacy free ||  
The chipset can select this to use a generic cache_as_ram.inc file
Select y if there is no keyboard controller in the system.
that should be good for all FSP based platforms.
This sets variables in AGESA and ACPI.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FSP_USES_UPD || drivers/intel/fsp1_0 || bool ||  ||  
| AZ_PIN || southbridge/amd/agesa/hudson || hex ||  ||  
If this FSP uses UPD/VPD data regions, select this in the chipset Kconfig.
bit 1,0 - pin 0
bit 3,2 - pin 1
bit 5,4 - pin 2
bit 7,6 - pin 3
||
||
|- bgcolor="#6699dd"
! align="left" | Menu: Devices || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MAINBOARD_DO_NATIVE_VGA_INIT || device || bool || Use native graphics initialization ||  
| EHCI_BAR || southbridge/amd/sb600 || hex || SATA Mode ||  
Some mainboards, such as the Google Link, allow initializing the display
Select the mode in which SATA should be driven. IDE or AHCI.
without the need of a binary only VGA OPROM. Enabling this option may be
The default is IDE.
faster, but also lacks flexibility in setting modes.


If unsure, say N.
config SATA_MODE_IDE
bool "IDE"


config SATA_MODE_AHCI
bool "AHCI"
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_ROM_RUN || device || bool || Run VGA Option ROMs ||  
| || || (comment) || || Super I/O ||
Execute VGA Option ROMs in coreboot if found. This is required
|- bgcolor="#eeeeee"
to enable PCI/AGP/PCI-E video cards when not using a SeaBIOS
| || || (comment) || || Embedded Controllers ||
payload.
|- bgcolor="#eeeeee"
 
| EC_ACPI || ec/acpi || bool ||  ||
When using a SeaBIOS payload it runs all option ROMs with much
ACPI Embedded Controller interface. Mostly found in laptops.
more complete BIOS interrupt services available than coreboot,
which some option ROMs require in order to function correctly.
 
If unsure, say N when using SeaBIOS as payload, Y otherwise.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| S3_VGA_ROM_RUN || device || bool || Re-run VGA Option ROMs on S3 resume ||  
| EC_GOOGLE_CHROMEEC || ec/google/chromeec || bool || ||  
Execute VGA Option ROMs in coreboot when resuming from S3 suspend.
Google's Chrome EC
 
When using a SeaBIOS payload it runs all option ROMs with much
more complete BIOS interrupt services available than coreboot,
which some option ROMs require in order to function correctly.
 
If unsure, say N when using SeaBIOS as payload, Y otherwise.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ALWAYS_LOAD_OPROM || device || bool ||  ||  
| EC_GOOGLE_CHROMEEC_ACPI_MEMMAP || ec/google/chromeec || bool ||  ||  
Always load option ROMs if any are found. The decision to run
When defined, ACPI accesses EC memmap data on ports 66h/62h. When
the ROM is still determined at runtime, but the distinction
not defined, the memmap data is instead accessed on 900h-9ffh via
between loading and not running comes into play for CHROMEOS.
the LPC bus.


An example where this is required is that VBT (Video BIOS Tables)
||
are needed for the kernel's display driver to know how a piece of
|- bgcolor="#eeeeee"
hardware is configured to be used.
| EC_GOOGLE_CHROMEEC_I2C || ec/google/chromeec || bool ||  ||
Google's Chrome EC via I2C bus.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| ON_DEVICE_ROM_RUN || device || bool || Run Option ROMs on PCI devices ||  
| EC_GOOGLE_CHROMEEC_I2C_PROTO3 || ec/google/chromeec || bool || ||  
Execute Option ROMs stored on PCI/PCIe/AGP devices in coreboot.
Use only proto3 for i2c EC communication.


If disabled, only Option ROMs stored in CBFS will be executed by
||
coreboot. If you are concerned about security, you might want to
|- bgcolor="#eeeeee"
disable this option, but it might leave your system in a state of
| EC_GOOGLE_CHROMEEC_LPC || ec/google/chromeec || bool ||  ||
degraded functionality.
Google Chrome EC via LPC bus.


When using a SeaBIOS payload it runs all option ROMs with much
||
more complete BIOS interrupt services available than coreboot,
|- bgcolor="#eeeeee"
which some option ROMs require in order to function correctly.
| EC_GOOGLE_CHROMEEC_MEC || ec/google/chromeec || bool ||  ||
Microchip EC variant for LPC register access.


If unsure, say N when using SeaBIOS as payload, Y otherwise.
||
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_PD || ec/google/chromeec || bool ||  ||
Indicates that Google's Chrome USB PD chip is present.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCI_OPTION_ROM_RUN_REALMODE || device || bool || Native mode ||  
| EC_GOOGLE_CHROMEEC_SPI || ec/google/chromeec || bool || ||  
If you select this option, PCI Option ROMs will be executed
Google's Chrome EC via SPI bus.
natively on the CPU in real mode. No CPU emulation is involved,
so this is the fastest, but also the least secure option.
(only works on x86/x64 systems)


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCI_OPTION_ROM_RUN_YABEL || device || bool || Secure mode ||  
| EC_GOOGLE_CHROMEEC_SPI_WAKEUP_DELAY_US || ec/google/chromeec || int || ||  
If you select this option, the x86emu CPU emulator will be used to
Force delay after asserting /CS to allow EC to wakeup.
execute PCI Option ROMs.


This option prevents Option ROMs from doing dirty tricks with the
||
system (such as installing SMM modules or hypervisors), but it is
|- bgcolor="#eeeeee"
also significantly slower than the native Option ROM initialization
| EC_EXTERNAL_FIRMWARE || ec/google/chromeec || hex ||  ||
method.
Disable building EC firmware if it's already built externally (and
added manually.)


This is the default choice for non-x86 systems.
||
|- bgcolor="#eeeeee"
| EC_GOOGLE_CHROMEEC_BOARDNAME || ec/google/chromeec || string || Chrome EC board name for EC ||
The board name used in the Chrome EC code base to build
the EC firmware.  If set, the coreboot build with also
build the EC firmware and add it to the image.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| YABEL_PCI_ACCESS_OTHER_DEVICES || device || bool || Allow Option ROMs to access other devices ||  
| EC_GOOGLE_CHROMEEC_PD_BOARDNAME || ec/google/chromeec || string || Chrome EC board name for PD ||  
Per default, YABEL only allows Option ROMs to access the PCI device
The board name used in the Chrome EC code base to build
that they are associated with. However, this causes trouble for some
the PD firmware. If set, the coreboot build with also
onboard graphics chips whose Option ROM needs to reconfigure the
build the EC firmware and add it to the image.
north bridge.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| YABEL_PCI_FAKE_WRITING_OTHER_DEVICES_CONFIG || device || bool || Fake success on writing other device's config space ||  
| EC_QUANTA_IT8518 || ec/quanta/it8518 || bool || ||  
By default, YABEL aborts when the Option ROM tries to write to other
Interface to QUANTA IT8518 Embedded Controller.
devices' config spaces. With this option enabled, the write doesn't
follow through, but the Option ROM is allowed to go on.
This can create issues such as hanging Option ROMs (if it depends on
that other register changing to the written value), so test for
impact before using this option.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| YABEL_VIRTMEM_LOCATION || device || hex || Location of YABEL's virtual memory ||  
| EC_QUANTA_ENE_KB3940Q || ec/quanta/ene_kb3940q || bool || ||  
YABEL requires 1MB memory for its CPU emulation. This memory is
Interface to QUANTA ENE KB3940Q Embedded Controller.
normally located at 16MB.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| YABEL_DIRECTHW || device || bool || Direct hardware access ||  
| EC_SMSC_MEC1308 || ec/smsc/mec1308 || bool || ||  
YABEL consists of two parts: It uses x86emu for the CPU emulation and
Shared memory mailbox interface to SMSC MEC1308 Embedded Controller.
additionally provides a PC system emulation that filters bad device
and memory access (such as PCI config space access to other devices
than the initialized one).
 
When choosing this option, x86emu will pass through all hardware
accesses to memory and I/O devices to the underlying memory and I/O
addresses. While this option prevents Option ROMs from doing dirty
tricks with the CPU (such as installing SMM modules or hypervisors),
they can still access all devices in the system.
Enable this option for a good compromise between security and speed.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIEXP_COMMON_CLOCK || device || bool || Enable PCIe Common Clock ||  
| EC_PURISM_LIBREM || ec/purism/librem || bool || ||  
Detect and enable Common Clock on PCIe links.
Purism Librem EC


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIEXP_ASPM || device || bool || Enable PCIe ASPM ||  
| EC_COMPAL_ENE932 || ec/compal/ene932 || bool || ||  
Detect and enable ASPM on PCIe links.
Interface to COMPAL ENE932 Embedded Controller.


||
||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIEXP_CLK_PM || device || bool || Enable PCIe Clock Power Management ||  
| EC_KONTRON_IT8516E || ec/kontron/it8516e || bool || ||  
Detect and enable Clock Power Management on PCIe.
Kontron uses an ITE IT8516E on the KTQM77. Its firmware might
come from Fintek (mentioned as Finte*c* somewhere in their Linux
driver).
The KTQM77 is an embedded board and the IT8516E seems to be
only used for fan control and GPIO.


||
||
||
|- bgcolor="#eeeeee"
| || || (comment) || || Intel FSP ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| EARLY_PCI_BRIDGE || device || bool || Early PCI bridge ||  
| HAVE_FSP_BIN || drivers/intel/fsp1_0 || bool || Use Intel Firmware Support Package ||  
While coreboot is executing code from ROM, the coreboot resource
Select this option to add an Intel FSP binary to
allocator has not been running yet. Hence PCI devices living behind
the resulting coreboot image.
a bridge are not yet visible to the system.


This option enables static configuration for a single pre-defined
Note: Without this binary, coreboot builds relying on the FSP
PCI bridge function on bus 0.
will not boot


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PCIEXP_L1_SUB_STATE || device || bool || Enable PCIe ASPM L1 SubState ||  
| FSP_FILE || drivers/intel/fsp1_0 || string || Intel FSP binary path and filename ||  
Detect and enable ASPM on PCIe links.
The path and filename of the Intel FSP binary for this platform.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SUBSYSTEM_VENDOR_ID || device || hex || Override PCI Subsystem Vendor ID ||  
| FSP_LOC || drivers/intel/fsp1_0 || hex || Intel FSP Binary location in CBFS ||  
This config option will override the devicetree settings for
The location in CBFS that the FSP is located. This must match the
PCI Subsystem Vendor ID.
value that is set in the FSP binary.  If the FSP needs to be moved,
rebase the FSP with Intel's BCT (tool).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SUBSYSTEM_DEVICE_ID || device || hex || Override PCI Subsystem Device ID ||  
| ENABLE_FSP_FAST_BOOT || drivers/intel/fsp1_0 || bool || Enable Fast Boot ||  
This config option will override the devicetree settings for
Enabling this feature will force the MRC data to be cached in NV
PCI Subsystem Device ID.
storage to be used for speeding up boot time on future reboots
and/or power cycles.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS || device || bool || Add a VGA BIOS image ||  
| ENABLE_MRC_CACHE || drivers/intel/fsp1_0 || bool || ||  
Select this option if you have a VGA BIOS image that you would
Enabling this feature will cause MRC data to be cached in NV storage.
like to add to your ROM.
This can either be used for fast boot, or just because the FSP wants
 
it to be saved.
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_FILE || device || string || VGA BIOS path and filename ||  
| MRC_CACHE_FMAP || drivers/intel/fsp1_0 || bool || Use MRC Cache in FMAP ||  
The path and filename of the file to use as VGA BIOS.
Use the region "RW_MRC_CACHE" in FMAP instead of "mrc.cache" in CBFS.
You must define a region in your FMAP named "RW_MRC_CACHE".


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| VGA_BIOS_ID || device || string || VGA device PCI IDs ||  
| MRC_CACHE_SIZE || drivers/intel/fsp1_0 || hex || Fast Boot Data Cache Size ||  
The comma-separated PCI vendor and device ID that would associate
This is the amount of space in NV storage that is reserved for the
your VGA BIOS to your video card.
fast boot data cache storage.


Example: 1106,3230
WARNING: Because this area will be erased and re-written, the size
should be a full sector of the flash ROM chip and nothing else should
be included in CBFS in any sector that the fast boot cache data is in.


In the above example 1106 is the PCI vendor ID (in hex, but without
||
the "0x" prefix) and 3230 specifies the PCI device ID of the
|- bgcolor="#eeeeee"
video card (also in hex, without "0x" prefix).
| VIRTUAL_ROM_SIZE || drivers/intel/fsp1_0 || hex || Virtual ROM Size ||
This is used to calculate the offset of the MRC data cache in NV
Storage for fast boot.  If in doubt, leave this set to the default
which sets the virtual size equal to the ROM size.


Under GNU/Linux you can run `lspci -nn` to list the IDs of your PCI devices.
Example: Cougar Canyon 2 has two 8 MB SPI ROMs.  When the SPI ROMs are
loaded with a 4 MB coreboot image, the virtual ROM size is 8 MB.  When
the SPI ROMs are loaded with an 8 MB coreboot image, the virtual ROM
size is 16 MB.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| INTEL_MBI || device || bool || Add an MBI image ||  
| CACHE_ROM_SIZE_OVERRIDE || drivers/intel/fsp1_0 || hex || Cache ROM Size ||  
Select this option if you have an Intel MBI image that you would
This is the size of the cachable area that is passed into the FSP in
like to add to your ROM.
the early initialization.  Typically this should be the size of the CBFS
area, but the size must be a power of 2 whereas the CBFS size does not
have this limitation.


You will be able to specify the location and file name of the
||
image later.
|- bgcolor="#eeeeee"
| USE_GENERIC_FSP_CAR_INC || drivers/intel/fsp1_0 || bool ||  ||
The chipset can select this to use a generic cache_as_ram.inc file
that should be good for all FSP based platforms.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| MBI_FILE || device || string || Intel MBI path and filename ||  
| FSP_USES_UPD || drivers/intel/fsp1_0 || bool || ||
The path and filename of the file to use as VGA BIOS.
If this FSP uses UPD/VPD data regions, select this in the chipset Kconfig.
||
|- bgcolor="#eeeeee"
| HAVE_INTEL_FIRMWARE || southbridge/intel/common/firmware || bool ||  ||  
Chipset uses the Intel Firmware Descriptor to describe the
layout of the SPI ROM chip.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PXE_ROM || device || bool || Add a PXE ROM image ||  
| || || (comment) || || Intel Firmware ||
Select this option if you have a PXE ROM image that you would
|- bgcolor="#eeeeee"
like to add to your ROM.
| HAVE_IFD_BIN || southbridge/intel/common/firmware || bool || Add Intel descriptor.bin file ||  
The descriptor binary


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PXE_ROM_FILE || device || string || PXE ROM filename ||  
| EM100 || southbridge/intel/common/firmware || bool || Configure IFD for EM100 usage ||  
The path and filename of the file to use as PXE ROM.
Set SPI frequency to 20MHz and disable Dual Output Fast Read Support


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| PXE_ROM_ID || device || string || network card PCI IDs ||  
| HAVE_ME_BIN || southbridge/intel/common/firmware || bool || Add Intel ME/TXE firmware ||  
The comma-separated PCI vendor and device ID that would associate
The Intel processor in the selected system requires a special firmware
your PXE ROM to your network card.
for an integrated controller.  This might be called the Management
Engine (ME), the Trusted Execution Engine (TXE) or something else
depending on the chip. This firmware might or might not be available
in coreboot's 3rdparty/blobs repository. If it is not and if you don't
have access to the firmware from 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/TXE firmware on your flash ROM.
 
||
|- bgcolor="#eeeeee"
| HAVE_GBE_BIN || southbridge/intel/common/firmware || bool || Add gigabit ethernet firmware ||
The integrated gigabit ethernet controller needs a firmware file.
Select this if you are going to use the PCH integrated controller
and have the firmware.


Example: 10ec,8168
||
|- bgcolor="#eeeeee"
| BUILD_WITH_FAKE_IFD || southbridge/intel/common/firmware || bool || Build with a fake IFD ||
If you don't have an Intel Firmware Descriptor (descriptor.bin) for your
board, you can select this option and coreboot will build without it.
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].


In the above example 10ec is the PCI vendor ID (in hex, but without
WARNING: Never write a complete coreboot.rom to your flash ROM if it
the "0x" prefix) and 8168 specifies the PCI device ID of the
was built with a fake IFD. It just won't work.
network card (also in hex, without "0x" prefix).


Under GNU/Linux you can run `lspci -nn` to list the IDs of your PCI devices.
[1] http://www.flashrom.org/pipermail/flashrom/2013-June/011083.html


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SOFTWARE_I2C || device || bool || Enable I2C controller emulation in software ||  
| IFD_BIOS_SECTION || southbridge/intel/common/firmware || string || BIOS Region Starting:Ending addresses within the ROM ||  
This config option will enable code to override the i2c_transfer
The BIOS region is typically the size of the CBFS area, and is located
routine with a (simple) software emulation of the protocol. This may
at the end of the ROM space.
be useful for debugging or on platforms where a driver for the real
 
I2C controller is not (yet) available. The platform code needs to
For an 8MB ROM with a 3MB CBFS area, this would look like:
provide bindings to manually toggle I2C lines.
0x00500000:0x007fffff


||
||
|- bgcolor="#eeeeee"
| IFD_ME_SECTION || southbridge/intel/common/firmware || string || ME/TXE Region Starting:Ending addresses within the ROM ||
The ME/TXE region typically starts at around 0x1000 and often fills the
ROM space not used by CBFS.
For an 8MB ROM with a 3MB CBFS area, this might look like:
0x00001000:0x004fffff


|- bgcolor="#6699dd"
||
! align="left" | Menu: Display || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FRAMEBUFFER_SET_VESA_MODE || device || bool || Set framebuffer graphics resolution ||  
| IFD_GBE_SECTION || southbridge/intel/common/firmware || string || GBE Region Starting:Ending addresses within the ROM ||  
Set VESA/native framebuffer mode (needed for bootsplash and graphical framebuffer console)
The Gigabit Ethernet ROM region is used when an Intel NIC is built into
the Southbridge/SOC and the platform uses this device instead of an external
PCIe NIC.  It will be located between the ME/TXE and the BIOS region.
 
Leave this empty if you're unsure.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FRAMEBUFFER_SET_VESA_MODE || device || bool || framebuffer graphics resolution ||  
| IFD_PLATFORM_SECTION || southbridge/intel/common/firmware || string || Platform Region Starting:Ending addresses within the Rom ||  
This option sets the resolution used for the coreboot framebuffer (and
The Platform region is used for platform specific data.
bootsplash screen).
It will be located between the ME/TXE and the BIOS region.
 
Leave this empty if you're unsure.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| FRAMEBUFFER_KEEP_VESA_MODE || device || bool || Keep VESA framebuffer ||  
| LOCK_MANAGEMENT_ENGINE || southbridge/intel/common/firmware || bool || Lock ME/TXE section ||  
This option keeps the framebuffer mode set after coreboot finishes
The Intel Firmware Descriptor supports preventing write accesses
execution. If this option is enabled, coreboot will pass a
from the host to the ME or TXE section in the firmware
framebuffer entry in its coreboot table and the payload will need a
descriptor. If the section is locked, it can only be overwritten
framebuffer driver. If this option is disabled, coreboot will switch
with an external SPI flash programmer. You will want this if you
back to text mode before handing control to a payload.
want to increase security of your ROM image once you are sure
that the ME/TXE firmware is no longer going to change.


||
If unsure, say N.
|- bgcolor="#eeeeee"
| BOOTSPLASH || device || bool || Show graphical bootsplash ||
This option shows a graphical bootsplash screen. The graphics are
loaded from the CBFS file bootsplash.jpg.
 
You will be able to specify the location and file name of the
image later.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| BOOTSPLASH_FILE || device || string || Bootsplash path and filename ||  
| CBFS_SIZE || southbridge/intel/common/firmware || hex || ||  
The path and filename of the file to use as graphical bootsplash
Reduce CBFS size to give room to the IFD blobs.
screen. The file format has to be jpg.


||
||
|- bgcolor="#6699dd"
|- bgcolor="#6699dd"
! align="left" | Menu: Generic Drivers || || || ||
! align="left" | Menu: AMD Platform Initialization || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH || drivers/spi || bool || ||  
| None || vendorcode/amd || None || AGESA source ||  
Select this option if your chipset driver needs to store certain
Select the method for including the AMD Platform Initialization
data in the SPI flash.
code into coreboot.  Platform Initialization code is required for
all AMD processors.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_ATOMIC_SEQUENCING || drivers/spi || bool || ||  
| CPU_AMD_AGESA_BINARY_PI || vendorcode/amd || bool || binary PI ||  
Select this option if the SPI controller uses "atomic sequencing."
Use a binary PI package.  Generally, these will be stored in the
Atomic sequencing is when the sequence of commands is pre-programmed
"3rdparty/blobs" directory. For some processors, these must be obtained
in the SPI controller. Hardware manages the transaction instead of
directly from AMD Embedded Processors Group
software. This is common on x86 platforms.
(http://www.amdcom/embedded).


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_MEMORY_MAPPED || drivers/spi || bool || ||  
| CPU_AMD_AGESA_OPENSOURCE || vendorcode/amd || bool || open-source AGESA ||  
Inform system if SPI is memory-mapped or not.
Build the PI package ("AGESA") from source code in the "vendorcode"
directory.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_SMM || drivers/spi || bool || SPI flash driver support in SMM ||  
| AGESA_BINARY_PI_VENDORCODE_PATH || vendorcode/amd/pi || string || AGESA PI directory path ||  
Select this option if you want SPI flash support in SMM.
Specify where to find the AGESA header files
for AMD platform initialization.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_NO_FAST_READ || drivers/spi || bool || Disable Fast Read command ||  
| AGESA_BINARY_PI_FILE || vendorcode/amd/pi || string || AGESA PI binary file name ||  
Select this option if your setup requires to avoid "fast read"s
Specify the binary file to use for AMD platform initialization.
from the SPI flash parts.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_ADESTO || drivers/spi || bool || ||  
| AGESA_BINARY_PI_LOCATION || vendorcode/amd/pi || string || AGESA PI binary address in ROM ||  
Select this option if your chipset driver needs to store certain
Specify the ROM address at which to store the binary Platform
data in the SPI flash and your SPI flash is made by Adesto Technologies.
Initialization code.


||
||
|- bgcolor="#6699dd"
! align="left" | Menu: ChromeOS || || || ||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_AMIC || drivers/spi || bool || ||  
| CHROMEOS || vendorcode/google/chromeos || bool || Build for ChromeOS ||  
Select this option if your chipset driver needs to store certain
Enable ChromeOS specific features like the GPIO sub table in
data in the SPI flash and your SPI flash is made by AMIC.
the coreboot table. NOTE: Enabling this option on an unsupported
board will most likely break your build.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_ATMEL || drivers/spi || bool ||  ||  
| VBNV_OFFSET || vendorcode/google/chromeos || hex ||  ||  
Select this option if your chipset driver needs to store certain
CMOS offset for VbNv data. This value must match cmos.layout
data in the SPI flash and your SPI flash is made by Atmel.
in the mainboard directory, minus 14 bytes for the RTC.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_EON || drivers/spi || bool || ||  
| CHROMEOS_VBNV_CMOS || vendorcode/google/chromeos || bool || Vboot non-volatile storage in CMOS. ||  
Select this option if your chipset driver needs to store certain
VBNV is stored in CMOS
data in the SPI flash and your SPI flash is made by EON.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_GIGADEVICE || drivers/spi || bool || ||  
| CHROMEOS_VBNV_CMOS_BACKUP_TO_FLASH || vendorcode/google/chromeos || bool || Back up Vboot non-volatile storage from CMOS to flash. ||  
Select this option if your chipset driver needs to store certain
Vboot non-volatile storage data will be backed up from CMOS to flash
data in the SPI flash and your SPI flash is made by Gigadevice.
and restored from flash if the CMOS is invalid due to power loss.


||
||
|- bgcolor="#eeeeee"
|- bgcolor="#eeeeee"
| SPI_FLASH_MACRONIX || drivers/spi || bool || ||  
| CHROMEOS_VBNV_EC || vendorcode/google/chromeos || bool || Vboot non-volatile storage in EC. ||  
Select this option if your chipset driver needs to store certain
VBNV is stored in