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)
6 source src/cpu/armltd/Kconfig
7 source src/cpu/samsung/Kconfig
13 source src/cpu/amd/Kconfig
14 source src/cpu/intel/Kconfig
15 source src/cpu/via/Kconfig
16 source src/cpu/x86/Kconfig
20 select DEFAULT_EARLY_CONSOLE
23 config DCACHE_RAM_BASE
26 config DCACHE_RAM_SIZE
29 # FIXME MAX_PHYSICAL_CPUS should move to AMD specific code, or better
30 # yet be dropped completely.
31 config MAX_PHYSICAL_CPUS
33 depends on CPU_AMD_MODEL_10XXX || CPU_AMD_MODEL_FXX || CPU_AMD_AGESA
38 default y if MAX_CPUS != 1
41 This option is used to enable certain functions to make coreboot
42 work correctly on symmetric multi processor (SMP) systems.
48 This must equal address of ap_sipi_vector from bootblock build.
53 Select MMX in your socket or model Kconfig if your CPU has MMX
54 streaming SIMD instructions. ROMCC can build more efficient
55 code if it can spill to MMX registers.
60 Select SSE in your socket or model Kconfig if your CPU has SSE
61 streaming SIMD instructions. ROMCC can build more efficient
62 code if it can spill to SSE (aka XMM) registers.
68 Select SSE2 in your socket or model Kconfig if your CPU has SSE2
69 streaming SIMD instructions. Some parts of coreboot can be built
70 with more efficient code if SSE2 instructions are available.
74 config CPU_MICROCODE_IN_CBFS
79 prompt "Include CPU microcode in CBFS" if ARCH_X86
80 default CPU_MICROCODE_CBFS_GENERATE if CPU_MICROCODE_IN_CBFS
81 default CPU_MICROCODE_CBFS_NONE if !CPU_MICROCODE_IN_CBFS
83 config CPU_MICROCODE_CBFS_GENERATE
84 bool "Generate from tree"
86 Select this option if you want microcode updates to be assembled when
87 building coreboot and included in the final image as a separate CBFS
88 file. Microcode will not be hard-coded into ramstage.
90 The microcode file may be removed from the ROM image at a later
91 time with cbfstool, if desired.
93 If unsure, select this option.
95 config CPU_MICROCODE_CBFS_EXTERNAL
96 bool "Include external microcode file"
98 Select this option if you want to include an external file containing
99 the CPU microcode. This will be included as a separate file in CBFS.
100 A word of caution: only select this option if you are sure the
101 microcode that you have is newer than the microcode shipping with
104 The microcode file may be removed from the ROM image at a later
105 time with cbfstool, if desired.
107 If unsure, select "Generate from tree"
109 config CPU_MICROCODE_CBFS_NONE
110 bool "Do not include microcode updates"
112 Select this option if you do not want CPU microcode included in CBFS.
113 Note that for some CPUs, the microcode is hard-coded into the source
114 tree and is not loaded from CBFS. In this case, microcode will still
115 be updated. There is a push to move all microcode to CBFS, but this
116 change is not implemented for all CPUs.
118 This option currently applies to:
119 - Intel SandyBridge/IvyBridge
122 Microcode may be added to the ROM image at a later time with cbfstool,
125 If unsure, select "Generate from tree"
128 Microcode updates intend to solve issues that have been discovered
129 after CPU production. The expected effect is that systems work as
130 intended with the updated microcode, but we have also seen cases where
131 issues were solved by not applying microcode updates.
134 Note that some operating system include these same microcode patches,
135 so you may need to also disable microcode updates in your operating
136 system for this option to have an effect.
139 A word of CAUTION: some CPUs depend on microcode updates to function
140 correctly. Not updating the microcode may leave the CPU operating at
141 less than optimal performance, or may cause outright hangups.
142 There are CPUs where coreboot cannot properly initialize the CPU
143 without microcode updates
144 For example, if running with the factory microcode, some Intel
145 SandyBridge CPUs may hang when enabling CAR, or some VIA Nano CPUs
146 will hang when changing the frequency.
148 Make sure you have a way of flashing the ROM externally before
149 selecting this option.
153 config CPU_MICROCODE_FILE
154 string "Path and filename of CPU microcode"
155 depends on CPU_MICROCODE_CBFS_EXTERNAL
156 default "cpu_microcode.bin"
158 The path and filename of the file containing the CPU microcode.