aboutsummaryrefslogtreecommitdiff
path: root/src/southbridge/intel/common/firmware/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'src/southbridge/intel/common/firmware/Kconfig')
-rw-r--r--src/southbridge/intel/common/firmware/Kconfig14
1 files changed, 8 insertions, 6 deletions
diff --git a/src/southbridge/intel/common/firmware/Kconfig b/src/southbridge/intel/common/firmware/Kconfig
index 71434ac0eb..8ad1fede41 100644
--- a/src/southbridge/intel/common/firmware/Kconfig
+++ b/src/southbridge/intel/common/firmware/Kconfig
@@ -38,15 +38,17 @@ config IFD_BIN_PATH
depends on HAVE_IFD_BIN && !BUILD_WITH_FAKE_IFD
config HAVE_ME_BIN
- bool "Add Intel Management Engine firmware"
+ bool "Add Intel ME/TXE firmware"
depends on HAVE_IFD_BIN
help
The Intel processor in the selected system requires a special firmware
- for an integrated controller called Management Engine (ME). The ME
- firmware might be provided in coreboot's 3rdparty/blobs 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.
+ 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.
config ME_BIN_PATH
string "Path to management engine firmware"