summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-03-05 11:21:03 +0800
committerSimon Glass <sjg@chromium.org>2015-03-24 21:22:37 -0600
commit83d9712e70dcd704462a3dc53254a05087c231f0 (patch)
treefa2cfda8c6c35b4faa3edf87793ed490a2c00e28 /doc
parent0eb9dc76e2987a07de9101e026ff26b28fa7496b (diff)
x86: Add queensbay fsp patch information in README.x86
The FSP release version 001 for Intel Queensbay has a bug which could cause random endless loop during the FspInit call. This bug was published by Intel although Intel did not describe any details. Describe this information in the x86 doc so that U-Boot Queensbay support is invulnerable. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.x867
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index fb87682e059..0355d1c9cb7 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -105,6 +105,13 @@ in this FSP package too.
Rename the first one to fsp.bin and second one to cmc.bin and put them in the
board directory.
+Note the FSP release version 001 has a bug which could cause random endless
+loop during the FspInit call. This bug was published by Intel although Intel
+did not describe any details. We need manually apply the patch to the FSP
+binary using any hex editor (eg: bvi). Go to the offset 0x1fcd8 of the FSP
+binary, change the following five bytes values from orginally E8 42 FF FF FF
+to B8 00 80 0B 00.
+
Now you can build U-Boot and obtain u-boot.rom
$ make crownbay_defconfig