aboutsummaryrefslogtreecommitdiff
path: root/src/northbridge/intel/haswell/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'src/northbridge/intel/haswell/Kconfig')
-rw-r--r--src/northbridge/intel/haswell/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/northbridge/intel/haswell/Kconfig b/src/northbridge/intel/haswell/Kconfig
index 8c1e0b18f7..e1067c5949 100644
--- a/src/northbridge/intel/haswell/Kconfig
+++ b/src/northbridge/intel/haswell/Kconfig
@@ -37,7 +37,7 @@ config HASWELL_VBOOT_IN_BOOTBLOCK
Haswell can either start verstage in a separate stage
right after the bootblock has run or it can start it
after romstage for compatibility reasons.
- Haswell however uses a mrc.bin to initialse memory which
+ Haswell however uses a mrc.bin to initialize memory which
needs to be located at a fixed offset. Therefore even with
a separate verstage starting after the bootblock that same
binary is used meaning a jump is made from RW to the RO region