summaryrefslogtreecommitdiffstats
path: root/Documentation/mainboard/lenovo
diff options
context:
space:
mode:
authorMarcello Sylvester Bauer <sylv@sylv.io>2020-03-17 10:55:04 +0100
committerPatrick Georgi <pgeorgi@google.com>2020-03-31 10:32:25 +0000
commiteff1306ea480c991b7340928f67cbf59e6e11433 (patch)
tree4fb801f18a447ff590a74d7244fdb54f584ec9a2 /Documentation/mainboard/lenovo
parentc79e96b4eb310db9d44e36e2dff072c01469c380 (diff)
downloadcoreboot-eff1306ea480c991b7340928f67cbf59e6e11433.tar.gz
coreboot-eff1306ea480c991b7340928f67cbf59e6e11433.tar.bz2
coreboot-eff1306ea480c991b7340928f67cbf59e6e11433.zip
Documentation/mb/lenovo: Test shrunken ME on Ivy Bridge
Update the Lenovo Ivy Bridge documentation that no issues could be observed on W530. Tested on Lenovo W530 with stripped ME and found no issues: commit 93b0c7cfc632e7b57f1f4915886bf53397a12f25 * USB * Bluetooth * Wifi * Wifi-kill switch * libgfxinit * SATA * mSATA * Audio * SD-card * Ethernet * Keyboard * Fn-Keys * Display brightness * ACPI S3 resume * CPU temperature reporting * Stress test stable (intel_pstate no_turbo due to W530 overheating bug) * Youtube videos * stress -c 8 -m 1 -t 3600 Change-Id: I46d23d41cc6ade5e641a6ddb3f357a6036002edc Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io> Reviewed-on: https://review.coreboot.org/c/coreboot/+/39603 Reviewed-by: Patrick Rudolph <siro@das-labor.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'Documentation/mainboard/lenovo')
-rw-r--r--Documentation/mainboard/lenovo/Ivy_Bridge_series.md15
-rw-r--r--Documentation/mainboard/lenovo/Sandy_Bridge_series.md4
2 files changed, 17 insertions, 2 deletions
diff --git a/Documentation/mainboard/lenovo/Ivy_Bridge_series.md b/Documentation/mainboard/lenovo/Ivy_Bridge_series.md
index 2f83ffa8a8f0..f4f0efff6c11 100644
--- a/Documentation/mainboard/lenovo/Ivy_Bridge_series.md
+++ b/Documentation/mainboard/lenovo/Ivy_Bridge_series.md
@@ -76,3 +76,18 @@ region. The update is then written into the EC once.
[fl]: flashlayout_Ivy_Bridge.svg
+## Reducing Intel Managment Engine firmware size
+
+It is possible to reduce the Intel ME firmware size to free additional
+space for the `bios` region. This is usually referred to as *cleaning the ME* or
+*stripping the ME*.
+After reducing the Intel ME firmware size you must modify the original IFD,
+[split the resulting coreboot ROM](#splitting-the-coreboot-rom) and then write
+each ROM using an [external programmer].
+Have a look at [me_cleaner] for more information.
+
+Tests on Lenovo W530 showed no issues with a stripped and shrunken ME firmware.
+
+
+[me_cleaner]: ../../northbridge/intel/sandybridge/me_cleaner.md
+[external programmer]: ../../flash_tutorial/index.md
diff --git a/Documentation/mainboard/lenovo/Sandy_Bridge_series.md b/Documentation/mainboard/lenovo/Sandy_Bridge_series.md
index dbbbbeef30c3..37a75b97993e 100644
--- a/Documentation/mainboard/lenovo/Sandy_Bridge_series.md
+++ b/Documentation/mainboard/lenovo/Sandy_Bridge_series.md
@@ -47,11 +47,11 @@ region. The update is then written into the EC once.
## Reducing Intel Managment Engine firmware size
It is possible to reduce the Intel ME firmware size to free additional
-space for the `bios` region. This is usually refered to as *cleaning the ME* or
+space for the `bios` region. This is usually referred to as *cleaning the ME* or
*stripping the ME*.
After reducing the Intel ME firmware size you must modify the original IFD
and then write a full ROM using an [external programmer].
-Have a look at the [me_cleaner] for more information.
+Have a look at [me_cleaner] for more information.
Tests on Lenovo X220 showed no issues with a stripped ME firmware.