summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Documentation/northbridge/intel/sandybridge/index.md1
-rw-r--r--Documentation/northbridge/intel/sandybridge/me_cleaner.md20
2 files changed, 21 insertions, 0 deletions
diff --git a/Documentation/northbridge/intel/sandybridge/index.md b/Documentation/northbridge/intel/sandybridge/index.md
index dcb090aad6..c1d4b9948d 100644
--- a/Documentation/northbridge/intel/sandybridge/index.md
+++ b/Documentation/northbridge/intel/sandybridge/index.md
@@ -6,3 +6,4 @@ This section contains documentation about coreboot on specific Intel "Sandy Brid
- [Native Ram Initialization](nri.md)
- [RAM initialization feature matrix](nri_features.md)
+- [ME Cleaner](me_cleaner.md)
diff --git a/Documentation/northbridge/intel/sandybridge/me_cleaner.md b/Documentation/northbridge/intel/sandybridge/me_cleaner.md
new file mode 100644
index 0000000000..1086e7e091
--- /dev/null
+++ b/Documentation/northbridge/intel/sandybridge/me_cleaner.md
@@ -0,0 +1,20 @@
+# ME Cleaner
+It's possible to 'clean' the ME partition within the flash medium as part
+of the build process. While cleaning as much code as possible is removed
+from the ME firmware partition. In this state the ME errors out and doesn't
+operate any more.
+
+**Using a 'cleaned' ME partition may lead to issues and its use should be
+carefully evaulated.**
+
+## Observations with 'cleaned' ME
+
+* Instable LPC bus
+ * SuperIO is malfunctioning
+ * TPM is malfunctioning
+ * Random system shutdowns on high bus activity
+
+## Filing bug reports
+
+Always test with unmodified IFD and ME section before reporting bugs to the
+coreboot project.