1 # Warning: This file is included whether or not the if is here.
2 # The if controls how the evaluation occurs.
3 # (See also src/Kconfig)
5 source "src/cpu/*/Kconfig"
12 config DCACHE_RAM_SIZE
15 config DCACHE_BSP_STACK_SIZE
18 config EARLYRAM_BSP_STACK_SIZE
19 depends on RESET_VECTOR_IN_RAM
24 default y if MAX_CPUS != 1
27 This option is used to enable certain functions to make coreboot
28 work correctly on symmetric multi processor (SMP) systems.
33 Select MMX in your socket or model Kconfig if your CPU has MMX
34 streaming SIMD instructions.
39 Select SSE in your socket or model Kconfig if your CPU has SSE
40 streaming SIMD instructions.
47 Select SSE2 in your socket or model Kconfig if your CPU has SSE2
48 streaming SIMD instructions. Some parts of coreboot can be built
49 with more efficient code if SSE2 instructions are available.
53 config SUPPORT_CPU_UCODE_IN_CBFS
57 config USES_MICROCODE_HEADER_FILES
59 select SUPPORT_CPU_UCODE_IN_CBFS
61 This is selected by a board or chipset to set the default for the
62 microcode source choice to a list of external microcode headers
64 config MICROCODE_BLOB_NOT_IN_BLOB_REPO
67 Selected by platforms that don't maintain microcode updates in the
70 config MICROCODE_BLOB_NOT_HOOKED_UP
73 Selected by platforms that haven't hooked microcode updates up yet.
75 config MICROCODE_BLOB_UNDISCLOSED
78 Selected by work-in-progress platforms that don't have microcode
79 updates available yet.
81 config USE_CPU_MICROCODE_CBFS_BINS
84 Automatically selected below to add binary microcode files
85 (`cpu_microcode_bins` in the makefiles) to CBFS.
88 prompt "Include CPU microcode in CBFS" if ARCH_X86
89 default CPU_MICROCODE_CBFS_EXTERNAL_HEADER if USES_MICROCODE_HEADER_FILES
90 default CPU_MICROCODE_CBFS_NONE if MICROCODE_BLOB_NOT_IN_BLOB_REPO || \
91 MICROCODE_BLOB_NOT_HOOKED_UP || \
92 MICROCODE_BLOB_UNDISCLOSED
93 depends on SUPPORT_CPU_UCODE_IN_CBFS
95 config CPU_MICROCODE_CBFS_DEFAULT_BINS
96 bool "Generate from tree"
97 select USE_CPU_MICROCODE_CBFS_BINS
98 depends on !(MICROCODE_BLOB_NOT_IN_BLOB_REPO || \
99 MICROCODE_BLOB_NOT_HOOKED_UP || \
100 MICROCODE_BLOB_UNDISCLOSED)
102 Select this option if you want microcode updates to be assembled when
103 building coreboot and included in the final image as a separate CBFS
104 file. Microcode will not be hard-coded into ramstage.
106 The microcode file may be removed from the ROM image at a later
107 time with cbfstool, if desired.
109 If unsure, select this option.
111 config CPU_MICROCODE_CBFS_EXTERNAL_BINS
112 bool "Include external microcode binary"
113 select USE_CPU_MICROCODE_CBFS_BINS
115 Select this option if you want to include external binary files
116 in the CPUs native format. They will be included as a separate
119 A word of caution: only select this option if you are sure the
120 microcode that you have is newer than the microcode shipping with
123 The microcode file may be removed from the ROM image at a later
124 time with cbfstool, if desired.
126 If unsure, and applicable, select "Generate from tree"
128 config CPU_MICROCODE_CBFS_EXTERNAL_HEADER
129 bool "Include external microcode header files"
131 Select this option if you want to include external c header files
132 containing the CPU microcode. This will be included as a separate
135 A word of caution: only select this option if you are sure the
136 microcode that you have is newer than the microcode shipping with
139 The microcode file may be removed from the ROM image at a later
140 time with cbfstool, if desired.
142 If unsure, and applicable, select "Generate from tree"
144 config CPU_MICROCODE_CBFS_NONE
145 bool "Do not include microcode updates"
147 Select this option if you do not want CPU microcode included in CBFS.
149 Microcode may be added to the ROM image at a later time with cbfstool,
152 If unsure, and applicable, select "Generate from tree"
155 Microcode updates intend to solve issues that have been discovered
156 after CPU production. The expected effect is that systems work as
157 intended with the updated microcode, but we have also seen cases where
158 issues were solved by not applying microcode updates.
161 Note that some operating system include these same microcode patches,
162 so you may need to also disable microcode updates in your operating
163 system for this option to have an effect.
166 A word of CAUTION: some CPUs depend on microcode updates to function
167 correctly. Not updating the microcode may leave the CPU operating at
168 less than optimal performance, or may cause outright hangups.
169 There are CPUs where coreboot cannot properly initialize the CPU
170 without microcode updates
171 For example, if running with the factory microcode, some Intel
172 SandyBridge CPUs may hang when enabling CAR, or some VIA Nano CPUs
173 will hang when changing the frequency.
175 Make sure you have a way of flashing the ROM externally before
176 selecting this option.
180 config CPU_MICROCODE_HEADER_FILES
181 string "List of space separated microcode header files with the path"
182 depends on CPU_MICROCODE_CBFS_EXTERNAL_HEADER
184 A list of one or more microcode header files with path from the
185 coreboot directory. These should be separated by spaces.
187 config CPU_UCODE_BINARIES
188 string "Microcode binary path and filename"
189 depends on CPU_MICROCODE_CBFS_EXTERNAL_BINS
192 Some platforms have microcode in the blobs directory, and these can
193 be hardcoded in the makefiles. For platforms with microcode
194 binaries that aren't in the makefile, set this option to pull
197 This should contain the full path of the file for one or more
198 microcode binary files to include, separated by spaces.
200 If unsure, leave this blank.