diff options
authorStefan Tauner <>2011-11-13 23:03:30 +0000
committerStefan Tauner <>2011-11-13 23:03:30 +0000
commit25ffba7644de824c7cba10a0d367d60e499d575d (patch)
parent745f6bbec2acf6a94111df385384067b01f6e567 (diff)
Create a directory for documentation files
Move the serprog specification there and document a few things we could not figure out on intel platforms yet. Corresponding to flashrom svn r1465. Signed-off-by: Stefan Tauner <> Acked-by: Carl-Daniel Hailfinger <>
-rw-r--r--Documentation/serprog-protocol.txt (renamed from serprog-protocol.txt)0
2 files changed, 18 insertions, 0 deletions
diff --git a/Documentation/mysteries_intel.txt b/Documentation/mysteries_intel.txt
new file mode 100644
index 0000000..d6d3dfb
--- /dev/null
+++ b/Documentation/mysteries_intel.txt
@@ -0,0 +1,18 @@
+= BBAR on ICH8 =
+ There is no sign of BBAR (BIOS Base Address Configuration Register) in the
+ public datasheet (or specification update) of the ICH8. Also, the offset of
+ that register has changed between ICH7 (SPIBAR + 50h) and ICH9 (SPIBAR +
+ A0h), so we have no clue if or where it is on ICH8. Out current policy is to
+ not touch it at all and assume/hope it is 0.
+= Accesses beyond region bounds in descriptor mode =
+ Intel's flash image tool will always expand the last region so that it covers
+ the whole flash chip, but some boards ship with a different configuration.
+ It seems that in descriptor mode all addresses outside the used regions can not
+ be accessed whatsoever. This is not specified anywhere publicly as far as we
+ could tell. flashrom does not handle this explicitly yet. It will just fail
+ when trying to touch an address outside of any region.
+ See also
+= Unlocking the ME region =
diff --git a/serprog-protocol.txt b/Documentation/serprog-protocol.txt
index a3a4863..a3a4863 100644
--- a/serprog-protocol.txt
+++ b/Documentation/serprog-protocol.txt
OpenPOWER on IntegriCloud