diff options
| author | Timothy Pearson <tpearson@raptorengineeringinc.com> | 2015-10-14 15:41:49 -0500 |
|---|---|---|
| committer | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-11-05 02:24:45 +0100 |
| commit | 855fc1fcdbf1e40931d31f25ca7091a7b0aeace5 (patch) | |
| tree | 59bd0a00f24697ebfc1b610110323385cc135608 /src/cpu/Kconfig | |
| parent | 24391321e8afe74063b1c4216732b66ad6d1ed36 (diff) | |
| download | coreboot-855fc1fcdbf1e40931d31f25ca7091a7b0aeace5.tar.xz | |
cpu/microcode: Remove EXTERNAL / ADDED_DURING_BUILD variables
There has been a concerted effort to clean up coreboot's microcode
handling that has included a move away from coreboot-specific
microcode file collections. As a result, the ability to specify
a single microcode file to be added to the image is of less utility
than before.
NOTE: This patch remove the built-in external microcode feature,
however the user can still specify no microcode during build and
manually add the correct microcode file(s) to the CBFS image after
the build is complete.
Change-Id: Ifea94c21e531a74953f5a0e2f489378c20ef3b5c
Signed-off-by: Timothy Pearson <tpearson@raptorengineeringinc.com>
Reviewed-on: http://review.coreboot.org/11903
Reviewed-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Tested-by: build bot (Jenkins)
Diffstat (limited to 'src/cpu/Kconfig')
| -rw-r--r-- | src/cpu/Kconfig | 32 |
1 files changed, 0 insertions, 32 deletions
diff --git a/src/cpu/Kconfig b/src/cpu/Kconfig index 578bab2296..9b9413c72c 100644 --- a/src/cpu/Kconfig +++ b/src/cpu/Kconfig @@ -67,17 +67,6 @@ config SUPPORT_CPU_UCODE_IN_CBFS bool default n -# This variable is used to determine if we add CPU microcode to CBFS during the -# build. Microcode can be added manually afterwards, or removed. As a result, -# code should not rely on this to tell if a microcode update is present or not, -# and should instead search CBFS. -# This variable is useful in determining if certain automated post-processing -# steps can be performed right after the build, such as automatically adding -# a firmware interface table. -config CPU_MICROCODE_ADDED_DURING_BUILD - bool - default y if CPU_MICROCODE_CBFS_GENERATE || CPU_MICROCODE_CBFS_EXTERNAL - choice prompt "Include CPU microcode in CBFS" if ARCH_X86 default CPU_MICROCODE_CBFS_GENERATE if SUPPORT_CPU_UCODE_IN_CBFS && USE_BLOBS @@ -95,20 +84,6 @@ config CPU_MICROCODE_CBFS_GENERATE If unsure, select this option. -config CPU_MICROCODE_CBFS_EXTERNAL - bool "Include external microcode file" - help - Select this option if you want to include an external file containing - 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. - - If unsure, select "Generate from tree" - config CPU_MICROCODE_CBFS_NONE bool "Do not include microcode updates" help @@ -160,10 +135,3 @@ config CPU_MICROCODE_MULTIPLE_FILES help Select this option to install separate microcode container files into CBFS instead of using the traditional monolithic microcode file format. - -config CPU_MICROCODE_FILE - string "Path and filename of CPU microcode" - depends on CPU_MICROCODE_CBFS_EXTERNAL - default "cpu_microcode.bin" - help - The path and filename of the file containing the CPU microcode. |